H
Hasani
Are there any plans to add a SSL Socket class in any future versions of the
..net framework?
..net framework?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
P
Pieter Philippaerts
Hasani said:Are there any plans to add a SSL Socket class in any future versions of the
.net framework?
Given the pressure from the community, I'm sure they'll add it in one of the
next versions of the framework. I've heard that the next version of the
framework contains some significant improvements in the System.Security.*
namespace, but I'm not sure if an SSL socket is one of those improvements.
That said, there's already an implementation of a SecureSocket that works on
the current versions of the framework. You can download this library from
http://www.mentalis.org/soft/projects/seclib/ It supports SSL3 and TLS1.
Regards,
Pieter Philippaerts
Managed SSL/TLS: http://www.mentalis.org/go.php?sl
H
Hasani
Thx Pieter, I was actually looking in to your product. I can't really use it
yet because my code is @ work and I forgot the login to my remote acct =/
But I was browsing briefly through the documentation for the secure sockets
class and it looks like a very robust product, at least for the 1 or 2
classes I will end up using. Unfortunately, I don't know how SSL (public
keys, private keys...???!?!) works. I just need it because I need send data
over a secure connection. I did post a similar question on your forums
though. Thx for the quick response here.
yet because my code is @ work and I forgot the login to my remote acct =/
But I was browsing briefly through the documentation for the secure sockets
class and it looks like a very robust product, at least for the 1 or 2
classes I will end up using. Unfortunately, I don't know how SSL (public
keys, private keys...???!?!) works. I just need it because I need send data
over a secure connection. I did post a similar question on your forums
though. Thx for the quick response here.
J
Jason Smith
Https works beautifully in .NET just using the standard Http classes. You
just specify "https://..." and away you go. As far as I know, this only
works for HTTP protocol though.
If you can use a web server on the back end, it is quite easy to exchange
data between two machines using SSL (https) and Web Services. You don't get
the full messaging ability that you get with true TCP, but it works for a
lot of different real world business problems. If you can use Web Services
and let the web server take care of the SSL, you will save yourself a lot of
time and headaches down the road.
just specify "https://..." and away you go. As far as I know, this only
works for HTTP protocol though.
If you can use a web server on the back end, it is quite easy to exchange
data between two machines using SSL (https) and Web Services. You don't get
the full messaging ability that you get with true TCP, but it works for a
lot of different real world business problems. If you can use Web Services
and let the web server take care of the SSL, you will save yourself a lot of
time and headaches down the road.