Hi folks, as I was reading the HOWTO certificates.txt to grab information on creating a CA, I saw several mentions of ca.txt.
Such as in section 4, "Creating a self-signed test certificate": "This is NOT the recommended way to create a CA certificate, see ca.txt." And I wanted to report the documentation bug about this non-existent ca.txt file. After some quick research, I found the rt.openssl.org website, which seems to be the place to report bugs. So, from http://rt.openssl.org, I found several relevant points : o There is no obvious way to bypass the authentication system to create a bug report o Using the login/password guest/guest, that works, and I can see tickets o I cannot create a new ticket o There seems to be several interesting tickets regarding security on current stable releases the interface shows o You can authenticate as *HTTP*. I just hope no developer log this way and use the same password for their CVS account o The certificate used for https is expired since 08/02/2003 Regards, Sebastien Tricaud. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [EMAIL PROTECTED]
