On Thu, Oct 22, 1998, Martin Kuzela wrote:
>[...]
> Yes, but which option points to "generate CSR"?
No option itself. The CSR is generated via "ssleay req".
> > > Question4: Are there any problems with CSR files generated this way at
> > > Verisign?
> >
> > No, as long as your "ssleay req -noout -text -in <file>" gives you the correct
> > DN it should not make problems.
>
> Hm. What is DN ?
DN = Distinguished Name.
That's the bundle of X.509 fields like CN, O, OU, etc.
> Information I has put in seems to be correct, but where should I search for DN?
> Subject: C=US, ST=New Jersey, L=Roseland, O=Inkflow, Inc., OU=Adela team
> , [EMAIL PROTECTED]
_This_ is the DN. Looks fine.
> > Just replace the installed etc/ssl.crt/server.crt with the certificate
> > Verisign sends you and the etc/ssl.key/server.key with the private key you
> > generated under 1.).
>
> Yes, this thing is clear. thanks.
>
> Please ,don't get angry from this mail. :-)
> but moving among these security terms makes me mad.
I don't get angry, no problem. But that's the price you have to pay: Before
you get security you have to understand it and for this a few terms are
necessary. Without them we couldn't talk about it or at least we won't
understand us ;-)
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
