g the CA.pl script, generate a> > certificate with a subjectAltName extension of type dNSName? The ones I> > have already generated do not have this field set.> > > I suppose there is an openssl.cnf file setting for this purpose? I> > notice the line "#subjectAlt
On Fri, Jun 09, 2006 at 12:25:52AM +0200, Goetz Babin-Ebell wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> david kine schrieb:
> Hello David,
>
> > One more question: how do I, using the CA.pl script, generate a
> > certificate with a subjectAlt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
david kine schrieb:
Hello David,
> One more question: how do I, using the CA.pl script, generate a
> certificate with a subjectAltName extension of type dNSName? The ones I
> have already generated do not have this field set.
> I supp
Hello Victor, Thank you very much, the code you provide is extremely useful! One more question: how do I, using the CA.pl script, generate a certificate with a subjectAltName extension of type dNSName? The ones I have already generated do not have this field set. I suppose there is
On Thu, Jun 08, 2006 at 11:40:04AM -0700, david kine wrote:
> My code to retrieve the common name from the subject field is:
> X509 *cert = [code not shown]
> char pName[ 256 ];
> X509_NAME *subj;
> subj = X509_get_subject_name( cert );
> X509_NAME_get_text_by_NID( subj, NID_commonNa
Hello, My secure client application performs post-connection fully-qualified-domain-name authentication. According to RFC 2818, "If a subjectAltName extension of type dNSName is present, that MUST be used as the identity. Otherwise, the (most specific) Common Name field in the Su
