From: Thiago Jung Bauermann via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Zacchaeus Scheffer <zaccysc@gmail.com>
Cc: 53752@debbugs.gnu.org
Subject: bug#53752: guix home symlink permissions
Date: Thu, 03 Feb 2022 20:06:25 -0300 [thread overview]
Message-ID: <68523536.hgpfNYuzMs@popigai> (raw)
In-Reply-To: <CAJejy7mVv5whyc3nJt3e8S+DkKyZbRdoXRNT5q-DdVdJNLfX4A@mail.gmail.com>
Em quinta-feira, 3 de fevereiro de 2022, às 18:22:49 -03, Zacchaeus Scheffer
escreveu:
> It seems the permissions on the symlink don't matter. The problem is
> that the file linked to in the store is readable by everyone (which I am
> ok with because it's just public keys).
>
> There is a solution with guix system by configuring openssh directly (see
> openssh-configuration -> authorized-keys), but there really should be a
> way to do this with guix home. (anyone that can call guix home for my
> user can see/modify my authorized_keys anyway)
>
> Maybe this bug should be renamed to something like "guix home cannot
> configure authorized_keys"?
Good idea. I just made that change.
I don’t use Guix Home and I don’t know much about its internals, so
unfortunately I can’t help much with this problem.
--
Thanks,
Thiago
next prev parent reply other threads:[~2022-02-03 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 18:08 bug#53752: guix home symlink permissions Zacchaeus Scheffer
2022-02-03 19:56 ` Thiago Jung Bauermann via Bug reports for GNU Guix
2022-02-03 21:22 ` Zacchaeus Scheffer
2022-02-03 23:06 ` Thiago Jung Bauermann via Bug reports for GNU Guix [this message]
2022-02-04 9:58 ` Liliana Marie Prikler
2022-02-04 18:17 ` Zacchaeus Scheffer
2022-02-07 19:47 ` Zacchaeus Scheffer
2022-02-07 21:02 ` Maxime Devos
2022-02-08 7:01 ` Liliana Marie Prikler
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=68523536.hgpfNYuzMs@popigai \
--to=bug-guix@gnu.org \
--cc=53752@debbugs.gnu.org \
--cc=bauermann@kolabnow.com \
--cc=zaccysc@gmail.com \
/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).