On Wed, 26 Apr 2000, David Oppenheim wrote: > Is there a standard way, or has anyone come up with a way, of reasonably > easily building a certificate into compiled code ? I guess I can think > of several, but if there's a (semi)standard, I'd rather follow it, and not > reinvent the wheel. one standard way is, of course, using sharable code objects in a dynamically linked library. this makes substitution somewhat harder than if just a plain cert file is supplied. you should propably use another step of crypto, a simple unlocking mechanism to make a vendor supplied .so usable. this way you could change the public key by updating a small dll, but substitution would be next to impossible if the unlocking code in your application did it's job well. ok? -- [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
