Bug 76944 - RFE : replace vsftpd-1.1.0 with vsftpd-1.1.2
RFE : replace vsftpd-1.1.0 with vsftpd-1.1.2
Product: Red Hat Linux
Classification: Retired
Component: vsftpd (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Mike McLean
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2002-10-29 16:51 EST by Peter van Egdom
Modified: 2014-03-16 22:32 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-12-13 19:28:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Peter van Egdom 2002-10-29 16:51:37 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
According to : ftp://vsftpd.beasts.org/users/cevans/

A newer version of vsftpd is out. This new version gets rid of the
      "220 ready, dude (vsFTPd 1.1.0: beat me, break me)" 

message that appears after logging in.

Of course, geeks & hackers love these kind of messages, but the pointy
haired managers don't seem to 'get' the humor involved. :-)

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

How reproducible:

Steps to Reproduce:
1. Enable ftp daemon in "/etc/xinet.d/vsftp"
2. "ftp localhost"
3. observe.

Actual Results:  "220 ready, dude (vsFTPd 1.1.0: beat me, break me)"

Expected Results:  "(vsFTPd 1.1.2)"

Additional info:

Comment 1 R P Herrold 2002-11-12 14:00:27 EST
Actually it appears that
ftp://vsftpd.beasts.org/users/cevans/vsftpd-1.1.3.tar.gz is out as well.

I get a clean compile and run with a simple substitution in ~/redhat/SOURCS/ and
a trivial edit to the .spec file.

Existing patches apply cleanly.

[herrold@ftp dl]$ ftp localhost
Connected to localhost (
220 (vsFTPd 1.1.3)
Name (localhost:herrold): asdf
331 Please specify the password.
530 Login incorrect.
Login failed.
Comment 2 Bill Nottingham 2002-12-13 19:28:55 EST
1.1.3-1 built.

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