"Bad owner or permissions" error using Cygwin's ssh.exe



When attempting to connect to a remote server via SSH, an error message similar to \bad owner or permissions on .ssh/config\ may be encountered. This error is indicative of a problem with the user’s SSH configuration, and is usually caused by an incorrect file or folder ownership or permissions issue.

In order to resolve this issue, it is necessary to verify that the user’s SSH configuration is correct. This can be done by examining the ownership and permissions of the user’s SSH configuration files and folders. Typically, the SSH configuration files and folders should be owned by the user, and should have a file permission set of “600”.

To change the ownership of the user’s SSH configuration files and folders, the “chown” command can be used. This command takes the form “chown username:groupname filename”, and should be used to change the ownership of the user’s SSH configuration files and folders to the user.

Once the ownership of the user’s SSH configuration files and folders has been changed, the “chmod” command can be used to set the correct file permission. This command takes the form “chmod 600 filename”, and should be used to set the correct file permission for the user’s SSH configuration files and folders.

Once the ownership and permissions of the user’s SSH configuration files and folders have been changed, the user should be able to connect to the remote server via SSH without encountering the “bad owner or permissions” error. It is important to note that, if the ownership and/or permissions of the user’s SSH configuration files and folders are incorrect, the user may still not be able to connect to the remote server via SSH. In this instance, the user should examine their SSH configuration for any errors or inconsistencies.

In conclusion, the “bad owner or permissions” error encountered when attempting to connect to a remote server via SSH is usually caused by an incorrect file or folder ownership or permissions issue. In order to resolve this issue, it is necessary to verify that the user’s SSH configuration is correct by changing the ownership and permissions of the user’s SSH configuration files and folders to the user, and setting the correct file permission for the user’s SSH configuration files and folders. If the user is still unable to connect to the remote server via SSH, they should examine their SSH configuration for any errors or inconsistencies.

Inquire Now

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Find your next full or part-time role here

ScaleDesk can either help you find your next full time gig or a part time side gig where you can create extra income!

Onboard with us once
Skip HR screening and go to the final interview with with only your resume and a video interview you never have to redo
Get paid electronically every month for the hours you work
We will be your reference even if you work for us once

IT Teams: Use ScaleDesk to augment your team

Schedule Demo