Send us a question or comment
   

My public-key authentication failed on Red Hat and VShell® logged an "Unable to authenticate" error. Why?

If VShell could not authenticate and logged the following error message:

"Disconnecting from server: Unable to authenticate using any of the configured authentication methods."

there is most likely a UMASK problem.

On Red Hat, the default UMASK is 0002, which means that files are created by default with the group-writable bit set. This causes public-key authentication with vshelld to fail. To keep this from happening on newly created files, change the setting on your UMASK to make them not group-writable (set them to 0022, for example). To correct this problem with existing files, change the permissions on your .vshell and publickey folders and any files in your publickey folder so that they are writable only by the owner.

Was this information helpful?
Yes No
Thank you!
Send your comments and questions to VanDyke Software Support,
or join the discussion in the VanDyke Software Forums.
Can't find the answer you're looking for?
Ask VanDyke Software Support directly
and we will get back to you as soon as possible.
Three Fast Ways to Learn More About VShell for Windows and UNIX
Tell me more. E-mail us your questions about putting VShell to work for your organization.
Try it today! Download a free 30-day evaluation copy of VShell for Windows or UNIX.
Talk to us. Let us help define the right VShell server solution for your company.