Alon, I have followed your discussion in http://www.openoffice.org/issues/show_bug.cgi?id=39382.
Thanks for offering help on improving certificate usage :) I just want to make sure that we all know the details: OOo should be a user of PKI infrastructure, but not the maintainer. On Windows it's clear that all apps should use the users global key store, IMHO it's wrong the Mozilla does it's own certificate management here. On other platforms there is no global key store, that's the reason why we have chosen to rely on a Mozilla profile. We think that most people on non-Windows platforms will have their personal certificate in some Mozilla profile anyway. So why should they import it to other places? It's not important for us how PKI is accessed, but how PKI is managed. OOo shouldn't do that. At maximum, OOo might store personal certificates for signature usage, but then we already would have the "overhead" of needing a encrypted certificate database for protecting private keys. In your scenario, if we used OpenSSL, how would this, as well as (CA) certificate and CRL management work? What is the benefit in replacing an existing Mozilla dependency with a new OpenSSL dependency? Best regards, Malte. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
