Hi,
We’re having trouble opening some 256Bit AES encrypted documents. Error reported is:
Permissions check failed (invalid Perms value).
The document opens fine in Acrobat and Nuance.
File is: Test Document AES256.pdf (25.0 KB)
Password is: 123456
Using the following Call
new Aspose.Pdf.Document(File, “123456”)
Other 256Bit pdfs and other encryption levels work fine. Using Aspose PDF 19.4.0.0
Thanks for contacting support.
We have tested the scenario with Aspose.PDF for .NET 19.5 and were able to replicate the issue that your have mentioned. For the sake of correction, we have logged it under the ticket ID PDFNET-46498 in our issue tracking system. We will further look into details of the issue and keep you posted with its rectification status. Please be patient and spare us little time.
We are sorry for the inconvenience.
Hello,
Just wondering how to keep track of ticket PDFNET-46498?
Your issue has been logged recently under free support model and is pending for analysis at the moment. We will keep you posted within this forum thread as soon as some certain news are available on its resolution. Please spare us little time.
We are sorry for the inconvenience.
Is PDFNET-46498 still open?
Yes, the ticket is still opened and we regret to share that we could not resolve it due to other urgent issues. We will surely let you know as soon as we have some significant updates regarding ticket resolution. Please spare us little time.
We are sorry for the inconvenience.
Hi Aspose,
It’s been a year and a half. Is the issue still being looked at. We’re using 20.11 now and it’s still showing the same behavior on some AES256 documents
We really regret to share that earlier logged ticket could not get resolved due to other issues logged prior to it. However, we have updated its information by recording your concerns and escalated it to the next level. We will certainly let you know as soon as we have additional updates regarding its fix. We highly appreciate your patience and comprehension in this regard.
We apologize for the inconvenience.
Thank you. What is meant by “next level”? Do I need to keep posting for it not to be forgotten like it was previously?
Please note that we do not neglect or leave any of the reported issues unresolved. We resolve every logged issue however, the resolution time depends upon various factors to be noticed like the support model under which they are logged, the nature and complexity of the issue, number of the API internal components related to the issue, etc.
By “next level”, we meant that we had increased the issue priority and will consider your concerns to schedule the issue fix as soon as possible. We will soon try to share some ETA with you regarding issue resolution. Please accept our humble apology for the inconvenience faced.
How soon will we receive the ETA to resolve this issue?
We will be able to share some reliable ETA once the issue is completely investigated. We regret to inform you that the ticket logged for the issue has not been fully analyzed yet. As soon as the fix against this issue is scheduled, we will inform you in this forum thread. We really appreciate your cooperation and patience in this regard.
We apologize for the inconvenience being caused.
Sadly, the ticket has not been yet resolved. We will inform you in this forum thread as soon as some news is available about its resolution or ETA. We apologize for the inconvenience.
The issues you have found earlier (filed as PDFNET-46498) have been fixed in Aspose.PDF for .NET 24.11.