RE: ODF 1.2 signatures and [xml-names] support

["Dennis E. Hamilton" <dennis.hamilton@acm.org>]

Wow.  According to that bugzilla report, the XML parser used does not implement namespaces and the namespace prefixes are hard-coded as part of element and attribute names.  I would hope that is no longer the case, but ...

It will be easy to test this case for packages (just change things in manifest.xml) for two resiliency cases: using a default namespace on the manifest elements (but not the attributes of course), and use a *different* namespace prefix instead of "manifest:".  

That is so tempting, I must do something about that before the next meeting.  It is also fairly easy to transform a meta.xml, styles.xml and even content.xml that has default and different prefix bindings for a namespace.

 - Dennis

PS: The meta:generator shouldn't be altered.  That way it is covered by the signature properly.  In fact, nothing should be altered except the signatures file.  There may be other signatures already and you don't want to break them.  [;<).

-----Original Message-----
From: plugtest-bounces@opendocsociety.org [mailto:plugtest-bounces@opendocsociety.org] On Behalf Of Hanssens Bart
Sent: Tuesday, July 26, 2011 05:29
To: ODF Plugfest mailinglist
Cc: Cornelis Frank
Subject: [ODFPlugtest] ODF 1.2 signatures

[ ... ]



2) And as you might know, OOo has an issue with namespace prefixes in documentsignatures and ignores the signature altogether:
http://openoffice.org/bugzilla/show_bug.cgi?id=107864



3) LibreOffice 3.4.2rc (Win7 - 64 bit) even crashes on the signed file (not on the unsigned)

Problem signature:
  Problem Event Name:	BEX
  Application Name:	soffice.bin
  Application Version:	3.4.201.500
  Application Timestamp:	4e1cbc9f
  Fault Module Name:	MSVCR90.dll
  Fault Module Version:	9.0.30729.6161
  Fault Module Timestamp:	4dace5b9
  Exception Offset:	0006ccd5
  Exception Code:	c0000417
  Exception Data:	00000000
  OS Version:	6.1.7601.2.1.0.256.4
  Locale ID:	2067
  Additional Information 1:	4935
  Additional Information 2:	4935eb945911156e9147882956d0c814
  Additional Information 3:	e15d
  Additional Information 4:	e15d0a9b8da56cc48a6d0c5c0a27b7da


4) Questions: should the <meta:generator> be updated (since the signature was added) or not ?
(as the content isn't actually updated, just signed)



Perhaps someone could test it in Symphony  / Calligra / MS-Office etc ?



Best regards

Bart