[Bug 2005] scp should not overwrite files (without confirmation)

bugzilla-daemon at bugzilla.mindrot.org bugzilla-daemon at bugzilla.mindrot.org
Thu May 10 23:05:10 EST 2012


--- Comment #3 from Darren Tucker <dtucker at zip.com.au> 2012-05-10 23:05:10 EST ---
it's basically not possible to extend the scp protocol (which is really
just the rcp protocol) without breaking existing implementations.

Here's how it works: the local end runs "scp -t" ("to") or scp -f
("from") on the remote end.  The sending end sends a header that looks
like "C0644 20 foo\n"  where the "C" is the header type, followed by
the file modes, size and name.  The receiving end makes a file with the
specified name and mode and writes the specified number of bytes into
it.  That's it.  No negotiation of any kind.

The only way to change the behaviour is sending an extra command line
switch to the other end, and unless all implementations support it
you've now caused an interop problem.

Also: http://openssh.com/faq.html#2.10

Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.

More information about the openssh-bugs mailing list