Why is chmod 600 recommended on a public authorized_key??

When inserting (pasting) a public SSH key on a user’s folder, within a Droplet, Im seeing a lot of people urge to

chmod 700 ~/.ssh

and then to

chmod 600 ~/.ssh/authorized_keys

But if i chmod 600 ~/.ssh/authorized_keys with my user then i am not able to login via ssh, i need to change it to chmod 755 ~/.ssh/authorized_keys in order to connect.

Which leads to my question: Why is so important to have a public key under chmod 600??

And why im not being able to connect with chmod 600 but only with chmod 755?

Thanks in advanced

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Ok to answer my own question i was not able to SSH with my user cause i needed to make sure that user owned the files and folders and not root, with:

sudo chown -R user:user /home/user/.ssh

where user = myusername

But i still don’t understand why a public key needs chmod 0600