Bug #2270

dma 0.7

Added by t_dfbsd over 1 year ago. Updated over 1 year ago.

Status:Closed Start date:
Priority:Normal Due date:
Assignee:swildner % Done:

0%
Category:-
Target version:-

Description

DF 2.13.0.809

- In the man page, change references to "three config files" to "two config
files" now that virtualtable is gone.

- Sending an email using "mail" as root throws this error, which appears to
be coming from dma:
send-mail: cannot drop root privileges: unknown error:

Tim

0001-dma.8-dma-uses-two-configuration-files.patch (644 Bytes) herrgard, 01/07/2012 03:18 am

0002-dma.h-change-DMA_ROOT_USER-to-mailnull.patch (632 Bytes) herrgard, 01/07/2012 03:18 am

0003-dma.8-dma-uses-two-configuration-files.patch (861 Bytes) herrgard, 01/08/2012 03:51 am

Related todos

History

#1
Updated by herrgard over 1 year ago

It cannot drop root privileges because you have no "mail" user. So you can either add one, or change #define DMA_ROOT_USER "mail" in libexec/dma/dma.h to use "mailnull", which is an user we have for sendmail.

Swildner seemed to think we should change drop group to mailnull as well. We have both mail and mailnull groups.

#2
Updated by herrgard over 1 year ago

However, if we change the group to mailnull, we must change group ownership of /etc/dma/dma.conf to mailnull as well.

#4
Updated by herrgard over 1 year ago

Sorry Tim, I accidentally deleted your last message. Here it is though:

> On Fri, Jan 6, 2012 at 6:46 PM, Tim Darby <t+dfbsd@timdarby.net> wrote:
>
> > DF 2.13.0.809
> >
> > - In the man page, change references to "three config files" to "two
> > config files" now that virtualtable is gone.
> >
> > - Sending an email using "mail" as root throws this error, which appears
> > to be coming from dma:
> > send-mail: cannot drop root privileges: unknown error:
> >
> > Tim
> >
>
> it appears that I'm registered in Redmine from having previously reported
> bugs, but don't know my password. I tried to use the Lost Password link,
> but when I get to the step of entering a new password, I get these messages:
>
> Last name can't be blank
> Login is invalid
>
> Anyway, thanks, the patch worked! In the man page, there is another
> reference to "three" files that needs to be changed.
>
> Tim

And here is a the new correct patch.

#5
Updated by t_dfbsd over 1 year ago

  • Status changed from New to Resolved

Thanks, it looks good and my login works now.

#6
Updated by swildner over 1 year ago

  • Status changed from Resolved to In Progress
  • Assignee set to swildner

grab

#7
Updated by swildner over 1 year ago

  • Status changed from In Progress to Closed

Also available in: Atom PDF