Bug 820876 - vsftpd DNS lookup cannot be disabled
vsftpd DNS lookup cannot be disabled
Status: CLOSED DUPLICATE of bug 752954
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vsftpd (Show other bugs)
6.2
All Linux
unspecified Severity medium
: rc
: ---
Assigned To: Jiri Skala
BaseOS QE Security Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-11 05:30 EDT by Sebastien Caps
Modified: 2014-11-09 17:35 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-05-11 06:15:57 EDT
Type: Bug
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 Sebastien Caps 2012-05-11 05:30:33 EDT
Description of problem:
vsftpd DNS lookup cannot be disabled.
This bug have been resolv in 5.x with the option 'reverse_lookup_enable'
but in 6.2 this option is no longer available

https://rhn.redhat.com/errata/RHBA-2009-1282.html :
...
* the DNS reverse lookup feature was implemented without any way to disable
it. This update contains the parameter 'reverse_lookup_enable', which
allows users to enable or disable the DNS reverse lookup functionality.
(BZ#498548) 
...
Version-Release number of selected component (if applicable):
rpm -qi vsftpd
Name : vsftpd Relocations: (not relocatable)
Version : 2.2.2 
Release : 6.el6_2.1

How reproducible:
ALWAYS
Steps to Reproduce:
1. having 2(or more) nameserver in /etc/resolv.conf that is NOT reachable
2. and then try to connect to the ftp server.
  
Actual results:
Connection timed out

Expected results:
Connection succesfull

Additional info:
trying with "reverse_lookup_enable=NO"
service vsftpd restart
Shutting down vsftpd: [FAILED]
Starting vsftpd for vsftpd: 500 OOPS: unrecognised variable in config file: reverse_lookup_enable
                                                           [FAILED]
Comment 2 Jiri Skala 2012-05-11 06:15:57 EDT
The fix will be available in the next update 6.3.

*** This bug has been marked as a duplicate of bug 752954 ***

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