Re: [suse-security] cannot access ftp server -- getpeername (in.ftpd): Transport endpoint is not connected
Hi, Thank you for the hints. Will tell you when the problem is actually solved. Currently, I am using proftpd in standalone as a workaround. Just like the standard in.ftpd, proftpd did not work in inetd mode; in standalone, it does. So I will try to fix inetd when I have more time. Cheers Matthias ----- Original Message ----- From: "Carlos E. R." <robin1.listas@tiscali.es> To: "SLE" <suse-linux-e@suse.com> Cc: "Matthias Hupp" <mhupp@gmx.de> Sent: Wednesday, May 19, 2004 3:30 AM Subject: Re: [suse-security] cannot access ftp server -- getpeername (in.ftpd): Transport endpoint is not connected El 2004-05-18 a las 12:07 +0800, Matthias Hupp escribió:
1) Run fsck on all partitions, maybe there was some damage. *** That was done already shortly after the incident...
I suppose so; but any way, run it manually, from the rescue CD, spscially if there is a reiser partition somewhere.
*** 2) maybe there was a configuration change time ago, that did not get activated because the services afected were not restarted at the time, till this forced reboot. *** That is theoretically possible. Still clueless, though...
Configuration file for ftp server, /etc/host*, resolv, dns files and server (if present)... firewall files... password/groups files... -- Saludos Carlos Robinson
On Sat, May 22, 2004 at 09:43:25PM +0800, Matthias Hupp wrote:
Currently, I am using proftpd in standalone as a workaround. Just like the standard in.ftpd, proftpd did not work in inetd mode; in standalone, it does. So I will try to fix inetd when I have more time.
/etc/inetd.conf should contain a line like this: ftp stream tcp nowait root /usr/sbin/tcpd in.ftpd -- Stefan Tichy ( s.list at pi4tel dot de )
I know; that is what I commented out so I could bind proftpd to port 21 in standalone mode. ----- Original Message ----- From: "Stefan Tichy" <nobody@localhost.invalid> To: <suse-security@suse.com> Sent: Sunday, May 23, 2004 1:57 AM /etc/inetd.conf should contain a line like this: ftp stream tcp nowait root /usr/sbin/tcpd in.ftpd
From: "Stefan Tichy" <nobody@localhost.invalid> Sent: Saturday, May 22, 2004 7:57 PM Hi,
On Sat, May 22, 2004 at 09:43:25PM +0800, Matthias Hupp wrote:
Currently, I am using proftpd in standalone as a workaround. Just like the standard in.ftpd, proftpd did not work in inetd mode; in standalone, it does. So I will try to fix inetd when I have more time.
/etc/inetd.conf should contain a line like this:
ftp stream tcp nowait root /usr/sbin/tcpd in.ftpd
but shouldn't it look like this: in /etc/inetd.conf ftp stream tcp nowait root /usr/sbin/tcpd /usr/local/sbin/proftpd and in /usr/local/etc/proftpd.conf ServerType inetd to start proftpd in inetd mode? c y Torsten
-- Stefan Tichy ( s.list at pi4tel dot de )
*** ----- Original Message ----- From: "T. E." <pelegrine@hotmail.com> To: <suse-security@suse.com> Sent: Sunday, May 23, 2004 4:24 PM but shouldn't it look like this: in /etc/inetd.conf ftp stream tcp nowait root /usr/sbin/tcpd /usr/local/sbin/proftpd and in /usr/local/etc/proftpd.conf ServerType inetd to start proftpd in inetd mode? *** Yes. By standard, inetd.conf was set to use in.ftpd. After this started to fail, I changed it to start proftpd from inetd, resulting in the same error messages (ith in.ftpd substituted by proftpd). Now I commented all ftp lines in inetd.conf out and am using proftpd in standalone. Cheers, Matthias
participants (3)
-
Matthias Hupp -
Stefan Tichy -
T. E.