Andr�a Cavallari wrote: > Thanks Michael!! > But I have one more question: When my client (in his browser) > generate a certificate and change the key pair, install the > certificate and will use it with the same browser configuration, the > certificate works. what you mean by: change the key pair? which browser you are talking about? what you mean by: the cert works? how this verified?
> the certificate stop working and we have to tell to the client make a > new certificate to work with the new configuration. this sounds strange > So, my question is: In the moment of the change key pair/generate, > the certificate get some information about browser's configuration? > Get any state of the selected SSL option or browser security level? I don't understand this question ;) a certificate is a signed data container it contains: - some vilidity fields (like valid from to) - some id fields (subject, subject alternative and so on) - some extensions (for what to use) - the public key of the keypair, for which a cert is requested and is signed by the ca so there is no connection to any browser configuration actually at least it shouldn't... or maybe you have some special configurations? greetings dalini ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Openca-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openca-users
