OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (OFFICE-3466) ODF 1.2 CD05-110.4.4 <draw:image> xlink:href case Repudiatable

    [ http://tools.oasis-open.org/issues/browse/OFFICE-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21972#action_21972 ] 

Robert Weir  commented on OFFICE-3466:

Of course, I could prepare a document using an odd font of my own creation that shows the glyphs YES when giving the Unicode code points for NO!.  This would not show the same way to different users, and could only be solved be embedding fonts.

And even then you could imagine a devious video driver that did something similar even with the correct fonts.

Caching doesn't help because I could have an app that puts false info into the cache.

You'll find dozens of similar issues.  These are really not things we're going to address in the file format.  

You also need to keep in mind the context of a digital signature.  If someone tries to repudiate a signed document, it ends up in court and expert witnesses, etc., will be brought out to explain what really happened.  This is the same as with a normal physical signature.  It doesn't prevent forgers or invisible ink or whatever.  But in cases of dispute you end up in court.

For external href's, the "meaning" of the document is clear -- If the imagine is external, it is subject to changes in that external image, ownership of tat website, DNS, Registrar domain transfers, etc.

> ODF 1.2 CD05-1 10.4.4 <draw:image> xlink:href case Repudiatable
> ---------------------------------------------------------------
>                 Key: OFFICE-3466
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3466
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Graphics, Part 1 (Schema), Security
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Dennis Hamilton
>             Fix For: ODF 1.2 CD 06
> When the xlink:href form of <draw:image> is used, the image is not captured in the document markup.
> That means that any digital signature of the markup does not include the image that may have been presented to the user, it only includes the xlink:href that is not to content that is part of the signed material.
> In this case, an user that requests the document be signed may believe that the image that is presented is included in that signature.  Alternatively, an user can repudiate that the document with a particular image presented is the one that was signed, because the image itself is not covered by the document signature.
> One way for a producer to safeguard that is to include a cache of the image that was rendered (if it was rendered) in the <draw:image> element in some way.  There is no provision for such a means of assuring, by it being included in the signature, that the user signed the document as seen when that particular image was presented.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]