Dennis,
uhm, perhaps I'm missing something here.
I'm not looking at the manifest at all, only at the zip.
There *is* a zip entry called "Configurations/menubar/".
Unzipping the .odt would map it to empty directories, but directories are actually
also files (probably this is what you meant, David ?), so indeed they should also
be signed.
Best regards,
Bart
________________________________________
From: Dennis E. Hamilton []
Sent: Sunday, September 26, 2010 12:08 AM
To: Hanssens Bart; 'David LeBlanc';
Cc: Cornelis Frank
Subject: RE: [office] RE: XAdES support in ODF
Bart, there is no Zip entry like "Configurations/menubar/". The only way
for there to be a Zip entry is for there to be a Zip directory entry with
that name, and that means there would have to be a file in the package that
had that name.
There might be such a META-INF/manifest.xml <manifest:file-entry>, just as
there is for "/", but that isn't relevant to the signature procedure so long
as it isn't for a file in the Zip.
What am I missing?
- Dennis
-----Original Message-----
From: Hanssens Bart [mailto:]
Sent: Saturday, September 25, 2010 14:32
To: David LeBlanc; ;
Cc: Cornelis Frank
Subject: RE: [office] RE: XAdES support in ODF
[ ... ]
So that leaves us with zip entries like "Configurations/menubar/", if they
are to be signed, then it should
IMHO be reflected in the spec (I wouldn't call this "a file", and the spec
only says "shall contain a
<ds:Reference> element for each *file*" - 1.2cd05 part 1, but perhaps I'm
misinterpreting "file" in this
context)
[ ... ]
