Ken Murchison wrote:
What is the correct way to convert a DSA key struct into a u_char buffer
for use with EVP_VerifyFinal()? Is there a generic way to do this
regardless of the signature key algorithm? The value of the EVP
interface seems lost if I have to call different key preparation
Nils Larsch wrote:
Ken Murchison wrote:
What is the correct way to convert a DSA key struct into a u_char buffer
for use with EVP_VerifyFinal()? Is there a generic way to do this
regardless of the signature key algorithm? The value of the EVP
interface seems lost if I have to call
On Sun, Feb 09, 2003, Ken Murchison wrote:
Nils Larsch wrote:
Ken Murchison wrote:
What is the correct way to convert a DSA key struct into a u_char buffer
for use with EVP_VerifyFinal()? Is there a generic way to do this
regardless of the signature key algorithm? The value
Dr. Stephen Henson wrote:
On Sun, Feb 09, 2003, Ken Murchison wrote:
Nils Larsch wrote:
Ken Murchison wrote:
What is the correct way to convert a DSA key struct into a u_char buffer
for use with EVP_VerifyFinal()? Is there a generic way to do this
regardless of the
I have the following scenario -
Client Cert -- Tunnel Server - Tunnel Client -- Backend server.
The requirement is to pass the Client Cert to the Backend server.
If you could do that then anyone who had access to a certificate
(for example the recipent of signed email) could
All this talk about trying to gateway client certs has got me thinking
about something I saw last week in the PGP-8.0 docs.
They have this concept of additional decryption keys. Apparently you
can configure PGP so that even though you are the only one with your
key-pair, when you encrypt a
On Mon, Feb 10, 2003, Jason Haar wrote:
All this talk about trying to gateway client certs has got me thinking
about something I saw last week in the PGP-8.0 docs.
They have this concept of additional decryption keys. Apparently you
can configure PGP so that even though you are the only one
On Mon, Feb 10, 2003 at 02:25:31AM +0100, Dr. Stephen Henson wrote:
Well for S/MIME enveloped data you can add additional certificates whose owner
(i.e. the entity with access to the private key) can decrypt. Many S/MIME
clients automatically make the message readable by the recpient (its silly
It seems I have not explained myself ably.
I completly understand that Private Keys should and would never be sent
across.
But assume that you are going through a proxy using SSL. And the proxy has
no capability to verify the certs. That capablity is vested with a server
that sits behind the
