Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Adopt Mac OS X crypto API instead of using Mozilla's | ||
---|---|---|---|
Product: | General | Reporter: | jogi |
Component: | code | Assignee: | joachim.lingner |
Status: | CLOSED WONT_FIX | QA Contact: | issues@framework <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues, malte_timmermann |
Version: | current | Keywords: | aqua |
Target Milestone: | --- | ||
Hardware: | Mac | ||
OS: | Mac OS X, all | ||
Issue Type: | FEATURE | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
jogi
2007-09-05 14:53:44 UTC
adding keyword MT, please send the issue then to user 'macport' Thx. mt told me that the system specific integration on Win32 is currently achieved by libxmlsec itself which is compiled differently to support Windows' on API. A similar approach for MacOSX would be possible, however the version of libxmlsec we currently have is quite old; we'd need to switch to a newer version and port up all our patches that we apply to libxmlsec before compiling it. JL... *** Issue 77589 has been marked as a duplicate of this issue. *** jsi: Sorry, no time to implement this for 3.0. => 3.x . These are actually two things here. 1. Dependency on NSS libs (Mozilla) 2. System integration. #1. I think it is absolutely ligitimate to use NSS (Mozilla) libs rather then those from MacOS. The MacOS security lib does NOT make clear what standards it follows when for example verifying a certificate. Also the libxmlsec library (external) which actual creates the XML signature does not support MacOS. Replacing it will be a huge effort. Keeping in mind that the legal value of our signature is more than questionable, this effort is not justified. #2. I agree that one should be able to use the system's certificate store. If this is what you intended please submit a separate issue. . |