allowing scp but not ssh (here's how) (WHOOPS)

[jabr at blu.org (John Abreau)]

"Derek D. Martin" <ddm at pizzashack.org> writes:

> This isn't really all that helpful...  What's going on here is the scp
> program (for example) passes the shell on the remote end a command,
> via the -c option to the shell.  The argument that follows the -c is
> intended to be a complete command line, but it's all one argument to the shell.
> I.E. it might look like this:

If it's that much of a pain to deal with, you could always decide to 
forget scp support and handle only sftp. If users are coming in from other
Linux or Unix boxes, their instance of openssh will work fine with it,
and for Windows users, the sftp-server module was originally written
for the F/Secure SFTP and VanDyke SecureFX clients. The sftp client 
component was actually written a little later.

I seem to recall reading in an O'Reilly book that the scp client was
supposed to use the sft-server component. I guess that must have been
just in the commercial version.


-- 
John Abreau / Executive Director, Boston Linux & Unix 
ICQ 28611923 / AIM abreauj / JABBER jabr at jabber.org / YAHOO abreauj
Email jabr at 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

   Some people say, "The enemy of my enemy is my friend."
   I often respond, "When elephants fight, it's the grass
   that gets trampled."



-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 344 bytes
Desc: not available
URL: <http://lists.blu.org/pipermail/discuss/attachments/20020804/d6612b37/attachment.sig>