VSFTPD et comptes locaux de la machine

Bonjour a tous,

J’essaye de permetre aux comptes locaux de la machine de pouvoir se connecter à vsftpd, mais sa ne fonctionne qu’avec le premier comptes user que j’ai crée ( à savoir le miens ), tous les comptes crée ensuite ne peuvent pas se logger . . .

mon fichier de conf :

[code]listen=YES
anonymous_enable=NO

Uncomment this to allow local users to log in.

local_enable=YES

Uncomment this to enable any form of FTP write command.

#write_enable=YES

Activate directory messages - messages given to remote users when they

go into a certain directory.

dirmessage_enable=YES

If enabled, vsftpd will display directory listings with the time

in your local time zone. The default is to display GMT. The

times returned by the MDTM FTP command are also affected by this

option.

use_localtime=YES

Activate logging of uploads/downloads.

xferlog_enable=YES

Make sure PORT transfer connections originate from port 20 (ftp-data).

connect_from_port_20=YES

If you want, you can arrange for uploaded anonymous files to be owned by

a different user. Note! Using “root” for uploaded files is not

recommended!

#chown_uploads=YES
#chown_username=whoever

You may override where the log file goes if you like. The default is shown

below.

xferlog_file=/var/log/vsftpd.log

If you want, you can have your log file in standard ftpd xferlog format.

Note that the default log file location is /var/log/xferlog in this case.

#xferlog_std_format=YES

You may change the default value for timing out an idle session.

#idle_session_timeout=600

You may change the default value for timing out a data connection.

#data_connection_timeout=120

It is recommended that you define on your system a unique user which the

ftp server can use as a totally isolated and unprivileged user.

nopriv_user=ftpsecure

Enable this and the server will recognise asynchronous ABOR requests. Not

recommended for security (the code is non-trivial). Not enabling it,

however, may confuse older FTP clients.

#async_abor_enable=YES

By default the server will pretend to allow ASCII mode but in fact ignore

the request. Turn on the below options to have the server actually do ASCII

mangling on files when in ASCII mode.

Beware that on some FTP servers, ASCII support allows a denial of service

attack (DoS) via the command “SIZE /big/file” in ASCII mode. vsftpd

predicted this attack and has always been safe, reporting the size of the

raw file.

ASCII mangling is a horrible feature of the protocol.

#ascii_upload_enable=YES
#ascii_download_enable=YES

You may fully customise the login banner string:

#ftpd_banner=Welcome to blah FTP service.

You may specify a file of disallowed anonymous e-mail addresses. Apparently

useful for combatting certain DoS attacks.

#deny_email_enable=YES

(default follows)

#banned_email_file=/etc/vsftpd.banned_emails

You may restrict local users to their home directories. See the FAQ for

the possible risks in this before using chroot_local_user or

chroot_list_enable below.

chroot_local_user=YES

You may specify an explicit list of local users to chroot() to their home

directory. If chroot_local_user is YES, then this list becomes a list of

users to NOT chroot().

#chroot_local_user=YES
#chroot_list_enable=YES

(default follows)

#chroot_list_file=/etc/vsftpd.chroot_list

You may activate the “-R” option to the builtin ls. This is disabled by

default to avoid remote users being able to cause excessive I/O on large

sites. However, some broken FTP clients such as “ncftp” and “mirror” assume

the presence of the “-R” option, so there is a strong case for enabling it.

#ls_recurse_enable=YES

Debian customization

Debian customization

Some of vsftpd’s settings don’t fit the Debian filesystem layout by

default. These settings are more Debian-friendly.

This option should be the name of a directory which is empty. Also, the

directory should not be writable by the ftp user. This directory is used

as a secure chroot() jail at times vsftpd does not require filesystem

access.

secure_chroot_dir=/var/run/vsftpd/empty

This string is the name of the PAM service vsftpd will use.

pam_service_name=vsftpd

This option specifies the location of the RSA certificate to use for SSL

encrypted connections.

rsa_cert_file=/etc/ssl/private/vsftpd.pem

Options for SSL

encrypted connections.

ssl_enable=YES
allow_anon_ssl=NO
force_local_data_ssl=YES
force_local_logins_ssl=YES

require_ssl_reuse=NO # Certains clients FTP nécessitent cette ligne

ssl_tlsv1=YES
ssl_sslv2=YES
ssl_sslv3=YES

rsa_cert_file=/etc/ssl/private/vsftpd.cert.pem
rsa_private_key_file=/etc/ssl/private/vsftpd.key.pem

mode passif

pasv_enable=YES
pasv_promiscuous=NO
pasv_min_port=56000
pasv_max_port=57000
port_promiscuous=NO
[/code]

Sachant que j’ai crée chaque nouvel utilisateurs avec la commande

Je ne voit pas ce qui cloche d’autant que dans le fichier de vsftpd le paramètre “enable_local_user=YES” n’est pas commenté… J’ai eu le même phénomène avec proftpd, je fini par me dire que j’ai zapé un truc.

Pouvez m’aider siouplè ?

EDIT : nouveau message d’erreur très exotique

Toujours pas de problème avec mon propre compte user sur cette machine.

ta commande ne créée pas de fichier home pour ton user

donc le serveur ftp ne peut le relier a son home et donc le chrooter

[Edit] j’allais oublier ta commande ne met pas le mot de passe, il faut lui en définir un

[Edit 2] je viens de voir aussi que tu ne lui donner pas d’interpréteur de commande ce qui peut poser probleme

lol ok je m’incline je suis un boulet sur ce coup, je pensait que la création du homedir étant… automatique.

J’avais bien penser au mot de passe par contre :stuck_out_tongue:

Merci !

par contre, je pense que les utilisateurs créés pour le
ftp n’ont pas besoin de shell.
donc /bin/false va très bien. :smiley: