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 16:56:06 -0300 [thread overview]
Message-ID: <1737102.PxY0oXxzeL@popigai> (raw)
In-Reply-To: <CAJejy7=okwP6Sous-ab_Ta44CgDDT9i795AxBcaZKyWaM8WErQ@mail.gmail.com>
Hello Zacchaeus,
Em quinta-feira, 3 de fevereiro de 2022, às 15:08:12 -03, Zacchaeus Scheffer
escreveu:
> I finally migrated my home configuration to guix home. However, it seems
> guix home creates all symlinks with 777 permissions. This causes
> problems with openssh as it will not recognize my
> ~/.ssh/authorized_keys. It seems the directories have reasonable
> permissions (maybe because they already existed?), but it seems like
> someone could in theory edit the symlinks in-place (though I wasn't able
> to figure that out).
In Linux, symlink permissions are meaningless. From the chmod(1) man page:
“chmod never changes the permissions of symbolic links; the chmod system
call cannot change their permissions. This is not a problem since the
permissions of symbolic links are never used. However, for each symbolic
link listed on the command line, chmod changes the permissions of the
pointed-to file. In contrast, chmod ignores symbolic links encountered
during recursive directory traversals.”
So AFAIK there’s nothing that guix home can do about that.
I don’t know what that implies for OpenSSH and authorized_keys, though.
--
Thanks,
Thiago
next prev parent reply other threads:[~2022-02-03 20:33 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 [this message]
2022-02-03 21:22 ` Zacchaeus Scheffer
2022-02-03 23:06 ` Thiago Jung Bauermann via Bug reports for GNU Guix
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=1737102.PxY0oXxzeL@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).