> From: owner-openssl-us...@openssl.org On Behalf Of Yvonne Wambui
> Sent: Friday, January 10, 2014 01:44
> thanks dave and martin. with all that information i think i should start
the process again.
> Do you have some materials that have step by step process of configuring
two way connections
I
thanks dave and martin. with all that information i think i should start
the process again. Do you have some materials that have step by step
process of configuring two way connections
On Fri, Jan 10, 2014 at 7:30 AM, Dave Thompson wrote:
> > From: owner-openssl-users On Behalf Of Martin Hecht
>
> From: owner-openssl-users On Behalf Of Martin Hecht
> Sent: Thursday, January 09, 2014 11:54
Generally good explanation, but a few quibbles:
> I don't know what exactly you are doing, so it is difficult to speculate
> why you are receiving code 19.
>
> Some information is exchanged during esta
I don't know what exactly you are doing, so it is difficult to speculate
why you are receiving code 19.
Some information is exchanged during establishment of the ssl
connection. For example if you have a web server and a browser, the web
server shows the host certificate to the browser and the br
could you please explain the last reason.
On Thu, Jan 9, 2014 at 3:38 PM, Martin Hecht wrote:
> X509_V_OK would be code 0
> 19 means that the CA certificate could be found, the chain could be
> built and verified completely up to the CA certificate but the latter is
> not trusted. (see http://
X509_V_OK would be code 0
19 means that the CA certificate could be found, the chain could be
built and verified completely up to the CA certificate but the latter is
not trusted. (see http://www.openssl.org/docs/apps/verify.html)
ah, for some things to work correctly, the file name must be the su
thanks martin. i made the changes and now im getting
Verify return code: 19 (self signed certificate in certificate chain)
is this ok, or i need code 0
On Thu, Jan 9, 2014 at 1:33 PM, Martin Hecht wrote:
> I was thinking about manual verification of certificates on the command
> line. From wha
I was thinking about manual verification of certificates on the command
line. From what you wrote now, it seems that you are using some calls to
the openssl library in a client-server application, maybe via other
tools/webserver or so, and I understand that the server certificate was
issued by a di
thanks martin, your response shade some light and i can now understand what
im doing. Im trying to create a two way ssl connection, the problem when
verifying the connection to the server, its using my RootCA instead of the
server, hence throwing verification error 19. would you please advise on
wh
On 08.01.2014 15:32, Yvonne Wambui wrote:
> i get this error when verifing a non-self signed certificate. how do i make
> it not point to the rootCA
>
It makes no sense to verify a non-self signed certificate without the
rootCA certificate. To verify such a certificate you have to provide the
certi
Thank you. It worked fine after concatenating cert1.pem and cert2.pem
into single file.
Regards,
Vinay
sandeep kiran p wrote:
The -untrusted argument to verify command takes a single file
containing multiple certificates concatenated together. Try adding
cert1.pem and cert2.pem into a single
The -untrusted argument to verify command takes a single file containing
multiple certificates concatenated together. Try adding cert1.pem and
cert2.pem into a single file and check again.
Thanks,
Sandeep
On Tue, Dec 14, 2010 at 12:00 PM, Vinay Kumar L <
vinaykuma...@globaledgesoft.com> wrote:
>
On Thu, Nov 25, 2004, Frédéric PAILLETTE wrote:
> Florin Angelescu wrote:
>
> >hello
> >i have build openldap with openssl support
> >and when a client try to connect i got :
> >
> >
> >TLS certificate verification: depth: 1, err: 19,
> >subject:
> >/C=BE/ST=BELGIUM/L=BRUSSELS/O=CAAMI_CA/OU=CC
Florin Angelescu wrote:
hello
i have build openldap with openssl support
and when a client try to connect i got :
TLS certificate verification: depth: 1, err: 19,
subject: /C=BE/ST=BELGIUM/L=BRUSSELS/O=CAAMI_CA/OU=CCI/CN=CAAMI_CA/[EMAIL PROTECTED],
issuer: /C=BE/ST=BELGIUM/L=BRUSSELS/O=CAAMI_C
14 matches
Mail list logo
