From: "Ludovic Courtès" <ludo@gnu.org>
To: "zero@fedora" <shinyzero0@tilde.club>
Cc: 67789@debbugs.gnu.org
Subject: [bug#67789] [PATCH] doc: Secure Shell: Add note about sshd and wrong permissions
Date: Thu, 14 Dec 2023 14:43:30 +0100 [thread overview]
Message-ID: <87le9wx5kt.fsf@gnu.org> (raw)
In-Reply-To: <20231211233532.63690-1-shinyzero0@tilde.club> (shinyzero0@tilde.club's message of "Tue, 12 Dec 2023 02:35:32 +0300")
Hello,
"zero@fedora" <shinyzero0@tilde.club> skribis:
> * doc/guix.texi (Home services: Secure Shell): Add note about sshd blocking connections because of wrong permissions
[...]
> +@quotation Note
> +Note that @command{sshd} will block any @command{ssh} connections to you if
> +your files in @file{~/.ssh} have wrong permissions or ownership, as the ones
> +created by this service do. To fix that, you need to set @code{StrictModes=no}
> +in your @command{sshd} configuration
> +@end quotation
I think we’d rather fix the permissions of those files than document the
bug.
On my laptop permissions seem to be good:
--8<---------------cut here---------------start------------->8---
$ ls -ld ~/.ssh/authorized_keys
lrwxrwxrwx 1 ludo users 59 Dec 10 23:36 /home/ludo/.ssh/authorized_keys -> /gnu/store/k79g5iaaa7gij52nrbhjz6fqq7banzdz-authorized_keys
$ ls -ld ~/.ssh
drwx------ 3 ludo users 4096 Dec 10 23:36 /home/ludo/.ssh/
$ ssh localhost uname
Linux
--8<---------------cut here---------------end--------------->8---
Maybe there are cases when this is not the case, maybe when ~/.ssh does
not exist prior to running ‘guix home reconfigure’?
Thanks,
Ludo’.
next prev parent reply other threads:[~2023-12-14 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 23:35 [bug#67789] [PATCH] doc: Secure Shell: Add note about sshd and wrong permissions zero@fedora
2023-12-14 13:43 ` Ludovic Courtès [this message]
2023-12-15 19:24 ` ShinyZero0
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87le9wx5kt.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=67789@debbugs.gnu.org \
--cc=shinyzero0@tilde.club \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).