public inbox for mlmmj@mlmmj.org
 help / color / mirror / Atom feed
From: Thomas Goirand <thomas@goirand.fr>
To: mlmmj@mlmmj.org
Subject: [mlmmj] Fwd: Bug#617242: mlmmj-make-ml does not ensure correct permissions
Date: Mon, 07 Mar 2011 17:20:43 +0000	[thread overview]
Message-ID: <4D7513EB.7090407@goirand.fr> (raw)

Someone sent this against the MLMMJ package in Debian. I found it a very
valid request. I think either mlmmj-make-ml should set the umask
explicitly, or even better, perform some chmods.

Thomas

-------- Original Message --------
Subject: Bug#617242: mlmmj-make-ml does not ensure correct permissions
for created files and directories
Resent-Date: Mon, 07 Mar 2011 13:21:02 +0000,	Mon, 07 Mar 2011 13:21:05
+0000
Resent-From: Reuben Thomas <rrt@sc3d.org>
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: MLMMJ packaging team <pkg-mlmmj-devel@lists.alioth.debian.org>
Date: Mon, 07 Mar 2011 13:16:46 +0000
From: Reuben Thomas <rrt@sc3d.org>
Reply-To: Reuben Thomas <rrt@sc3d.org>, 617242@bugs.debian.org
To: Debian Bug Tracking System <submit@bugs.debian.org>

Package: mlmmj
Version: 1.2.17-1
Severity: minor


I have my umask set to 0027. If I run mlmmj-make-ml with sudo, then
this umask is inherited, and used to create all the files and
directories for a new mailing list, which is wrong. The files and
directories should be explicitly chmodded to the correct permissions.



             reply	other threads:[~2011-03-07 17:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 17:20 Thomas Goirand [this message]
2011-03-07 17:29 ` [mlmmj] Fwd: Bug#617242: mlmmj-make-ml does not ensure correct Moritz Wilhelmy
2011-03-08  0:03 ` Ben Schmidt
2011-03-08  0:11 ` Ben Schmidt
2011-03-08  9:55 ` Mads Martin Jørgensen
2011-03-08 13:44 ` Thomas Goirand
2011-03-08 21:03 ` Ben Schmidt

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=4D7513EB.7090407@goirand.fr \
    --to=thomas@goirand.fr \
    --cc=mlmmj@mlmmj.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox