Date: Thu, 29 Aug 2002 12:49:03 -0700 (PDT) From: Ted Mittelstaedt <tedm@toybox.placo.com> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/42172: ftp and fetch client needs an active command line option now Message-ID: <200208291949.g7TJn3J2026751@www.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 42172
>Category: misc
>Synopsis: ftp and fetch client needs an active command line option now
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Aug 29 13:00:15 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Ted Mittelstaedt
>Release: 4.6-RELEASE
>Organization:
Cool Dudes Inc.
>Environment:
N/A
>Description:
Several FreeBSD versions ago the ftp client in FreeBSD was
modified to default to Passive mode, rather than active mode. This was
a good thing because so many FTP sites these days are behind
restrictive firewalls that don't permit active FTP.
However, the problem is that nobody thought about the -p
option. According to the manual, -p means "start in passive mode"
This is now unnecessary. Instead, we need an option, such as -c,
that makes FTP start in active mode. I'd assume that we want to
leave -p in there just to keep anyone's scripts from breaking, even
though it now does nothing.
Now, I know that most people are going to be saying "so what,
all FTP servers support passive mode" but au-contraire, that is not
true. I ran across one that ONLY supports ACTIVE mode FTP - it is
a network storage device called a "Snap!" server, manufactured by
Quantum. The lack of an active switch makes it rather difficult to
write scripts that deal with this device.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200208291949.g7TJn3J2026751>