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-2721) ODF 1.2 Part 3CD01-rev08 Contradictory <manifest:algorithm> provisions

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

Dennis Hamilton commented on OFFICE-2721:

I apologize for the confusion about <Encryption Method>.  There is no <Encryption Method> element now.  We use <manifest:algorithm> as a counterpart of the <Encryption Method> which is where details of the different manifest:algorithm-name values are handled in [xmlenc-core].  I was only suggesting that if we allow additional elements under <manifest:algorithm>, that they be ones provided for as children of <Encryption Method> in [xmlenc-core].

Since we are allowing new elements in <manifest:algorithm> in section 3.4.1, we need to do something in the schema about that.  Section 4.5 and the schema say that <manifest:algorithm> has no child elements.

I agree that we are not providing an alternative encryption, so we now must resulve the conflict between 3.4.1 and 4.5.

Whether we call the Blowfish CFB and Password Based encryption that it is tied to "default" or "legacy" doesn't matter here.  We should treat that separately.  Either way, we need to resolve the conflict between 3.4.1 and 4.5+schema, and also affirm that the extensibility does not apply to Blowfish CFB and the Password Based Encryption it is tied to.

> ODF 1.2 Part 3 CD01-rev08 Contradictory <manifest:algorithm> provisions
> -----------------------------------------------------------------------
>                 Key: OFFICE-2721
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2721
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Packaging, Part 3 (Packages), Security
>    Affects Versions: ODF 1.2 CD 05
>         Environment: This issue applies to ODF 1.2 Part 3 CD01-rev08.odt in conjunction with the latest manifest schema.  It applies to the ODF 1.2 draft4 Part 3 approved to become Part 3 of the combined Public Review CD.
>            Reporter: Dennis Hamilton
>            Assignee: Dennis Hamilton
>             Fix For: ODF 1.2 CD 06
> In ODF 1.2 Par 3 CD01-rev08.odt (ODF 1.2 draft4 Part 3), 
> 1. Section 2.1.1(B.3) requires that the META-INF/manifest.xml file conform to the schema provided in Appendix A.
> 2. Section 4.5 <manifest:algorithm> and the schema confirm that <manifest:algorithm> has no elements.
> 3. Section 3.4.1 confirms that OpenDocument Package Consumers and Producers may employ additional algorithms beyond those established as the defaults in section 3.4.2.  Section 4.5 <manifest:algorithm> text stipulates that there may be additional elements as required to support different encryption algorithms as if <manifest:algorithm> were an <EncryptionMethod> element of [xmlenc-core] associated with the provided <manifest:algorithm> manifest:algorithm-name attribute value.
> 4. Although incorporation of elements from [xmlenc-core] is stated, there is no discussion of how namespace considerations apply.
> NOTE: The simplicity or complexity of resolution of this conflict depends on whether or not an alternative full-package encryption methodology is introduced in place of encryptions that deal with the individual Zip contents individually.

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]