|
More information: In 0.6.0rc1 I could use WSAAsyncSelect to determine when a client was connecting, but in 0.6.4 I can't. I rewrote the code around the ssh_bind_listen() to useĀ select() instead and now things are MOSTLY working. I am still getting client (putty) disconnects with "Incoming packet was garbled on decryption" during the key exchange. I wrote a NodeJS SSH2 client to test with also, and it is throwing an exception stating "Bad packet length". On 4/6/2015 6:31 PM, Kevin Stewart
wrote:
I developed a Windows-based (using VS2010) server application using the 0.6.0rc1 version of libssh and was getting memory leaks on a per connection basis. I decided to migrate to the latest version (0.6.4) to see if it alleviated these leaks and ran into different issues. The first issue is in socket.c starting at line 314. --
|
Title: Snippet
- Errors after migrating from 0.6.0rc1 to 0.6.4 Kevin Stewart
- Re: Errors after migrating from 0.6.0rc1 to 0.6.4 Kevin Stewart
- Re: Errors after migrating from 0.6.0rc1 to 0.6... Andreas Schneider
- Re: Errors after migrating from 0.6.0rc1 to... Kevin Stewart
