Issue 41276 - opening OOo-native documents leads to crash in XMLSignatureHelper::Init
Summary: opening OOo-native documents leads to crash in XMLSignatureHelper::Init
Status: CLOSED FIXED
Alias: None
Product: porting
Classification: Code
Component: code (show other issues)
Version: 680m71
Hardware: Mac Mac OS X, all
: P1 (highest) Trivial (vote)
Target Milestone: OOo 2.0
Assignee: frank
QA Contact: issues@porting
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-25 11:57 UTC by florian
Modified: 2005-04-04 13:50 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
crash log of MacOSX's console (18.81 KB, text/plain)
2005-01-25 11:58 UTC, florian 		no flags Details
This is a workaraound patch (463 bytes, patch)
2005-01-25 11:59 UTC, florian 		no flags Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description florian 2005-01-25 11:57:11 UTC 
When trying to open an OOo-native document soffice.bin crashes in XMLSignatureHelper::Init 
(xmlsecurity/source/helper/xmlsignaturehelper.cxx). The problem is that in the statement 
"mxSecurityContext = mxSEInitializer->createSecurityContext( aTokenPath );" in Init() mxSEInitializer 
seems to be a null pointer.
Complete crash log of MacOSX's console is attached. Also attached is a workaround patch that enables 
opening of native documents in MacOSX.
Comment 1 florian 2005-01-25 11:58:32 UTC 
Created attachment 21853 [details]
crash log of MacOSX's console
Comment 2 florian 2005-01-25 11:59:32 UTC 
Created attachment 21854 [details]
This is a workaraound patch
Comment 3 eric.bachard 2005-01-25 12:13:57 UTC 
I confirm, same problem here with SRC680_m71s1, build on Mac OSX 10.3.4 with
gcc-3.3, and Xcode 1.5

1) Reading your patch, loooks like there is missing code ?  (or not complete ? )
2) Can someone change this issue to "confirmed" (I have not enough rights) 

Thank you  :-) 


Regards,
eric bachard


Ericb -> Florian : maybe you can post shortly on dev@porting to inform other
devs you fill this issue ?
Comment 4 eric.bachard 2005-01-25 15:06:21 UTC 
Issue confirmed, changed to NEW

Same issue for Dominique Mores, one of french Mac OS X tester send me the same
log, with same issue too.  log not posted, because nearly the same as Florian or
mine.

Florian : I have read a lot about xmlsecurity on EIS, and we have to verify if
this bug is already fixed or not. The cws name is xmlsec07 ( about digital
signatures ), and you can find all on EIS, on "releases"


Regards,

-- 
ericb
Comment 5 florian 2005-01-25 15:24:54 UTC 
I get the same results using project xmlsecurity from cws xmlsec07. The problem seems to exist there, 
too.
Comment 6 eric.bachard 2005-01-25 18:52:13 UTC 
1) If I'm not wrong, not found any bugfix in xmlsec07 relative to this issue.
(Someone disagree ?) 

2) Florian's patch is ok for me  : after rebuild xmlsecurity and changed the new
binaries in /opt.../program and /opt..../program/resource, I now can open files
without crash.

Waiting for better changes, this bugfix is very usefull since we now can open
more types of files.

Thank's Florian !


Regards,
Comment 7 Martin Hollmichel 2005-01-31 09:39:33 UTC 
reassign
Comment 8 malte_timmermann 2005-02-02 13:05:23 UTC 
Fixed in xmlsec08...
Comment 9 malte_timmermann 2005-02-25 10:50:28 UTC 
MT->FST: MacOSX, so believe me...



re-open issue and try to reassign to fst
Comment 10 malte_timmermann 2005-02-25 10:50:36 UTC 
try to reassign to fst
Comment 11 malte_timmermann 2005-02-25 10:50:43 UTC 
try to reset resolution to FIXED
Comment 12 frank 2005-03-08 15:22:05 UTC 
For now I have to trust Malte that it's fixed
Comment 13 frank 2005-03-09 15:47:14 UTC 
set the target
Comment 14 frank 2005-04-04 13:50:25 UTC 
As far as I can tell fixed and integrated