What exactly do you mean by "SSL encrypted"?
If you mean you want your web service to work over https, then this
can be done by putting the web service on a server that is configured
to service https request. This can easily be done using IIS and
creating the correct certificates. After you've set up the server and
web service, then you can create a web service client proxy using the
https:// url, just as you would if the service was located using
http:// url. All web method calls between the web service client and
the web service server will encrypted.
If you mean you want to use the Secure Socket Layer protocol without
using
https://, then this is more challenging, but still possible. I
can think of two ways to do this, both ways invole P/Invoking to OS
level functionality.
1) WINCSOCK has support for implementing a secure socket. This is
commonly known as SO_SECURE. To find out more info you can search MSDN
or Google for SO_SECURE.
2) You can also create a P/Invoke wrapper around the Security Support
Provider Interface API (SSPI). The SSPI API allows you create a seucre
connection using Schannel security package which inturn provides
access to TLS1, SSL2, SSL3, PCT. The providers handle encrypting and
decrypting data that will then send and receive over a raw socket. You
can learn more about SSPI by doing a search on MSDN or Google.
I hope this helps.
//RDY
