Apache OpenOffice (AOO) Bugzilla – Issue 55073
Crash when open a signed document
Last modified: 2007-10-06 22:40:54 UTC
I try to open a signed document. the document has been signed on win2k. When the document is without electronique signature , i arrive to open.
No problem for openning the same doc on OOo 2.0 (129 ) debian
ericb -> pierduluberon Can you please attahc the mentioned document, please ? (and give us some infos about the used signature you are using) Thank's in advance :-)
+ me on CC
cc -> tra
adding myself to cc. oooqa kw added.
Created attachment 30427 [details] document signed under Win32
I have opened up the attached document and no crash happens, everything works as expected under Mac OS X Tiger using SRC680 m132. Can somebody with Panther verify that it works? I am setting this issue to WORKSFORME and if no objections arrive in the next weeks, this will be set to INVALID.
Ok I happy to learn it is OK with the Version m132 :) With m130 it crash :( Where can I donwload the 680 m132 ? I am with 10.3 ( Panther) With the 680 m132 do you arrive to sign document ? I install Mozilla and load a cetificat inside the certificat manager , but when i am on Oo2 (680 m130) , i do not have cert in the windows !!! Do you know a small doc about it this subject? Pierre
Hi cyb , I find version 680 m133 with fr language package, I try to open your doc signatur.odt on my MacOs 10.3 ( Panther) , I have a crash. sorry but i think is not resolved :( on 10.3 MacOs . And i dont see the certifcat list in the windows , when i want append one signature. Pierre
alright, looks like it's a problem for Panther only. Assigning to ericb. cyb->ericb: Please test the issue's attached document file on your Panther system and give feedback about whether the office crashes or not.
Created attachment 30542 [details] Crash log file
adding keyword crash.
setting it to NEW.
TRA: Crash is reproducable on Panther
TRA: Just happens when OOo will be launched via the soffice script not when soffice.bin will be started directly. Might have something to do with the search path? Further investigation necessary.
ericb->pierduluberon Experimenting the same problem, looks like libnss3.dylib is faulty (gdb said me the problem was libnss3.dylib , with nss_certificate_hash() ). Looking at the code, problem could be in security/nss Searching why the issue didn't occur when OOo was launched with soffice.bin, I found I already have mozilla installed, and most iinteresting, I found another libnss3.dylib in my system... If you have mozilla (or firefox in your system, please have a look in its directory, maybe another libnss3.dylib is inside. In this case, can you please rename, or move libnss3.dylib located in /Applications/OpenOffice.org2.0/Contents/openoffice.org/program/libnss3.dylib ...and try again ? For me it works : I can open your file without any problem with both soffice and soffice.bin. If you have not mozilla installed nor Firefox, not libnss3.dylib present in your system, I have no idea. Maybe mozilla build has to be verified on Mac OS X. Florian pointed me with macosxgcc4 one typo for a pointer and one cast. I'll continue in this direction.
Hi,This week-end i could test your solution, as I have a Mozilla installation I change name of nss lib. Ok i can open the document, but i don't see that is a signed document !!!!! and when i clic on digital signature , i have a alert windows that he said me we don't have a Mozilla installation ??? regards. Pierre
I upgrade Mac Os X 10.3 to 10.4 I can open the document signatur.odt but i can see if is signed ???? same message about Mozilla OpenOffice don't find the Mozilla installation. Regards. Pierre
ericb->pierduluberon ok, thank you for your report. Looks like the problem is definitively caused by libnss3.dylib. ericb->windly Could yo please help us ?
Sorry, I don't have access to any MacOSX machines. But you can try this area to find out where is the problem. First I suggest you try Mozilla 1.7.5 you built with OOo. Try to use it to access some site with ssl to find out whether it's a Mozilla bug for version 1.7.5. Second try to access you Mozilla address book and Thunderbird address book with OOo. You can access them by create a database and choose connecting to Mozilla Address Book or Thunderbird Address Book. If you can access your address book then you can try whether you can signature a document using OOo.
Created attachment 31454 [details] This file have a macro to check Mozila profiles
ericb->windly First, thank yo very much for your quick help :-) I have tried to trace OOo (using gdb), and after rebuild sal, xmlsecurity, psprint and vcl using debug=true, and I have found several problems in fact: 1) MOZILLA_CERTIFICATE_FOLDER is not defined -> char * env = getenv("MOZILLA_CERTIFICATE_FOLDER") // why is " char * " used ? Reading hackers guide, I believed it was not a good idea ? .. is false, and assertions lines 140 and 144 in xmlsecurity return "failed to create instance " because MOZILLA_CERTIFICATE_FOLDER is not found. Help is clear whith that : Manage your certificates If you are using Solaris or Linux, you must install a recent version of Thunderbird, Mozilla Suite, or Firefox software to install some system files that are needed for encryption. If you have created different profiles in Thunderbird, Mozilla, or Firefox, and you want OpenOffice.org to use one specified profile for certificates, then you can set the environment variable MOZILLA_CERTIFICATE_FOLDER to point to the folder of that specified profile. Save and sign the document 2) as you will see on my attachment, it's not possible to connect to a mozilla address book. I think the problem starts there. ( I have compared with Linux version, where it is possible to use both, Mozilla, Thunderbird and LDAP. So, I think I first have to search in connectivity (or ?? ) why Mozilla ...etc stuff is not activated. To be continued...
Created attachment 31478 [details] screenshot : no choice mozilla/thunderbird address book
The address book ui maybe disabled by the db wizard. You can try to use mozillabootstrap.odt to find out whether you can list all the profiles in your machine. If it cann't list your profiles you can try the attached patch on connectivity/source/drivers/mozab/bootstrap/MNSFolders.cxx. I am not sure, maybe you need modify the file to use the MacOSX special way to get the home directory.
Created attachment 31496 [details] patch to connectivity/source/drivers/mozab/bootstrap/MNSFolders.cxx
ericb->windly Sorry for the long delay : your solution helped a lot. I have completed with a change in scp2, and now it works. Still some problems on Panther, I'll verify soon. Thank you very much :-) We still have to discuss with Maho because of something similar in <http://www.openoffice.org/issues/show_bug.cgi?id=59731> ericb->tra I propose to add the fixes in macosx20xfixes01 (for 2.0.2 ?)
tra->ericb: No problem, you can add this issue to macosx20xfixes01.
I don't know whether it is in any way important for fixing this issue, but the "try to use systen libnss" hack in the soffice shell script doesn't check any Mac specific places as well.
Created attachment 33036 [details] fix for correct preferences path of Mozilla, Firefox,Thunderbird (Mac OS X)
Created attachment 33037 [details] libmozab/libmozabdrv were missing on Mac OS X when internal mozilla is used/built
set target for 2.0.2
TRA: Patches have been commited. Fixed in cws 'macosx20xfixes01'.
tra: Verified -> ok. tra->ericb: Could you verify yourself again.
ericb->tra Verified on Mac OS X Tiger, with m149, using singatur.odt document Pierre provided.
tra->ericb: OOo still crashes on Panther when opening a signed document. Reopened.
ericb->tra Ok, thank you. I'll restart a build on Panther, and see if I can fix it ... or not
re-target to 2.0.3.
Set target for 2.0.4
reset target to 2.x
crash -> higher prio.
Opening both the signed document and macro-ed document on Ooo 2.1 OS X 10.4.8 did not produce a crash. Perhaps the issue has been resolved in the new version? I will be conducting further tests regarding this issue.
Should also note that I tested this bug on both Intel and PowerPC architectures and was not able to reproduce it. Both systems were running OS X 10.4.8.
Eric: please test. i think it was fixed by setting proper install_name on libs...
We no longer maintain Panther version -> wontfix
Closing