Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I connect through ssh (putty) using a user authentication public key stored on the ssh server in ~/.ssh/authorized_keys. Permissions for ~ are 750. When I change them to 757 I can't connect anymore - connection by key is not accepted by server. How is this possible?
it's possible because that's the way it works. that data is PRIVATE and you're making ANYONE able to read it. So another user could trivially add a key to YOUR config and login as you. Why would you want to change it in the first place??
it's possible because that's the way it works. that data is PRIVATE and you're making ANYONE able to read it. So another user could trivially add a key to YOUR config and login as you. Why would you want to change it in the first place??
You say that sshd checks the permissions for the home directory where ~/.ssh/authorized_keys is stored? The permissions for ~/.ssh are still 700, and for authorized_keys are 644 (read for everbody, write for owner).
I did this stupid thing while trying to make local mail work, but now it works with the right permissions. Anyway, are you sure that sshd is checking the permissions of the ~ directory? I did not expect this behaviour.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.