unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Evgeny Pisemsky <evgeny@pisemsky.com>
To: 56444@debbugs.gnu.org
Subject: bug#56444: Acknowledgement (Gitolite home directory permissions)
Date: Fri, 08 Jul 2022 11:10:42 +0300	[thread overview]
Message-ID: <87ilo8ja7x.fsf@pisemsky.com> (raw)
In-Reply-To: <handler.56444.B.165722972531874.ack@debbugs.gnu.org> (GNU bug Tracking System's message of "Thu, 07 Jul 2022 21:36:01 +0000")

After some digging I came up to the procedure `activate-users+groups' in
the file `gnu/build/activation.scm' and found the following lines:

┌────
│ ;; Always set ownership and permissions for home directories of system
│ ;; accounts.  If a service needs looser permissions on its home
│ ;; directories, it can always chmod it in an activation snippet.
│ (chown home (passwd:uid pwd) (passwd:gid pwd))
│ (chmod home #o700)))
└────

So it looks like the case for gitolite activation procedure - it should
chmod the home directory with respect to the umask value.




  parent reply	other threads:[~2022-07-08  8:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 21:35 bug#56444: Gitolite home directory permissions Evgeny Pisemsky
     [not found] ` <handler.56444.B.165722972531874.ack@debbugs.gnu.org>
2022-07-08  8:10   ` Evgeny Pisemsky [this message]
2022-08-19 13:32 ` bug#56444: Patch to fix " Thompson, David
2022-08-23 12:41   ` Maxime Devos
2022-08-23 14:45     ` Thompson, David
2022-08-29 12:49       ` Thompson, David
2022-08-29 12:52         ` Maxime Devos
2022-08-29 12:57           ` bug#56444: [EXT] " Thompson, David
2022-08-29 13:09             ` Maxime Devos
2022-08-29 13:11             ` Maxime Devos
2022-08-29 13:19             ` Maxime Devos
2022-08-29 13:30               ` bug#56444: [EXT] " Thompson, David
2022-08-29 13:44                 ` Maxime Devos
2022-08-29 13:59                   ` bug#56444: [EXT] " Thompson, David
2022-08-29 21:05                     ` zimoun
2022-08-30 15:20                     ` bug#56444: " Ludovic Courtès
2022-08-30 16:39                       ` bug#56444: [EXT] " Thompson, David
2022-08-30 18:31                       ` david larsson

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=87ilo8ja7x.fsf@pisemsky.com \
    --to=evgeny@pisemsky.com \
    --cc=56444@debbugs.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 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).