However, when i tried to connect from Squeak i received an error ("bad signature") on SSHDHGroup1KeyExchangeProcessor>>processServerDHReplyMsg:securityParams: method on the key exchange phase of the algorithm.
Rob Withers-2 wrote
I wrote the SSH code 3-4 years ago. I got it working with some Linux boxes. The problem you are describing is at the heart of authentication. It is hashing some security parameters and then rehashing that hash and signing it with the private key. This happens on your server. Then the client will also hash the security parameters and then rehash that hash and verify signature with the server generated signature and the public key. This is the point that is failing. The problems could be transmission of security params, changes to hashing in cryptography code in squeak (don't think this has happened), bad public key, perhaps something else.
Can you connect to a different SSH server?
Can you provide me the credentials to connect to your server so I can walk the code? reefedjib at gmail.com, replace the at with @.
I know this is crazy old, but (hoping Rob is still following the list), was this ever resolved?
Thanks, Sean
-- View this message in context: http://forum.world.st/Cryptography-Problem-with-SSH-client-tp2966962p4669964... Sent from the Squeak - Dev mailing list archive at Nabble.com.