Hello,
Server decrypts this packet with client certificate, calculates its own
hash, compares this two hashes and accepts client authentication or not.
It is not way how DSA/ECDSA signatures work.
If we are talking about RSA, we can talk about decrypting.
But in El-Gamal style algorithms
On 2007.11.20 at 11:48:47 +0100, Marek Marcola wrote:
Server decrypts this packet with client certificate, calculates its own
hash, compares this two hashes and accepts client authentication or not.
It is not way how DSA/ECDSA signatures work.
If we are talking about RSA, we can talk about
Hello,
I notice that the length for a certificate verify message produced by
s_client is always 0x80 bytes (indicated in the messgeLength field).
However, according to RFC 4346, the CertificateVerify message should be
either 36 or 20 bytes, depending on the signature algorithm.
Can anyone
Hello,
I notice that the length for a certificate verify message produced by s_client
is always 0x80 bytes (indicated in the messgeLength field). However, according
to RFC 4346, the CertificateVerify message should be either 36 or 20 bytes,
depending on the signature algorithm. Can anyone
