Hello,
I have implemented ssl for tcp ad HTTP as well i.e ssl security for
tcp ad http servers. I have created self- signed certificate for CA and
server and client certificates using the self- signed CA certificate.But I
would like to know the process of automating certificate
Hello,
I have implemented ssl for tcp ad HTTP as well i.e ssl security for
tcp ad http servers. I have created self- signed certificate for CA and
server and client certificates using the self- signed CA certificate.But I
would like to know the process of automating certificate management
. How
can such a thing be tested for a server listening over private ip?
Please help. Awaiting response.
Regards,
R-D Intern
--
View this message in context:
http://openssl.6102.n7.nabble.com/regarding-ssl-server-test-tp66354.html
Sent from the OpenSSL - User mailing list archive at Nabble.com
Thank you so much.I tried searching for a downloadable ssl_server test
source code for internal servers but couldn't get any.how could I get one?
Thanks and regards,
R-D Intern
--
View this message in context:
http://openssl.6102.n7.nabble.com/regarding-ssl-server-test-tp66354p66400.html
Thank you a lot, Jakob.I understood your answers and am quite satisfied too
that the replies sound conceptually right. But it would be kind on your part
if you answer some questions further.
1. Regarding question 3, I am using openssl 1.0.2e which supports named
curve. Such a question had earlier
Hello ,
I am a Masters student and currently working on a project related to
security. I have certain queries regarding ssl security. It would be of
great use to me if some of my queries get clarified. The following is listed
as:
1. How do I prove that ECC 256 bit key is equivalently
Hello,
I am trying with SSL handshake mechanism with ECDSA-ECDHE-AES-SHA
and have generated certificates following the below link.
http://this.is.thoughtcrime.org.nz/elliptic-curve-ca-guide
But have certain issues regarding the same.
1. The generated certificates show "The
Hello,
I am using ECDSA-ECDHE-AES-SHA cipher suite for client -server security.I
tried understanding the mechanism handshake mechanism. What still quizzes me
is ; communication between a specific client -server for a specific session
generates different encrypted text for the same plain text
Hello,
I have used ECDSA-ECDHE-AES-SHA as the cipher suite in my client- server
communication. To use ECDHE key exchange algorithm I used ECDHE parameters
and what I see is an additional server key exchange in my SSL handshake
process. What does that imply? Does that increase the security
Hello Benjamin,
Thanks for the reply.
I know the purpose and benefit of creating different cipher texts of the
same corresponding plain text.But I would like to know about the places
where this randomness gets introduced to create different encrypted
texts.Because SSL handshake takes place only
Thank you, Jakob.
I had read that the earlier versions IV logic used to use the last block of
the ciphertext as the IV for the next message and this proved vulnerable
giving way to reflection attacks. But is it only the IV that changes? the
bulk encryption and MAC keys remain constant throughput
Thanks Salz for the reply. I do understand the server key exchange is used to
involve even the server in the key exchange process to send the ECDHE public
key with the EC domain parameters so that the client creates the ECDHE
public key and the pre master secret. But even if there is no server key
Thank you, Stephen.
You answered regarding randomness in different sessions if session
resumption is on. But my question revolves around the same messages within
the same Session. How different encrypted texts are formed of the same
plaintext between a client -server?
Is it only the iv changes
13 matches
Mail list logo
