Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] SCP from STDIN: "-t" option undocumented?

In my case, I had a passwordless ssh key, and a validate-rsync script
to use in the key's "command=" prefix in the authorized_keys file.
I wanted to allow the same key to accept scp as well as rsync.
I discovered the -t option when I had the validate-rsync script write
the $SSH_ORIGINAL_COMMAND to a logfile in order to determine
how scp works behind the scenes.

On Fri, Dec 23, 2011 at 2:59 PM, Jerry Feldman <gaf at> wrote:

> The issue IMHO, is the lack of documentation for the -t option. I feel
> that every interface should be documented. As a programmer I am used to
> APIs. Historically, my colleagues find hidden APIs, and use them for
> either because they are there or because they might be more efficient.
> How many programs have been written to use undocumented APIs
> only to crash when the vendor changes the API without notice.

John Abreau / Executive Director, Boston Linux & Unix
Email jabr at / WWW / PGP-Key-ID 0xD5C7B5D9
PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /