bug in scp (OpenSSH)

[Jason Stone]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> >This has come up many times before, and the consensus of the developers
> >seems to be that they're not interested in fixing or adding features to
> >scp because they want to make scp just the secure version of rcp, and it's
> >not up to them to change rcp.
> 
> One thing I have missing from other versions is the throughput meter
> in the status bar.

Incidentally, at my last company, the progress bar was a source of
breakage for legacy scripts that didn't expect rcp to be producing any
output - so what's up with that?  How does that fit into your model of
being rsh/rcp compatible and not introducing extraneous features?  Do you
really think that breaking rcp compatibility with a status bar is a better
idea than "breaking" it with, for example, a flag to allow atomic
transfers?

Don't you think that if the progress bar exists at all, it should at least
be enabled via commandline option or environment variable, and not be the
default?


 -Jason

 -----------------------------------------------------------------------
 I worry about my child and the Internet all the time, even though she's
 too young to have logged on yet.  Here's what I worry about.  I worry
 that 10 or 15 years from now, she will come to me and say "Daddy, where
 were you when they took freedom of the press away from the Internet?"
	-- Mike Godwin

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: See https://private.idealab.com/public/jason/jason.gpg

iD8DBQE7lWXcswXMWWtptckRAgFMAJ4yMVLL21lLMdcEA/voCWYXF7DC0wCfV4Ta
Vt1GGZ4jCc4gx2j7Tl0KJMM=
=/RwG
-----END PGP SIGNATURE-----