Bug 24542 – Passive ftp doesn't use port 20

Bug 24542 - Passive ftp doesn't use port 20

Summary:	Passive ftp doesn't use port 20

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	ftp (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bernhard Rosenkraenzer
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-01-22 07:16 EST by Olle Hedman
Modified:	2007-04-18 12:30 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-01-22 07:16:33 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Olle Hedman 2001-01-22 07:16:30 EST

I run into trouble when using ftp from a redhat 7.0 server (uname -r 
2.2.16-22) to another linux machine (uname -r 2.2.12-20). After login I 
try a "ls", thus using passive ftp, and find that the redhat 7.0 machine 
is using an arbitray high port instead of port 20. This will cause 
problems with firewalls. 

The behavior is as follows:
ftp> ls
227 Entering Passive Mode (IP for the "other linux machine",port)
where it should be:
ftp> ls
227 Entering Passive Mode (IP for the "redhat 7.0 server",port)

Comment 1 Bernhard Rosenkraenzer 2001-01-22 07:56:02 EST

This is not a bug, but an RFC compliant security fix.
You need to update either the ftp server or the firewall (probably the latter).

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