|
|
Forums -> Security Library Forum
| Secure Client Blocked after handshaking |
|
|
by Germen [germen at astri dot org]
posted on 2003/08/17 |
|
I am trying to connect a Secure Server using this security lib. I have successfully start the connect and verify the server.
However the client is blocked at this location (SocketController.cs:206):
if (!ret.AsyncResult.IsCompleted)
ret.AsyncResult.AsyncWaitHandle.WaitOne();
From the WriteLine trace, I found that the handshaking process has been finsihed successfully. The processFinished method in ClientHandShakingLayer has bee called.
Do you have any hints to avoid this block?
Regards,
Germen
|
by Pieter Philippaerts [Pieter at mentalis dot org]
posted on 2003/08/18 |
|
What version of the Security Library are you using? We've uploaded a new version yesterday that fixes a deadlock problem, so maybe it's this problem you're seeing if you're using an older version. The latest version is 1.0.13.669.
If you're using the latest version, can you send me the hostname you're trying to connect to, so I can try to reproduce the problem on my computer? |
by Germen
posted on 2003/08/18 |
|
I've sent u email thanks!
|
by Pieter Philippaerts [Pieter at mentalis dot org]
posted on 2003/08/19 |
|
Apparently, your client and server are using a different protocol to talk to each other, and this is where your problem arises.
The server appears to be an echoing server; it waits for input and sends the input back to the client.
The client is some kind of FTP client. Because the FTP protocol specifies that the FTP server should send the first message, your client waits until it receives a message, but it will never receive a message because the server is waiting also.
This is why both programs are blocked; they're simply waiting on each other to send the first message.
After making some modifications to your client, the code works perfectly. |
|
|
