To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=104554 Issue #|104554 Summary|xmlsecurity: loading of root certificate with S Component|xml Version|DEV300m56 Platform|All URL| OS/Version|Unix, X11 Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|cmc Reported by|jl
------- Additional comments from j...@openoffice.org Thu Aug 27 14:04:58 +0000 2009 ------- I made changes to the code with loads the root certificate module and noticed that this would probably not work when "SYSTEM_MOZILLA" is used. Please check the code in xmlsecurity/source/xmlsec/nss/seinitializer_nssimpl.cxx:nsscrypto_initialize The code change was made on cws jl127 and will probably integrated in DEV300m57. This is the my comment from the source file: //Older versions of Firefox (FF), for example FF2, and Thunderbird (TB) 2 write //the roots certificate module (libnssckbi.so), which they use, into the //profile. This module will then already be loaded during NSS_Init (and the //other init functions). This fails in two cases. First, FF3 was used to create //the profile, or possibly used that profile before, and second the profile was //used on a different platform. // //Then one needs to add the roots module oneself. This should be done with //SECMOD_LoadUserModule rather then SECMOD_AddNewModule. The latter would write //the location of the roots module to the profile, which makes FF2 and TB2 use //it instead of there own module. // //When using SYSTEM_MOZILLA then the libnss3.so lib is typically found in ///usr/lib. This folder may, however, NOT contain the roots certificate //module. That is, just providing the library name in SECMOD_LoadUserModule or //SECMOD_AddNewModule will FAIL to load the mozilla unless the LD_LIBRARY_PATH //contains an FF or TB installation. Additional notes: I am not sure anymore if it really worked with setting the LD_LIBRARY_PATH. If it worked then because a Firefox 2 or Thunderbird 2 profile was used. These profiles contain the path to the root certificate module so that the nss library can load it during initialization. Provided that you can confirm that, one way to fix this would be to provide the complete path to the libnssckbi.so file. This would probably achieved by some kind of configure magic. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@xml.openoffice.org For additional commands, e-mail: issues-h...@xml.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
