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 <g...@blu.org> 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 j...@blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9 PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 _______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
