Thanks for your help David.
Regards,
/carl h.
On Tue, Apr 20, 2010 at 9:54 PM, David Schwartz wrote:
>
> Piper Guy1 wrote:
>
>> > This is precisely what a browser does. Again, using the
>> > "https://www.amazon.com"; example, OpenSSL takes care of getting the
>> > certificate from the server, ma
allows the server to send these, lest the client does not
> have some of them. Starting from the trusted root certificate, the client
> can verify intermediate certificates in turn until it finally verifies the
> server certificate.
>
> Has that helped at all?
>
>
> ---
Piper Guy1 wrote:
> > This is precisely what a browser does. Again, using the
> > "https://www.amazon.com"; example, OpenSSL takes care of getting the
> > certificate from the server, making sure the certificate is valid,
> checking
> > that the server owns the certificate, and making sure the
>
that helped at all?
-Original Message-
From: owner-openssl-us...@openssl.org on behalf of piper.guy1
Sent: Mon 4/19/2010 1:27 PM
To: openssl-users@openssl.org
Subject: Re: Verisign client requirements
David,
Sorry for my late response. (pulled in another direction for a while).
But i s
David,
Sorry for my late response. (pulled in another direction for a while).
But i still have a few holes in my understanding (and maybe my head!!).
Here are some facts about our implementation:
1. The server does not have my root certificate.
2. I do not have the server's root certificate.
3.
Piper.guy1 wrote:
> Hi,
>
> Please understand I'm a newbie to security if my question sounds
> rather elementary.
>
> The embedded product I'm working on requires a secure connection to
> our server that uses a Verisign certificate to authenticate. I've been
> porting the OpenSSL examples from
Hi,
Please understand I'm a newbie to security if my question sounds
rather elementary.
The embedded product I'm working on requires a secure connection to
our server that uses a Verisign certificate to authenticate. I've been
porting the OpenSSL examples from the O'Reilly publication so far and
