Thanks Ram,
Another question too,
After exchanging the client and server hello , On what basis is the common
cipher agreed upon?
-mithun
On Sat, Nov 5, 2011 at 9:26 AM, wrote:
> By default it will send all the ciphersuites it is supporting , but you
> can always control the cipher suites yo
By default it will send all the ciphersuites it is supporting , but you
can always control the cipher suites you want negotiate by using something
like below ...
here it will set only Non_anonymous and RSA type ciphersuites
if (!SSL_CTX_set_cipher_list(*ctx,
"RSA:!ADH:!NULL:!aNULL!RC4:!RC5:!EXPORT
Thanks Ram,
i have another question,
When the client sends "client hello" will it specify all the cipher suites
it supports or are there any other parameters that can be configured at the
client so that it sends selective list of cipher suites?
-Thanks
mithun
On Sat, Nov 5, 2011 at 8:59 AM,
You can check the supported cipher suites by looking in to client hello
messsage.
Regards,
Ram
> Hello Forum,
>
> I want to know what are the cipher suites that the client is supporting.
> How can i do that?
>
> -mithun
>
__
Op
Hello Forum,
I want to know what are the cipher suites that the client is supporting.
How can i do that?
-mithun
> I've been having consistent performance problems with the 64 bit
> openssl FIPS 1.2.3 with asm on AES. The assembly code on 64 bit
> architectures is much slower than without assembly. Running the same
> tests on a 32 bit machine results with ASM being faster than no-asm,
> which is expected.
>
>
> That is present but not actually used by the 2.0 module. Those values will
come from
> the FIPS capable OpenSSL (1.0.1 and later) the module is used with.
>
> The 2.0 module itself has separate version numbers which can be retrieved
using
> FIPS_module_version() and FIPS_module_version_text()
> From: owner-openssl-us...@openssl.org On Behalf Of ramaswamy
> Sent: Thursday, 03 November, 2011 07:44
> Try this...if you need some extensions you can add those in
> openssl.cnf.
>
Several minor errors, and some infelicities.
>
> export OPENSSL_CONF=./openssl.cnf
> PATH=.:$PATH
>
> # Root C
> From: owner-openssl-us...@openssl.org On Behalf Of Evans, Darren E (IS)
> Sent: Thursday, 03 November, 2011 17:04
> I build both the 0.9.8k and 0.9.8r from the source. They are
> configured the same way, ./Configure solaris-sparcv9-cc
> no-shared no-ecdh
>
> It is installed in /usr/local/ssl
On 4 Nov 2011, at 7:12 AM, Mr.Rout wrote:
> Can any body please let me know "what is the difference between TLS
> Connection and TLS Session ?
If a client makes a connection to a server it has previously connected to, it
can re-use the cryptographic parameters (such as the initial session key /
Thanks Ciao !!!.
I am seeing that "for one TCP connection my TLS client is doing 4
handshakes". I don't know what is the reason for this.
But when i see the packet capture i see "TLSv1: [TCP Previous segment lost]
Ignored Unknown" & "TLSv1: Encrypted Alert".
Can somebody please confirm this
Am 04.11.2011 15:12, schrieb Mr.Rout:
Dear All,
Can any body please let me know "what is the difference between TLS
Connection and TLS Session ?
How many TLS Session would be there in one TLS Connection?
For each TCP connection how many TLS Connection and TLS Session would be
there ?
See e.g
Thanks a lot RAM & MICHEL for giving your precious time to answer my query.
Best Regards,
Rout
ramaswamy.bm wrote:
>
> Try this...if you need some extensions you can add those in openssl.cnf.
>
>
> export OPENSSL_CONF=./openssl.cnf
> PATH=.:$PATH
>
> # Root Certificate
> openssl genrsa -o
Dear All,
Can any body please let me know "what is the difference between TLS
Connection and TLS Session ?
How many TLS Session would be there in one TLS Connection?
For each TCP connection how many TLS Connection and TLS Session would be
there ?
Please clarify.
Best Regards,
Rout
--
View th
On Fri, Nov 4, 2011 at 6:05 AM, Shashidhar RP wrote:
> HI
> I disabled SSLv2 on the server. When the client which is capable of SSLV2
> and SSLV3 sends the hand shake, client sends first V2 hello rt So the
> server is not capable of handling V2 packet as SSLV2 is
> disabled on server. C
HI
I disabled SSLv2 on the server. When the client which is capable of SSLV2
and SSLV3 sends the hand shake, client sends first V2 hello rt So the
server is not capable of handling V2 packet as SSLV2 is
disabled on server. Can you please help me here how to proceed.
From our side, the
Hello,
I have an embedded device (with limited ressources) that needs to connect to an
OpenSSL server (Apache2).
The device works very well with many SSL servers with OpenSSL, but not on some
Apache2 servers, because there's a timeout,
after 10 seconds the server always send a "close_notify" al
17 matches
Mail list logo