Re: [Proftpd-user] Issue configuring ProFTPd

On 20/9/2020 8:27 π.μ., Dieter Bloms via Proftp-user wrote:

> ...
> I hope its help to you in thr right way.
> PS.: is selinux or appamore enabled and blocks the access ?

Hi Dieter,

Thanks for you quick reply!

Following your suggestions, I suspected mod_vroot / VRootEngine 
directive which was by default configured to ON (and I had left it 
unchanged). This was not used at all in my other (earlier) configs!

After I set it to off:

    <IfModule mod_vroot.c>
       VRootEngine off
    </IfModule>

...everything worked fine!

So, it seems currently everything is running smoothly! Thanks for the hint!

I don't know if some additional mod_vroot directive(s) would eventually 
provide a better and safer (but well-working!) environment than the 
current.

The principle in my setup is to chroot to the path indicated by the 
value of the homeDirectory LDAP attribute (in the associated user 
account) and this is accomplished by:

    # Specify ftpuser:nginx uid/gid
    LDAPDefaultUID 500
    LDAPDefaultGID 987

    # Force default (ftpuser:nginx) owner always!
    LDAPForceDefaultUID on
    LDAPForceDefaultGID on

    LDAPGenerateHomedir on
    RequireValidShell   no
    CreateHome on 750 dirmode 750
    DefaultRoot ~

By the way, would you happen to know how we could disable 
systemd/journal-based logging and use the classic SystemLog logging method?

If I simply configure:

    DebugLevel     3
    SystemLog      /var/log/proftpd/proftpd.log

...it's just getting ignored. In fact, an empty file is created indeed, 
but logging continues to be handled exclusively by systemd journal. I 
only get log entries in trace.log (which is configured separately / in 
parallel).

Thank you for your kind help!

Cheers,
Nick



_______________________________________________
ProFTPD Users List   <[email protected]>
Unsubscribe problems?
http://www.proftpd.org/list-unsub.html