Login  
Search All Forums
Dart Home | PowerTCP Sockets for .NET | Custom Development Reply | PowerTCP Sockets for .NET (Secure and Standard) Topics | Forums   
AuthorForum: PowerTCP Sockets for .NET (Secure and Standard)
Topic: SSL Tool and SSL Sockets for ,NET compatibility
Rupert Taylor

From: Brighton, United Kingdom
Posts: 5
Member Since: 05/28/03
posted November 13, 2003 6:24 PM

I have written a server application (running on
Win2K Server) using SSL Sockets .Net (.Net version 1.1). Server object.

I also have a client application (VB6) which uses the SSL Tool SecureTCP object to connect to the server.

The client and the server converse over port 990 and when the Server certificate property is not set and when the client secure protocol property is set to secureNone everything works fine.

When I set the certificate property on the server (to a valid server authentication certificate) and change the client protocol property to any of secureAuto, secureSSL2 or secureSSL3 the client is no longer able to connect to the server and the
clients SecureTCP Authenticate event never fires.

Should this possible, and if so is there anything I need to do to achieve it.

Unfortunately I have no control over the environments that the client will be running in so can not force a .Net solution on them and the server must also accept SSL connections from 1 client that was developed in .Net so I can't use COM interop on the server (using SSL Tool) - unless it works in that direction!

Any help or just a straight "It can't be done" would be gratefully received.

cheers

Rupert
Tony Priest



From: Utica, NY USA
Posts: 8466
Member Since: 04/11/00
posted November 13, 2003 10:09 PM

Did you set the SecureProtocol of the server?
Rupert Taylor

From: Brighton, United Kingdom
Posts: 5
Member Since: 05/28/03
posted November 14, 2003 5:09 AM

The Server Class in SSL Sockets .net does not have a SecureProtocol
property but the TCP class does (although it is not mentioned in the
help file but I can see it in the object browser).

The help file for the server class certificate property states that

"Only use this property if you wish to create a secure server.

When this property is set to a valid certificate, all TCP connections to the server will be sent the certificate for server authentication. If successful, all communication between server and client will occur using SSL.

To change back to non-secure operation, set Server.Certificate to null."

I took this to mean that that was all I had to do - which is currently the case.


To summarise the setup:

Server (.net) - SSL Sockets .Net Server class / Certificate property set.

Client (vb6) - SSL Tool (COM) SecureTCP class with protocol set to secureAuto

Communication on Port 990

Connections OK when Server certificate property not set and client secureprotocol set
to secureNone.

The authenticate event does not fire in vb6 client when the server certificate property
and client secure protocol is set.

Is there something I am missing? Do you need me to post code fragments?

cheers

Rupert
Tony Priest



From: Utica, NY USA
Posts: 8466
Member Since: 04/11/00
posted November 14, 2003 9:00 AM

Sorry. The property I mentioned will be in the next release (look for it in a couple days). We changed it so that you had to set the property as well.

What you are trying to do should be possible. Do the sample apps work?
Reply | PowerTCP Sockets for .NET (Secure and Standard) Topics | Forums   
This site is powered by PowerTCP WebServer Tool PowerTCP WebServer for ActiveX