A few tips:
1. The tool "openssl s_client" (with appropriate command
line options) can be used (on a PC) to figure out which
SSL/TLS options and variations a server is using, this
may or may not be easier than waiting for an answer
from vertx2. I would link to the online documentation,
On Mon, Aug 17, 2015 at 11:25:47AM +0530, Ajay Garg wrote:
> Yes, we need our (embedded-)clients to talk to our TLS-server.
The protocol is documented at:
https://tools.ietf.org/html/rfc5246
However you SHOULD NOT attempt to write your own TLS implementation.
This is much too difficult, eve
Hi Viktor.
Thanks for the reply.
Yes, we need our (embedded-)clients to talk to our TLS-server.
We are using Vertx2 as our server.
Its SSL-support APIs are in "SSLSupport" class at
http://vertx.io/vertx2/api/java/index.html
Going by the APIs, it is not exactly clear what TLS-Algorithm and
Ciphe
We can disable DSO support at configure time with 'no-dso'.
But its not clear to me how to explicitly disable the feature at
runtime if the platform/distro provided the OpenSSL libraries (and
they were enabled). I took a look at config(5), but that's more for
configuration files, and less of runni
> I noticed this weekend that the man pages are no longer available from the
> OpenSSL.org site. The site is beautiful, but the man pages are really needed.
> For example: try openssl.org/docs/ssl/ or openssl.org/docs/apps/
Please see the blog. We're working on it. Might be a couple of days.
__
Hi there,
I noticed this weekend that the man pages are no longer available from the
OpenSSL.org site. The site is beautiful, but the man pages are really needed.
For example: try openssl.org/docs/ssl/ or openssl.org/docs/apps/
I noticed that the search engine results point to http pages while
On Sun, Aug 16, 2015 at 02:44:54PM +0530, Ajay Garg wrote:
> We wish to exhange data over sockets in embedded-environments, and
> unfortunately can't afford to use the de-facto openssl implementation,
> which I believe uses dynamic memory allocations/deallocations in its code
> (we intend to deplo
Hi All.
We wish to exhange data over sockets in embedded-environments, and
unfortunately can't afford to use the de-facto openssl implementation,
which I believe uses dynamic memory allocations/deallocations in its code
(we intend to deploy our solution using bare-metal C, in environments where
ev
