ICEpdf
  1. ICEpdf
  2. PDF-1134

Encryption key generation regression

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 6.2.2
          • Fix Version/s: 6.2.3
          • Component/s: Security
          • Labels:
            None
          • Environment:
            Viewer RI

            Description

            The PDF in question contains an owner password and no users password. A use has noticed that if they open the permission dialog followed by the document information dialog there is a security exception.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Patrick Corless added a comment -

              The PDF contains an owner password which usually we don't access to render the document, instead we default to the user password which is an empty string by default. When the Permission dialog is opened we check the user and owner password which sets off a chain of calls which invalidated the default user password. This turns out to be an ordering issue in our calls.

              To minimize any further changes to the encryption code making a simple change to the PermissionsDialog fixed the issue. Calling isOwnerAuthorized first will invalidate the encryption key but a following call to isUserAuthorized() will reinstate the default user password and create a valid encryption key.

              Show
              Patrick Corless added a comment - The PDF contains an owner password which usually we don't access to render the document, instead we default to the user password which is an empty string by default. When the Permission dialog is opened we check the user and owner password which sets off a chain of calls which invalidated the default user password. This turns out to be an ordering issue in our calls. To minimize any further changes to the encryption code making a simple change to the PermissionsDialog fixed the issue. Calling isOwnerAuthorized first will invalidate the encryption key but a following call to isUserAuthorized() will reinstate the default user password and create a valid encryption key.
              Hide
              Permalink
              Patrick Corless added a comment -

              Fix applied to 6.2 branch and trunk

              Show
              Patrick Corless added a comment - Fix applied to 6.2 branch and trunk

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved: