I must first tell that im a beginer on security things.
Im building a webserver in c++, for unix, linux and windows. And i wonder if i can use this library to get the webserver to support ssl(https)?.
Or at least understand how to code https support.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2001-04-04
Sorry i didnt read your ISSL+HOWTO.txt first.
I see that you have made your own protocol,
I wonder if their are much to do to modify this protocol to follow the ssl protocol standard??.
Or its maybe better to build a new from scratch??
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think I really should finally answer this because it's a good question. :)
It would take a lot of changes to change issl into a fully ssl(v1/v2) compatible
protocol including cipher negotiation, mutual trust, x509, etc. The main
reason why I say this isn't worth it is because there's a
good alternative already out there: Please try
scl+sssl for this purpose: http://www.freshmeat.net/projects/scl+sssl
I've already talked to the author, and know this project.. this is what you want for a small webserver SSL library.
iSSL will rather help you in designing your very own applications, especially lightweight ones, or fortifying existing protocols for internal use (such as issl-ircd, or issl-opennap, etc. etc.) almst-on-the-fly...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I must first tell that im a beginer on security things.
Im building a webserver in c++, for unix, linux and windows. And i wonder if i can use this library to get the webserver to support ssl(https)?.
Or at least understand how to code https support.
Sorry i didnt read your ISSL+HOWTO.txt first.
I see that you have made your own protocol,
I wonder if their are much to do to modify this protocol to follow the ssl protocol standard??.
Or its maybe better to build a new from scratch??
I think I really should finally answer this because it's a good question. :)
It would take a lot of changes to change issl into a fully ssl(v1/v2) compatible
protocol including cipher negotiation, mutual trust, x509, etc. The main
reason why I say this isn't worth it is because there's a
good alternative already out there: Please try
scl+sssl for this purpose: http://www.freshmeat.net/projects/scl+sssl
I've already talked to the author, and know this project.. this is what you want for a small webserver SSL library.
iSSL will rather help you in designing your very own applications, especially lightweight ones, or fortifying existing protocols for internal use (such as issl-ircd, or issl-opennap, etc. etc.) almst-on-the-fly...