Slackware :: VSFTPD User Versus Login Shell Definition

I'm using VSFTPD on my office LAN for one simple task: to receive-and send - installation images created with Ghost4Linux. Until recently, my main LAN server ran on CentOS, but I decided to migrate it to Slackware (nicer release policy ).

What I usually do is create an 'install' user who can login to FTP, but not on the system. Here's an example of what I used to do on my CentOS setup:

Code:

# mkdir -p -m 0700 /home/ftp/install
# groupadd install
# useradd -d /home/ftp/install -g install -s /sbin/nologin install
# chown -R install:install /home/ftp/install
# passwd install

The relevant bits in vsftpd.conf looked like this on the CentOS server:

Code:

...
anonymous_enable=NO
...
userlist_enable=YES
userlist_deny=NO
userlist_file=/etc/vsftpd/user_list
...

Then I only had to create the /etc/vsftpd/user_list file and put a single line in it to allow the newly created user:

Code:

install Now I've tried to get the same behaviour on Slackware, and I succeeded more or less, except for one thing. There's no way my 'install' user can login to FTP when his default shell is set to '/sbin/nologin' (or '/bin/false'). Only when I change the 'install' users' default shell to a "real" shell like '/bin/bash', he's able to login.

Here's a little practical demonstration of what's happening:

Code:

$ lftp localhost
lftp localhost:~> user install
Mot de passe :

[code]...