On 8/24/24 12:31 AM, Jeffrey Walton wrote:
On Sat, Aug 24, 2024 at 3:24 AM Samuel Sieb <samuel@xxxxxxxx> wrote:
On 8/23/24 3:17 PM, Dave Close wrote:
Jeffrey Walton wrote:
At this point, I would visit each machine and:
mkdir -p ~/.ssh
chown -R dclose:dclose ~/.ssh
chmod -R o-rwx ~/.ssh
That would be guaranteed to cause failure. For example, my private keys
cannot have 0777 permissions!
I think you're misinterpreting that command. It *removes* all "other"
permissions from the files. I'm not sure what the point of it is, but
it won't harm anything.
SSH server will refuse a connection from the user if the permissions
on the .ssh/ directory, keys or authorized_keys are too loose. See,
for example, <https://stackoverflow.com/q/67000681>.
Sure, but ssh was working and using sudo isn't going to add permissions
to the files. (It's not even going to use those files.)
But the solution was already found anyway, so this is all irrelevant.
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
