all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon South <simon@simonsouth.net>
To: Morgan.J.Smith@outlook.com
Cc: 49601@debbugs.gnu.org
Subject: [bug#49601] [PATCH] services: transmission: Create downloads directory.
Date: Sat, 17 Jul 2021 07:52:21 -0400	[thread overview]
Message-ID: <87y2a5gnt6.fsf@simonsouth.net> (raw)
In-Reply-To: <BYAPR05MB40231D4388D70966EC26C79CC5109@BYAPR05MB4023.namprd05.prod.outlook.com> (Morgan J. Smith's message of "Fri, 16 Jul 2021 20:28:31 -0400")

Morgan.J.Smith@outlook.com writes:
> This fixes a bug where transmission doesn't have permission to create
> it's download directory. This bug occurs when download-dir is
> configured to a location where the transmission user doesn't have
> permission to create a directory.

Morgan,

I recall originally having the service activation create the downloads
directory, as your change makes it do, but then removing this as there
was some common case where it made service activation fail.
Unfortunately, I've forgotten what that was.

Let me see if I can duplicate that and if so, perhaps we can find a
solution that will handle both cases. At any rate:

> +                              (,download-dir #o755))

The folder permissions should be #o750, not #o755. The reasoning here is
that it ought to be possible to place limits on who can see and access
files being shared by other users.

-- 
Simon South
simon@simonsouth.net




  reply	other threads:[~2021-07-17 11:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-17  0:28 [bug#49601] [PATCH] services: transmission: Create downloads directory Morgan.J.Smith
2021-07-17 11:52 ` Simon South [this message]
2021-07-17 17:47   ` Simon South
2021-07-19 12:13   ` Efraim Flashner
2021-07-21 13:14     ` Simon South

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=87y2a5gnt6.fsf@simonsouth.net \
    --to=simon@simonsouth.net \
    --cc=49601@debbugs.gnu.org \
    --cc=Morgan.J.Smith@outlook.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 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.