public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Alexander Marx <alexander.marx@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] BUG12403: Fix permissions of DMA configfile
Date: Mon, 11 May 2020 11:02:28 +0200	[thread overview]
Message-ID: <d9da1fe5-fec8-604c-e559-5dc2349619ce@ipfire.org> (raw)
In-Reply-To: <D5DB60C8-BAAC-45F4-BAF9-95F6C57E82C0@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2367 bytes --]



Am 11.05.20 um 10:35 schrieb Michael Tremer:
> Hello,
>
>> On 9 May 2020, at 07:06, Alexander Marx <alexander.marx(a)ipfire.org> wrote:
>>
>> From: Alexander Marx <amarx(a)ipfire.org>
> Your Git is set up with a different email address for commits than what you are using for email. Is this intentional?
There were some confusions when i set up the accounts in the beginning....

>> Change read permissions of dma configfile so other users are able to read it.
>> Needed for Addons like WIO to send Mails.
> I am not sure if this patch is a good idea. We will make the credentials readable for everyone.
>
> What would probably work better is a group called “mail” which nobody and wio will be a member of so that they can read the configuration file. Others still won’t be able to read it.
>
> What do you think about this solution?
>
> Best,
> -Michael
Well, it's a bit more complex. The next thing i am working on with 
Stephan will be the APCUPSD with a nice webinterface. To make things 
round we are thinking of putting the apcupd and website together in one 
addon. But the apcupsd has a complete different user (apcups) and maybe 
there will be other tools and services with own usernames that also 
could use the mailaddon.
Therefor a general readpermission would be a good solution.

In case of apcups we would otherwise be forced to put the apcups user 
into the mailgroup.

Anyway, if this is not the solution, please delete the patch and we try 
to find another solution.
Alex

>> FIXES: #12403
>> ---
>> lfs/dma | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/lfs/dma b/lfs/dma
>> index aceb2704e..6b5d9bfbf 100644
>> --- a/lfs/dma
>> +++ b/lfs/dma
>> @@ -24,7 +24,7 @@
>>
>> include Config
>>
>> -VER        = 0.12
>> +VER        = 0.13
>>
>> THISAPP    = dma-$(VER)
>> DL_FILE    = $(THISAPP).tar.gz
>> @@ -80,6 +80,7 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
>> 	install -v -m 755 $(DIR_SRC)/config/dma/dma-cleanup-spool /usr/sbin
>> 	chown -R nobody.nobody /var/ipfire/dma
>> 	chown nobody.root /var/ipfire/dma/auth.conf
>> +	chmod 644 /var/ipfire/dma/auth.conf
>> 	ln -svf dma /usr/sbin/sendmail.dma
>> 	/usr/sbin/alternatives --install /usr/sbin/sendmail sendmail /usr/sbin/sendmail.dma 20
>> 	@rm -rf $(DIR_APP)
>> -- 
>> 2.17.1
>>


  reply	other threads:[~2020-05-11  9:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09  6:06 Alexander Marx
2020-05-11  8:35 ` Michael Tremer
2020-05-11  9:02   ` Alexander Marx [this message]
2020-05-11  9:04     ` Michael Tremer

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=d9da1fe5-fec8-604c-e559-5dc2349619ce@ipfire.org \
    --to=alexander.marx@ipfire.org \
    --cc=development@lists.ipfire.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