Re: [Proftpd-user] Directory and umask problems

[Yoann M. <inf...@mi...>]

Le lundi 26 juillet 2010 à 14:08 -0700, TJ Saunders a écrit :
> > Directories into "data/" have the good rights but not the "data/"
> > directory itself, like, I had done "/home/user/monsite/*/data/*"
> > 
> > here the commands I did[3] and the result, and below, log debug server
> > side[4], client side[5] and conf file[6]
> > 
> > 3.http://file.mistur.org/proftpd/command_result.log
> > 4.http://file.mistur.org/proftpd/serveur-debug.log
> > 5.http://file.mistur.org/proftpd/client-debug.log
> > 6.http://file.mistur.org/proftpd/proftpd.conf
> > 
> > the default umask is 027 and the custom umask is 007.
> > 
> > /home/user/monsite/dir1/data should have rwxrwx---, isn't it ? 
> > 
> > cf [1] : "Then that Umask value will be used within the
> > "/path/to/dir/subdir/" directory as well."
> > 
> > to match only subdir, I should add "/* at the end.
> > 
> > cf [1] "applies the section's configuration directives only to the
> > contents of dir, not to the directory itself."
> > 
> > and
> > 
> > /home/user/monsite/dir2/dir22/data/dir221 souldn't have rwxrwx--- 
> > 
> > cf [1] : "since * does not expand to some/other/ or /some/other/level/;
> > they cover multiple levels."
> > 
> > maybe I misunderstand the doc, but if not maybe it's a bug in the
> > interpretation of the regexp.
> 
> I tracked this down; turns out to be a bug in how proftpd is matching the 
> given path against the various <Directory> patterns.  I've opened a bug 
> report for this:
> 
>   http://bugs.proftpd.org/show_bug.cgi?id=3491

it works if I have only one <Directory> occurrence, as soon as I have a
second one[1], the umask is set u 007 for everything, as you can see in
the log[2]

<Directory /home/user/monsite/*/data>
        Umask 007 007
</Directory>

<Directory /home/user/monsite2/dir1/data>
        Umask 0007 0007
</Directory>

1. http://file.mistur.org/proftpd/proftpd2.conf
2. http://file.mistur.org/proftpd/serveur-debug2.log


[...] dispatching PRE_CMD command 'MKD /home/user/monsite/dir1' to mod_core
[...] dispatching CMD command 'MKD /home/user/monsite/dir1' to mod_core
[...] in dir_check_full(): path = '/home/user/monsite/dir1', fullpath = '/home/user/monsite/dir1'.
[...] in dir_check_full(): setting umask to 0007 (was 0027)
[...] dispatching LOG_CMD command 'MKD /home/user/monsite/dir1' to mod_log

/home/user/monsite/dir1 does not match any of the 2 rules below.

Cheers,

Yoann Moulin