Selvom "anon_upload_enable" som standard er NO, så kan jeg ikke få lov og skrive "anon_upload_enable=NO" i konfigurationen, og det ville jeg gerne for at undgå misforståelser. vsftpd nægter at starte hvis den er sat, og den skriver hverken en fejl i terminalen når jeg prøver, eller i logfilen.
Er der nogen der kender grunden?
Pt. ser konfiggen sådan her ud
Kode: Vælg alt
# Run standalone? vsftpd can run either from an inetd or as a standalone
# daemon started from an initscript.
listen=YES
listen_port=21
anonymous_enable=YES
no_anon_password=YES
anon_root=/home/ftp
# anon_upload_enable=NO
anon_mkdir_write_enable=NO
# Uncomment this to allow local users to log in.
local_enable=NO
write_enable=NO
dirmessage_enable=NO
use_localtime=NO
# Activate logging of uploads/downloads.
xferlog_enable=YES
xferlog_std_format=YES
xferlog_file=/var/log/vsftpd.log
# Make sure PORT transfer connections originate from port 20 (ftp-data)
connect_from_port_20=YES
# You may change the default value for timing out
idle_session_timeout=120
data_connection_timeout=300
accept_timeout=60
connect_timeout=60
anon_max_rate=200000
# 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=ftpuser
# 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=NO
# You may fully customise the login banner string
ftpd_banner=aptget reporting in
# 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