One that is up to date and actively developed, open source, small size, small footprint and portability - not only for Win and Linux.
I went trough several sites comparing them and, as expected, openSSL is the mostly used. However there is this MatrixSSL with a full set of features and its overall functioning is worth a look. Regarding portability they say "has a very portable OS layer that allows easy porting to any operating system."
There is already a crypto library in use in Darkbot we need to take in consideration too, avoiding duplicity and reducing sizes and footprint.
Other matter we should think of is the possibility of having it as per user wishes, as a (separated) module for example.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have no preference, other than to agree with Luiz. Though I've not seen MatrixSSL.
Following the Heartbleed bug (bugs get their own logo now?) I suspect OpenSSL will get a lot more eyeballs looking at making sure it doesn't have any more such nasty security bugs lurking for years.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
... and, George, have in mind the usage of servers.ini (of course) and perform.ini . This one might help reducing sizes and time in the coding process :)
/me is not a coder nor programmer- only general ideas ;)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm starting to look into implementing this feature. Do we have any preference for the SSL library?
One that is up to date and actively developed, open source, small size, small footprint and portability - not only for Win and Linux.
I went trough several sites comparing them and, as expected, openSSL is the mostly used. However there is this MatrixSSL with a full set of features and its overall functioning is worth a look. Regarding portability they say "has a very portable OS layer that allows easy porting to any operating system."
There is already a crypto library in use in Darkbot we need to take in consideration too, avoiding duplicity and reducing sizes and footprint.
Other matter we should think of is the possibility of having it as per user wishes, as a (separated) module for example.
I have no preference, other than to agree with Luiz. Though I've not seen MatrixSSL.
Following the Heartbleed bug (bugs get their own logo now?) I suspect OpenSSL will get a lot more eyeballs looking at making sure it doesn't have any more such nasty security bugs lurking for years.
... and, George, have in mind the usage of servers.ini (of course) and perform.ini . This one might help reducing sizes and time in the coding process :)
/me is not a coder nor programmer- only general ideas ;)
sure. I'll look into it. I might be able to cook up a simple design doc so people can proof read it, though I'm gonna get a POC working first.
Cool, I look forward to seeing your contribution.