Once upon a time, Timo Sirainen said:
> On Sun, 2010-02-07 at 12:02 -0600, Chris Adams wrote:
> > > Also v2.0 handles this by copying the parent directory's permissions.
>
> Oh, actually I lied. When creating mailbox directories, it copies the
> permissions from mail root directory. But if the ma
On Sun, 2010-02-07 at 12:02 -0600, Chris Adams wrote:
> > Also v2.0 handles this by copying the parent directory's permissions.
Oh, actually I lied. When creating mailbox directories, it copies the
permissions from mail root directory. But if the mail root doesn't
exist, it's created with 0700. I
Once upon a time, Timo Sirainen said:
> On Fri, 2010-02-05 at 11:20 -0600, Chris Adams wrote:
> > If a user doesn't have a ~/mail directory and logs in, the directory is
> > created for them. However, it is created with insecure permissions,
> > 0770 (full group access).
> >
> > The problem is t
On Fri, 2010-02-05 at 11:20 -0600, Chris Adams wrote:
> If a user doesn't have a ~/mail directory and logs in, the directory is
> created for them. However, it is created with insecure permissions,
> 0770 (full group access).
>
> The problem is this bit in src/lib-storage/index/mbox/mbox-storage.
If a user doesn't have a ~/mail directory and logs in, the directory is
created for them. However, it is created with insecure permissions,
0770 (full group access).
The problem is this bit in src/lib-storage/index/mbox/mbox-storage.c:
#define CREATE_MODE 0770 /* umask() should limit it more
