Bug 4288 - ftp gives "ftp: ftp/tcp: unknown service" for regular user
ftp gives "ftp: ftp/tcp: unknown service" for regular user
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: ftp (Show other bugs)
6.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-07-31 13:50 EDT by Bertil Askelid
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-08-01 05:02:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bertil Askelid 1999-07-31 13:50:38 EDT
/usr/bin/ftp has to installed with suid bit set:

	chmod 4755 /usr/bin/ftp

Same error occures for telnet and fwhois.
Comment 1 Bertil Askelid 1999-07-31 14:53:59 EDT
My suggested solution is no good. Means that ftp:ed files are owned
by root. Thus, there must be something in the tcp that prevents ftp,
telnet and fwhois to be used by a regular user. But what?
Comment 2 Bertil Askelid 1999-07-31 15:31:59 EDT
Problem solved: /etc/services comes with rw------- on the 6.0 CD.
Should be rw-r--r--.
Comment 3 Bill Nottingham 1999-07-31 17:46:59 EDT
No, it comes with the correct 644 permissions (just checked here.)
Perhaps something else changed them on your system. Did you install
the samba upgrade with a non-default root umask?
Comment 4 Jeff Johnson 1999-07-31 19:03:59 EDT
No, don't put a setuid on the program, check the permissions
on /etc/services. I believe that a recent update (samba?)
changes the permissions to 600 on /etc/servcies. Can you confirm
whether:
   1) you recently installed the samba update.
   2) the permissions are 600 on /etc/services
so I can get this problem fixed? Thanks ...
Comment 5 Jeff Johnson 1999-08-01 05:02:59 EDT
This problem appears to be resolved.

Note You need to log in before you can comment on or make changes to this bug.