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-2727) ODF 1.2 Part 3 4.8.7manifest:key-size units, constraints, and defaults

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

Michael Brauer commented on OFFICE-2727:

The proposal is okay for me, except that
- We don't need individual sections for describing different default values. We elsewhere also do that within a single section.
- I have difficulties with the algorithm dependent default. We should either make the attribute mandatory for <manifest:start-key-generation>, or agree on a single value, although this means that the value has to be specified in many cases. The only possible default here seems to be 20, since that is compatible with ODF 1.1. See also OFFICE-2741.
- We should use the same formulation for default values that we use elsewhere: 
For a <manifest:start-key-generation> element the default value for this attribute is 20.
For a <manifest:key-derivation> element the default value for this attribute is 16.

> ODF 1.2 Part 3 4.8.7 manifest:key-size units, constraints, and defaults
> -----------------------------------------------------------------------
>                 Key: OFFICE-2727
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2727
>             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: The optional manifest:key-size attribute is introduced with ODF 1.2.  This issue is described specifically against the text in ODF 1.2 CD05 Part 3.
>            Reporter: Dennis Hamilton
>            Assignee: Dennis Hamilton
>             Fix For: ODF 1.2 CD 06
> Key sizes are typically expressed in bits or octets (the number of consecutive 8-bit groups contained in the key) and are regarded as big-endian numbers.  No size unit is specified for the manifest:key-size attributes, but examination of current implementations indicates that the value is a number of octets.   Those units and how short keys are extracted from algorithms that produce longers ones needs to be explicit.
> There are also natural constraints on key sizes, either because an algorithm produces a fixed-size result or because an algorithm to which the key will be supplied has constraints on the sizes of keys it accepts.  These effects need to be accounted for in some way.

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]