>> That's us. :-) We're exploring the possibility of setting up a private CA
>> to support a small number of our PC's in an IPSEC configuration.
>>
>
> OK. Well if thats you, does that mean that you have the private key for
> the certificate it mentions?
Yes.
> If so it should be possible to d
John Wehle wrote:
>
> > More interesting. It looks like a CSR but its broken somewhat. Since
> > there are several forms for the CSR I needed to check the file to be
> > sure.
> >
> > These things can have a PKCS#10 request variant and some other data
> > inside a PKCS#7 wrapper. The wrapper can
> More interesting. It looks like a CSR but its broken somewhat. Since
> there are several forms for the CSR I needed to check the file to be
> sure.
>
> These things can have a PKCS#10 request variant and some other data
> inside a PKCS#7 wrapper. The wrapper can be either PKCS#7 signed data or
> Cisco router use CEP protocol to enroll certificates.
> It can only request certificates to CA servers which supports
> CEP. I do not know how you made Cisco router to save the Certi request
> in this attached file. How did you get it?
By pointing it to a http server which has the following cgi
Cisco router use CEP protocol to enroll certificates.
It can only request certificates to CA servers which supports
CEP. I do not know how you made Cisco router to save the Certi request
in this attached file. How did you get it?
regards
ajith
(Disclaimer: This is only a personnel email. i am jus
John Wehle wrote:
>
> > John Wehle wrote:
> > >
> > > The Cisco 2501 generates the enclosed ASN1 data stream when asked
> > > to generated a certificate request. How do I certify it? It
> > > doesn't seem to be recognized as a request by openssl.
> > >
> > > $ openssl req -inform der < cert_req
> John Wehle wrote:
> >
> > The Cisco 2501 generates the enclosed ASN1 data stream when asked
> > to generated a certificate request. How do I certify it? It
> > doesn't seem to be recognized as a request by openssl.
> >
> > $ openssl req -inform der < cert_req.27281
> > Using configuration fr
This is part of the IPSEC stuff. I know Verisign handles this.
I'll be evaluating that, along with NetworkAlchemy's box.
Are IPSEC CSR's different, or is this a Cisco thing? I know the CSR's have to
hold the IP addressesof the encryption interfaces.
On Thu, 06 May 1999 Ben Laurie wrote:
>
> J
On Thu, 6 May 1999, Ben Laurie wrote:
> John Wehle wrote:
> >
> > The Cisco 2501 generates the enclosed ASN1 data stream when asked
> > to generated a certificate request.
>
> Gosh, when did they start doing that?
They did that some months ago, as you'll see in the draft I sent.
These request
John Wehle wrote:
>
> The Cisco 2501 generates the enclosed ASN1 data stream when asked
> to generated a certificate request.
Gosh, when did they start doing that?
> How do I certify it? It
> doesn't seem to be recognized as a request by openssl.
>
> $ openssl req -inform der < cert_req.2728
10 matches
Mail list logo
