From: TakeV <takev@disroot.org>
To: help-guix@gnu.org
Subject: SSH home container permissions issue
Date: Wed, 24 Jan 2024 15:30:41 -0500 [thread overview]
Message-ID: <d23zsoo4bbcr25xkh5zbppdyfcf4cspcxbcqgarumkv7dql2k4@adhhfamibvwp> (raw)
[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]
I am trying to test out ssh in a home container, but there is some odd behavior when it tries to read the config.
The commands I used:
> takev@gaba ~/guix/home$ guix home container -N config.scm
> takev@gaba ~$ ssh [redacted]
> Bad owner or permissions on /home/takev/.ssh/config
Looking at the permissions on that file, and the weird thing is that both authorized_keys and config appear to be identical to the working version I have outside of the container:
Container version:
> takev@gaba ~$ ls -al .ssh/
> total 0
> drwx------ 2 takev users 80 Jan 24 20:03 ./
> drwxr-xr-x 7 takev users 260 Jan 24 20:03 ../
> lrwxrwxrwx 1 takev users 59 Jan 24 20:03 authorized_keys -> /gnu/store/vs9xkamzjpj5dmvxgpw58dj3ykrw1h1l-authorized_keys
> lrwxrwxrwx 1 takev users 52 Jan 24 20:03 config -> /gnu/store/q1vgzvlz5ksn0q6mx2nvxj1i0m6adh60-ssh.conf
Live version:
> takev@gaba ~/guix/home$ ls -al ~/.ssh/
> total 32
> drwx------ 2 takev users 4096 Jan 24 15:12 ./
> drwx------ 84 takev users 4096 Jan 24 15:12 ../
> lrwxrwxrwx 1 takev users 59 Jan 24 15:12 authorized_keys -> /gnu/store/vs9xkamzjpj5dmvxgpw58dj3ykrw1h1l-authorized_keys
> lrwxrwxrwx 1 takev users 52 Jan 24 15:12 config -> /gnu/store/q1vgzvlz5ksn0q6mx2nvxj1i0m6adh60-ssh.conf
> -rw------- 1 takev users 419 Jun 4 2021 id_ed25519
> -rw-r--r-- 1 takev users 108 Jun 4 2021 id_ed25519.pub
> -rw------- 1 takev users 13722 Jan 23 10:59 known_hosts
Is this a bug, or is there some sort of setting I need to set?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
reply other threads:[~2024-01-24 20:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d23zsoo4bbcr25xkh5zbppdyfcf4cspcxbcqgarumkv7dql2k4@adhhfamibvwp \
--to=takev@disroot.org \
--cc=help-guix@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.