Okay, I cleaned out all of the older versions of the keys and ran the scripts again. I ended up with this:
1 out of 1 certificate requests certified, commit? [y/n]y Write out database with 1 new entries Data Base Updated CA verifying: www.pelathe.org.crt <-> CA cert www.pelathe.org.crt: OK That does mean it worked, right? Everything is good? If so, should I move the new files I have to their respective directories or should I change my httpd.conf file to point to the new directory? I don't know if moving or copying/patsing damages the integrity of the encryptions or not. On Thursday 13 March 2003 05:01, camun2020 wrote: > --- On Thu 03/13, A. Putnam < [EMAIL PROTECTED] > wrote: > > Still no luck. I get the same error with this script too. Thank you for > pointing out the script though. It was a LOT easier to use than the other > one I had been using. > > OK, now I'm getting vague but could this be to do with the fact that you > have some 'incomplete' keys and data in your ca.db.certs directory from the > previous failed attempts? > > Make sure you start in a whole new clean directory... > > Having said that, I haven't actually tried those scripts with the most > recent openssl so perhaps there are new problems. > > cam > > _______________________________________________ > No banners. No pop-ups. No kidding. > Introducing My Way - http://www.myway.com > ______________________________________________________________________ > Apache Interface to OpenSSL (mod_ssl) www.modssl.org > User Support Mailing List [EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] -- A. Putnam Assistant IT Administrator Pelathe Community Resource Center ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
