Have two questions:
1) Is it mandatory to build the OpenSSL library in order to use the
functionality provided by OpenSSL?, or is it possible to use it with the
OpenSSL-Win32 library I downloaded.
2) If I build the OpenSSL library with one compiler is it possible to use with
another compiler?
On 12/17/2010 1:41 AM, Kingston Smiler wrote:
Is there any way to identify whether the other end supports TLS or not.
There is no way we could know the answer to this question. We have no
idea what your other end is, who designed it, or how.
My requirement is like this.
If the other end su
You can use the -config option to specify a desired config file.
...
Erik Tkal
Juniper OAC/UAC/Pulse Development
-Original Message-
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of felix farcas
Sent: Friday, Dece
The client sends a ClientHello message with the protocol version in this case
3.1.
The server sends a ServerHello message with the protocol it supports.
The client reads the ServerHello and checks the protocol version.
You can test by running the following commands.
openssl s_server -deb
On Fri, Dec 17, 2010 at 03:11:54PM +0530, Kingston Smiler wrote:
> Is there any way to identify whether the other end supports TLS or not.
Only if the application protocol supports a way to negotiate TLS (e.g.
SMTP, IMAP, telnet, ... with STARTTLS), or the service in question is
layered over TLS
Hi All,
Is there any way to identify whether the other end supports TLS or not. My
requirement is like this.
If the other end supports TLS i should send the packet over TLS connection
otherwise i should send traffic over TCP.
If the other end doesn't support TLS, my initial TCP connection will be
Hello Patrick
thank you for the answer
Is it possible to use a special openssl.cnf file in the same commnad,
without using the initial *.cnf file from openssl?
Thank you
Felix
On 16.12.2010 20:32, Patrick Patterson wrote:
Hi Felix:
What you want is the -subj command line option.
Have fun.
