You are right! I renamed the files and then c_rehash them. It seemed that hash files were generated. And yes, I guess my *.crt files actually already encoded in PEM format.
I am a newbie, and do not know much about CoSign. If you have interest, you can check its website: www.weblogin.org :) This is a tool used for Single Sign-On. I am grateful for your help! 2007/4/13, Bernhard Froehlich <[EMAIL PROTECTED]>:
Buffalo Dickens schrieb: > Dear Ted, yes, I found that too. It just looks for *.pem files. I just > used the c_rehash from the source code package of openssl-0.9.8e. Is > it feasible for me to just rename file.crt to file.pem? openssl usually does not rely on filenames or extensions, with only a few exceptions (I guess you already found most of them). So you can just rename your *.crt-files to *.pem. Note beside: Some people use the extension "*.crt" for DER encoded data (a binary file format) and "*.pem" for PEM encoded data (an ASCII file format). To change the encoding it would be necessary to use the "openssl x509" tool. But since your files work with "openssl verify" as you described, they obviously are already PEM encoded. > Or is there an > appropriate and graceful method for this transformation? > > Oh, I just want to deploy a software called CoSign for my websites. > But I kept coming across problems with certificates. OK, then it may help to understand how openssl handles certificates, expecially if CoSign uses openssl (I don't know that software). Something that just jumps to my mind: maybe that software expects DER encoded certificates? Ted ;) -- PGP Public Key Information Download complete Key from http://www.convey.de/ted/tedkey_convey.asc Key fingerprint = 31B0 E029 BCF9 6605 DAC1 B2E1 0CC8 70F4 7AFB 8D26
-- You will when you BELIEVE. Buffalo Dickens ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
