RE: How to get rid of "do you want to sign the cert" user request when signing a CSR?

> From: owner-openssl-us...@openssl.org On Behalf Of Martin Schneider > Sent: Thursday, 24 September, 2009 04:58 > I'm using CA.pl from an application to automatically sign > certificate requests. The problem is, that when the CSR is (Aside: you're not signing the CSR. The CSR is already signed

RE: trying to understand ECDHE operations

> From: owner-openssl-us...@openssl.org On Behalf Of Michael D > Sent: Thursday, 24 September, 2009 09:12 > I have been playing with an the command line tools of open > SSL and am examining traces in hopes to get an understanding > of how ECDHE works in real life. > Remember commandline s_clien

RE: error:0200274D:system library:connect:reason(1869)?

> From: owner-openssl-us...@openssl.org On Behalf Of gary clark > Sent: Thursday, 24 September, 2009 00:29 > I am receiving a 0200274D error when attempting to connect to > a linux server. > > 274D=10061 ECONNREFUSED. > > Not sure what the reason is 1869? could somebody please tell me. > The 1

Re: verify client certificate at a later point

sorry! I mean BIO_do_connect() this function automatically checks the client verificate, so I need to overwrite the verifiction callback BIO_do_connect uses thx On Thu, Sep 24, 2009 at 5:13 PM, Michael Prinzinger wrote: > Thank You very much Victor, > > I think I understand now how it can be don

Re: verify client certificate at a later point

Thank You very much Victor, I think I understand now how it can be done. If you could give me one last pointer, how to overwrite the verification callback function, that is called when executing "BIO_do_handshake", I'd be very grateful. sorry for using misguiding vocanulary :) Michael On Thu, S

Re: verify client certificate at a later point

On Thu, Sep 24, 2009 at 04:23:03PM +0200, Michael Prinzinger wrote: > > Are you saying that the accepting system expects X.509 client credentials > > from the connecting system, but that the payload (encrypted to the > > receiving node's public key) also contains the same certificate, and > > you

Re: verify client certificate at a later point

Thank You again Victor for your answer, You are right, I am not to firm with OpenSSL terminology. I tried to find some tutorials and introduction, but found relatively few, and thus tried to understand OpenSSL from looking at the man pages and the code, which makes it a little hard to get the big

Re: verify client certificate at a later point

On Thu, Sep 24, 2009 at 12:00:05AM +0200, Michael Prinzinger wrote: > > "Certificates" are useless without corresponding signed messages. What > > messages are signed by the private key of the "previous" node, that the > > current node can forward to the next? > > > > I only want to verify that t

trying to understand ECDHE operations

Hello, I have been playing with an the command line tools of open SSL and am examining traces in hopes to get an understanding of how ECDHE works in real life. My confusion focuses on the Client Key Exchange, Change Cipher Spec, Encrypted Handshake message. The server has selected: TLS_ECDHE_ECD

How to get rid of "do you want to sign the cert" user request when signing a CSR?

Hello everybody I'm using CA.pl from an application to automatically sign certificate requests. The problem is, that when the CSR is signed some user interaction is still needed what I do not want of cause. OpenSSL asks Certificate is to be certified until Sep 24 08:38:55 2010 GMT (365 days) Sign

Re: verify client certificate at a later point

* Victor Duchovni wrote on Wed, Sep 23, 2009 at 16:18 -0400: > On Wed, Sep 23, 2009 at 10:04:48PM +0200, Michael Prinzinger wrote: > > > I have a somewhat curious setting (without CAs) about [...] > > > > > //check certificate > > This only verifies the server's *trust chain*, but not its > i