Es kann keine Verbindung mit der vsftpd-Instanz hergestellt werden, die auf Centos 7 von xinetd verwaltet wird

740
Hosty

Ich versuche, eine Instanz von vsftpd auszuführen und habe zusätzliche Zugriffskontrollen und Protokollierungen von xinetd.

Auf der VM, auf der beide Dienste ausgeführt werden, kann ich erfolgreich eine FTP-Verbindung initiieren und Dateien sowohl an Port 21 als auch an Port 14121 bearbeiten (wo xinetd zu hören ist). Wenn ich jedoch versuche, eine FTP-Verbindung von einem anderen Computer aus zu initiieren, tritt das folgende Problem auf:

ftp 192.168.188.149 14121 Connected to 192.168.188.149. 220 (vsFTPd 3.0.2) Name (192.168.188.149:user): [username here] 331 Please specify the password. Password: 230 Login successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> ls 500 Illegal PORT command. ftp: bind: Address already in use ftp> pass Passive mode on. ftp> ls 227 Entering Passive Mode (127,0,0,1,166,186). ftp: connect: Connection refused 

Meine Firewall ist wie folgt konfiguriert:

# firewall-cmd --list-all public (active) target: default icmp-block-inversion: no interfaces: ens33 sources:  services: dhcpv6-client ssh ports: 80/tcp 443/tcp 14121/tcp protocols:  masquerade: no forward-ports:  source-ports:  icmp-blocks:  rich rules:   # netstat -ant Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State  tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN  tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN  tcp 0 0 192.168.122.1:53 0.0.0.0:* LISTEN  tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN  tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN  tcp 15 0 127.0.0.1:52432 127.0.0.1:21 CLOSE_WAIT  tcp 15 0 127.0.0.1:44080 127.0.0.1:14121 CLOSE_WAIT  tcp6 0 0 ::1:25 :::* LISTEN  tcp6 0 0 :::443 :::* LISTEN  tcp6 0 0 :::14121 :::* LISTEN  tcp6 0 0 :::80 :::* LISTEN  tcp6 0 0 :::22 :::* LISTEN  tcp6 0 0 ::1:631 :::* LISTEN  

Meine Datei xinetd.conf ist wie folgt konfiguriert:

defaults { # The next two items are intended to be a quick access place to # temporarily enable or disable services. # # enabled = # disabled =  # Define general logging characteristics. log_type = SYSLOG authpriv log_on_failure = HOST log_on_success = PID HOST DURATION EXIT  # Define access restriction defaults # # no_access = # only_from = # max_load = 0 cps = 50 10 instances = 50 per_source = 10  # Address and networking defaults # # bind = # mdns = yes v6only = no  # setup environmental attributes # # passenv = groups = yes umask = 002  # Generally, banners are not used. This sets up their global defaults # # banner = # banner_fail = # banner_success = }  includedir /etc/xinetd.d 

Die xinetd-Konfigurationsdatei für vsftpd ist wie folgt konfiguriert

service FTP { disable = no type = UNLISTED wait = no user = root server = /usr/sbin/vsftpd socket_type = stream protocol = tcp port = 14121 redirect = 127.0.0.1 21 log_on_success = PID HOST DURATION EXIT log_on_failure += HOST cps = 5 30 } 

Schließlich ist meine vsftpd-Konfiguration wie folgt:

# Example config file /etc/vsftpd/vsftpd.conf # # The default compiled in settings are fairly paranoid. This sample file # loosens things up a bit, to make the ftp daemon more usable. # Please see vsftpd.conf.5 for all compiled in defaults. # # READ THIS: This example file is NOT an exhaustive list of vsftpd options. # Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd's # capabilities. # # Allow anonymous FTP? (Beware - allowed by default if you comment this out). anonymous_enable=NO # # Uncomment this to allow local users to log in. # When SELinux is enforcing check for SE bool ftp_home_dir local_enable=YES # # Uncomment this to enable any form of FTP write command. write_enable=YES # # Default umask for local users is 077. You may wish to change this to 022, # if your users expect that (022 is used by most other ftpd's) local_umask=022 # # Uncomment this to allow the anonymous FTP user to upload files. This only # has an effect if the above global write enable is activated. Also, you will # obviously need to create a directory writable by the FTP user. # When SELinux is enforcing check for SE bool allow_ftpd_anon_write, allow_ftpd_full_access #anon_upload_enable=YES # # Uncomment this if you want the anonymous FTP user to be able to create # new directories. #anon_mkdir_write_enable=YES # # Activate directory messages - messages given to remote users when they # go into a certain directory. dirmessage_enable=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/xferlog # # 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 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(). # (Warning! chroot'ing can be very dangerous. If using chroot, make sure that # the user does not have write access to the top level directory within the # 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 # # When "listen" directive is enabled, vsftpd runs in standalone mode and # listens on IPv4 sockets. This directive cannot be used in conjunction # with the listen_ipv6 directive. listen=YES # # This directive enables listening on IPv6 sockets. By default, listening # on the IPv6 "any" address (::) will accept connections from both IPv6 # and IPv4 clients. It is not necessary to listen on *both* IPv4 and IPv6 # sockets. If you want that (perhaps because you want to listen on specific # addresses) then you must run two copies of vsftpd with two configuration # files. # Make sure, that one of the listen options is commented !! listen_ipv6=NO  pam_service_name=vsftpd userlist_enable=YES tcp_wrappers=YES allow_writeable_chroot=YES pasv_enable=YES 

Ich habe versucht:

  • Ändern des listen-Parameters in vsftpd.conf (nein und ja)

  • Festlegen eines passiven Portbereichs und Weiterleiten von xinetd an diesen Bereich

  • Port 21 öffnen und direkt mit vsftpd verbinden

  • Einen anderen FTP-Client verwenden (Filezilla)

  • Vsftpd explizit an localhost binden

Bisher hat keine dieser Methoden zu einer erfolgreichen externen Verbindung geführt, was zur Auflistung oder Manipulation von Dateien geführt hat.

1

0 Antworten auf die Frage