ICEpdf
  1. ICEpdf
  2. PDF-366

Outline items not corretly decoded

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.2.2
    • Fix Version/s: 5.1
    • Component/s: Core/Parsing
    • Labels:
      None
    • Environment:
      any

      Description

      The PDF located on the forums has a outline that is not correctly decoded. I've taken a quick look but nothing seems out of place on first look. The PDF is encrypted, but when looking at the default outline encoding it almost looks like the outline title isn't actually encrypted.

        Activity

        Patrick Corless created issue -
        Patrick Corless made changes -
        Field Original Value New Value
        Salesforce Case []
        Fix Version/s 5.0 [ 10314 ]
        Fix Version/s 4.3 [ 10266 ]
        Hide
        Patrick Corless added a comment -

        A second sample file was added by the user.

        Show
        Patrick Corless added a comment - A second sample file was added by the user.
        Patrick Corless made changes -
        Fix Version/s 5.0.1 [ 10872 ]
        Fix Version/s 5.0 [ 10314 ]
        Patrick Corless made changes -
        Fix Version/s 5.1 [ 10675 ]
        Patrick Corless made changes -
        Fix Version/s 5.0.1 [ 10872 ]
        Repository Revision Date User Message
        ICEsoft Public SVN Repository #42577 Wed Sep 17 13:57:20 MDT 2014 patrick.corless PDF-366 fixed an issue where HexStringObject are not correctly decoded when unencrypted.
        Files Changed
        Commit graph MODIFY /icepdf/branches/icepdf-5.0.1/icepdf/core/src/org/icepdf/core/pobjects/HexStringObject.java
        Hide
        Patrick Corless added a comment -

        Both samples document are encrypted and the document meta data is hex encoded. It would appear that e are looking at a very old bug where getDecryptedLiteralString() for HextStringObjects uses the string hex data for encryption ration then the literal string. Once I make this change the outline and document meta data loads correctly.

        Show
        Patrick Corless added a comment - Both samples document are encrypted and the document meta data is hex encoded. It would appear that e are looking at a very old bug where getDecryptedLiteralString() for HextStringObjects uses the string hex data for encryption ration then the literal string. Once I make this change the outline and document meta data loads correctly.
        Hide
        Patrick Corless added a comment -

        We don't have a lot of test cases for this but after referring to the specification we do indeed need to convert to literal string before unencrypting.

        Show
        Patrick Corless added a comment - We don't have a lot of test cases for this but after referring to the specification we do indeed need to convert to literal string before unencrypting.
        Patrick Corless made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Patrick Corless made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Patrick Corless
            Reporter:
            Patrick Corless
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: