Re: Passive FTP
Those who still want active FTP (what on earth for?) I have encountered hosting companies in the past that only have inbound port 21 access for security reasons. I think this a bit odd but it is was it is. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Passive FTP
Peter Jeremy peterjer...@acm.org writes: Dag-Erling Smørgrav d...@des.no writes: This overrides both the default setting and fetch(1)'s -p command-line option. I'm less happy with this - my gut feeling in that command-line options should override evnironment variables. This was already the case, just in the other direction. The environment variable overrode the absence of -p, and there was no reverse option, neither on the fetch(1) command line nor in the fetchGetFTP(3) arguments. DES -- Dag-Erling Smørgrav - d...@des.no ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Passive FTP
On 2011-Sep-27 21:53:43 +0200, Dag-Erling Smørgrav d...@des.no wrote: I have therefore flipped the switch and made passive FTP the default. Those who still want active FTP (what on earth for?) can set FTP_PASSIVE_MODE=NO in their environment. I thought I needed it for the $work firewall but some more careful checking shows that it's just EPSV that gives it indigestion. This overrides both the default setting and fetch(1)'s -p command-line option. I'm less happy with this - my gut feeling in that command-line options should override evnironment variables. I configure my environment to suit my general requirements and I override this on a command-by- command basis via command line options if I need to. Are there other commands where the environment overrides the command line? -- Peter Jeremy pgpNMiZ3Kg57b.pgp Description: PGP signature
