Bug 130119 - Update from FC1 to FC2 overwrites the Home dir of the ftp user in /etc/passwd
Summary: Update from FC1 to FC2 overwrites the Home dir of the ftp user in /etc/passwd
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: vsftpd
Version: 2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Radek Vokál
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-08-17 10:25 UTC by Joachim Backes
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-09-16 08:42:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Joachim Backes 2004-08-17 10:25:02 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

Description of problem:
When updating from FC1 to FC2, the /etc/passwd entry for the anonymous
ftp user is overwritten (more exact: the home dir entry). 

Version-Release number of selected component (if applicable):
krb5-workstation-1.3.3-1

How reproducible:
Always

Steps to Reproduce:
1. Install FC1
2. Configure the anonymous ftp user with a special home dir
3.Update to FC2
    

Actual Results:  /etc/passwd entry will be overwritten

Expected Results:  No changes /etc/passwd entry.

Additional info:

The same problem when updating RH9->FC1

Comment 1 Nalin Dahyabhai 2004-08-23 23:38:51 UTC
The krb5-workstation package (which includes the kerberized ftp
server) doesn't touch the 'ftp' account in its scripts.  Reassigning
to vsftpd.

Comment 2 Radek Vokál 2004-09-15 08:44:29 UTC
vsftpd doesn't modify /etc/passwd while installing. Scripts checked.
Seems to me more like anaconda problem.


Comment 3 Jeremy Katz 2004-09-15 18:43:26 UTC
No, vsftpd does set it

See from its %post -- 
/usr/sbin/usermod -d /var/ftp ftp >/dev/null 2>&1 || :

Comment 4 Radek Vokál 2004-09-16 08:21:01 UTC
You're right (Thx Jeremy). The home directory is changed to default
dir. Anyway I don't see any reason why it is changed so I'll remove it
from next release. 


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