![]() scp1\'s implementation of server-side wildcards is inherently unsafe. NOTE WELL that this disallows remote-to-local wildcards such as \"pscp server:*.c. It will refuse to let the remote host write to a file that doesn\'t have the same name as the file that was requested. PSCP, in old-style scp1 mode, is now much tighter on security.This should allow it to interoperate cleanly with ssh.com\'s product, and is a security improvement besides. PSCP now uses the new SFTP protocol if possible, and only falls back to the old scp1 form if SFTP can\'t be found (for example, if your connection is SSH-1).We still think RSA is better, and recommend you use it if you have the choice.) Details are in sshdss.c for anyone who\'s interested credit mostly goes to Colin Plumb for letting me know about it. (Yes, I know I\'ve been claiming DSA is horrifically insecure for ages, but now I\'ve been told about a clever way to get round the insecurity.Agent forwarding is supported, but only to OpenSSH servers, because ssh.com have a different agent protocol which they haven\'t published. Support for public keys in SSH-2, both RSA and DSA.A full manual has been written, and is supplied as a Windows Help file alongside the program executables.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |