Bug 54405 - all port numbers above 32768 erroneously report
Summary: all port numbers above 32768 erroneously report
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ftp
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2001-10-06 05:34 UTC by Need Real Name
Modified: 2008-05-01 15:38 UTC (History)
0 users

Clone Of:
Last Closed: 2001-10-06 05:34:29 UTC

Attachments (Terms of Use)

Description Need Real Name 2001-10-06 05:34:24 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0b; Windows NT 5.0; DigExt)

Description of problem:
Works fine in 6.1, but now in 7.1
ftp -i 50000
gives that error message.

I think someone must have messed with the code, and accidentally change 
the data type to "signed int" - beats me *why* anyone would be messing 
with this, and make such a silly mistake, and it would get past the 
quality control test suite... there *is* a quality-control test suite, 
isn't there?

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

How reproducible:

Steps to Reproduce:
1. ftp -i 50000

Actual Results: bad port number-- 50000

Expected Results:  connected to my ftp server which runs on port 50000

Additional info:

works fine in RedHat 6.1.

Possible security implications:
1. Why did it get changed such that it got broken?  perhaps a diff of the 
6.1 and 7.1 source should be examined for other messups?
2. Since this paramater is obviously not being checked proplery, is there 
something here, or new, that could lead to a buffer problem?

Comment 1 Bernhard Rosenkraenzer 2001-10-23 14:45:10 UTC
I can't reproduce this on a 7.2 system

[bero@spock bero]$ ftp localhost 50000
Connected to localhost (
220 spock.home.bero.org FTP server (Version wu-2.6.1-18) ready.
Name (localhost:root):

Comment 2 Bernhard Rosenkraenzer 2001-10-23 14:46:06 UTC
(and yes, there is a QA test suite. But it didn't check for this. It just does 
a couple of standard ftp transfers, port 21)

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