Bug 142805 - bad (old place) path in pam file for vsftpd
Summary: bad (old place) path in pam file for vsftpd
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: vsftpd   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Radek Vokal
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-12-14 10:40 UTC by Anton Guda
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-12-14 11:29:51 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Use new file place in pam file for vsftpd (473 bytes, patch)
2004-12-14 10:42 UTC, Anton Guda
no flags Details | Diff

Description Anton Guda 2004-12-14 10:40:12 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux; X11; ru) (KHTML, like Gecko)

Description of problem:
Such string exist in /etc/pam.d/vsftpd:
auth required pam_listfile.so item=user sense=deny 
 file=/etc/vsftpd.ftpusers onerr=succeed

This prevents from checking for disallowed users.

New ftpusers file is in /etc/vsftpd/

Patch proposed.

Version-Release number of selected component (if applicable):
vsftpd-2.0.1-6

How reproducible:
Always

Steps to Reproduce:
1. Launch vsftpd or tell xinetd to launch it on request (with pam   in config).
2. Connect to it with any ftp client.
3. Watch in log about missing /etc/vsftpd.ftpusers file
    

Actual Results:  vsftpd (really pam) tryes to file file on old place

Expected Results:  It must use new file place.

Additional info:

Comment 1 Anton Guda 2004-12-14 10:42:12 UTC
Created attachment 108501 [details]
Use new file place in pam file for vsftpd

Comment 2 Radek Vokal 2004-12-14 11:29:51 UTC
Thanks, I've missed this one. Fixed in vsftpd-2.0.1-7.


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