signature example

Bart,


The scenario is interesting!


I double checked the sample files. Sure, OO/Symphony will ignore "dsig" and "ds" prefixes and no warning. That should be the implementation issue. I can not remember when the latest spec changes have been added. Maybe OO/Sym implement the old spec.


Of course, another issue for digital signature is a known issue. Sym is based on OO3.1 which does not sign mimetype and manifest.xml in ODF package, so have interoperability issues with OO3.2+ versions. I've checked OO3.2 code, there are 76 source files changed, so it is not a simple bug fix. You know the reason for this issue is because digital signature spec is changing and OO3.1/Sym implements the old spec.


BTW, what is the password for the several encrypted sample files?:-)


Best Regards,


Mingfei Jia(贾明飞)

IBM Lotus Symphony Development

IBM China Software Development LAB, Beijing

Tel: 86-10-82452493   Fax: 86-10-82452887

NOTES:Ming Fei Jia/China/IBM   E-mail: 

Address: No.28 Building, Zhong Guan Cun Software Park, No.8 Dong Bei Wang West Road, ShangDi, Haidian District, Beijing 100193, P.R.China 

Hanssens Bart ---2010-06-17 18:20:14---Hi,






From:

Hanssens Bart <>



To:

"" <>



Date:

2010-06-17 18:20



Subject:

[odf-interop-tech] signature example





Hi,



By the way, completely unrelated to the java eid applet, I've created a very small signing script

in Groovy, using only the standard Java SE libraries, plus a dummy certificate store (so you

don't need an eID card)


It's been a while, but's in the OIC svn:


http://tools.oasis-open.org/version-control/browse/wsvn/oic/TestSuite/branches/barth/odf12/misc/#_TestSuite_branches_barth_odf12_misc_


I have to update it a little bit, and change it so you don't have to add the documentsignatures.xml

manually to the ODF package



Now, last time I've checked OOo / Symphony did not add the dsig and ds prefixes suggested

(mandated ?) by the latest ODF 1.2 spec (and just ignored signatures that did use the correct

prefixes, no warning or error, just... nothing). To be checked !



Anyway, about a signature scenario, what about a timesheet:


- lpOD script generating a document with a table (or just a spreadsheet) with the days of the

month and some nice headings + fields / cells were one can fill out his / her name etc

it is stored in the "to be filled out" directory


- Symphony user ("the consultant") filling out the hours for this month, 210 in total, and signing

the ODF, stores it in "filled out" directory


- ODFDom parsing signed document, checking if total of hours / month exceeds 200 hours,

and moves it to "to be approved" directory


- OpenOffice user ("the boss") signs the document for approval, and copies it to "approved"

directory


- ODFDom checks the two signatures, creates a short summary document and copies it

to "management" directory


- KOffice mobile user ("the CFO") reads the document




(Yes, I realize all this could be done using html/forms... but you'd surprised how many

document-flows are still around)




Best regards


Bart








---------------------------------------------------------------------

To unsubscribe from this mail list, you must leave the OASIS TC that

generates this mail.  Follow this link to all your TCs in OASIS at:

https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php