Next in thread → Next in month →

[OASIS Issue Tracker] Updated: (OFFICE-3709) ODF 1.3: PackageEncryption Enhancements

From
OASIS Issues Tracker <>
Date
2011-08-22T18:43:57+00:00
ID
1803864172.12071314038624379.JavaMail.tomcat55@mw00
Thread
[OASIS Issue Tracker] Updated: (OFFICE-3709) ODF 1.3: PackageEncryption Enhancements
[ http://tools.oasis-open.org/issues/browse/OFFICE-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Weir  updated OFFICE-3709:
---------------------------------

    Affects Version/s: ODF 1.2 COS 1
                           (was: ODF 1.2)
           Resolution: Member-submitted proposal for ODF 1.3

> ODF 1.3: Package Encryption Enhancements
> ----------------------------------------
>
>                 Key: OFFICE-3709
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3709
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Improvement
>          Components: Packaging, Part 3 (Packages), Security
>    Affects Versions: ODF 1.2 COS 1
>         Environment: This is an enhancement, described in terms of changes to OpenDocument-v1.2-cs01-part3
>            Reporter: Dennis Hamilton
>            Assignee: Dennis Hamilton
>             Fix For: ODF 1.3 CSD 01
>
>
> In the default encryption method for packages, the same start-key, the SHA1 digest of the user-entered-password, is used for all key generations for encrypting the individual parts of the package.  Although the start-key is a secret, its successful attack permits decryption of the entire package.
> This proposal adds a method by which the start key is different for every key generation, relying on the cryptographically-random and different manifest:salt that is created for each key generation.  This means that successful attack of one start key does not provide the start key for any of the other encryptions.
> Note: This procedure does not materially impact attacks on the user-specified password, which remain at least as vulnerable as memorable passwords generally are.
> In addition, the proposal adds an additional manifest:checksum-type that is salted in a way that avoids production of duplicate checksums for the same-plaintext files in different encrypted documents, reducing any attack surface that the detection of same-plaintext files may offer..

-- 
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
Next in thread → Next in month →