On Saturday 29 May 2010 12:02:44 a list member wrote:
> As somebody who audits CAs for purpose of them getting into trusted root
> list, this is what you have to do:
> a) Obtain WebTrust for certification authorities or ETSI 101 456 standard
> (+ EV guidelines from cabforum.org)
> b) Implement sys
On Sunday 07 March 2010 18:45:26 you wrote:
> Oops, a sanity check added to OID handling in 0.9.8m was incorrect and
> rejected that policy OID. Here is a patch:
>
> http://cvs.openssl.org/chngview?cn=19398
Thanks Steve,
that worked!
Vesa
_
Hi,
I updated from 0.9.8l to 0.9.8m on my gentoo machine and now openssl can't
parse anymore my X509v3 Certificate Policies field.
This has worked before with my private and allocated policy OID.
with 0.9.8l output for the same certificate was (cut to have the interesting
part only):
openssl
Hi,
I just finish installing Redhat 7.0 on my notebook and I'd like
to inform Redhat users that RH 7.0 include now :
openssl 0.9.5a
apache 1.3.12
mod_ssl 2.6.6
A big + for openssl/mod_ssl.
Regards
__
OpenSSL Project
>I'm trying to produce certs for use with Apache Project Tomcat :
>
>openssl req -new -out REQ.pem -keyout KEY.pem
>openssl req -x509 -in REQ.pem -key KEY.pem -out CERT.pem
>openssl req -verify -in REQ.pem
>openssl req -verify -in REQ.pem -key KEY.pem
>openssl req -text -in REQ.pem
Ok,
>But when I
I'm trying to produce certs for use with Apache Project Tomcat :
openssl req -new -out REQ.pem -keyout KEY.pem
openssl req -x509 -in REQ.pem -key KEY.pem -out CERT.pem
openssl req -verify -in REQ.pem
openssl req -verify -in REQ.pem -key KEY.pem
openssl req -text -in REQ.pem
But when I try to imp