New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 724100 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 725267
Owner: ----
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Compat



Sign in to add a comment

Chrome PDF Viewer does not support 256-bit AES (level8) PDF any more

Reported by shima...@gmail.com, May 18 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3100.0 Safari/537.36

Example URL:
http://www.broadband-xp.com/test/chrome/chrome256.pdf

Steps to reproduce the problem:
1. Access to http://www.broadband-xp.com/test/chrome/chrome256.pdf
2. 
3. 

What is the expected behavior?
To view the PDF without any password prompt.

What went wrong?
I see a password prompt. Futhermore, even if I input the right password (= 12345), Chrome PDF Viewer won't open the PDF.

Does it occur on multiple sites: N/A

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 60.0.3100.0  Channel: dev
OS Version: 6.3
Flash Version: 

Even if the PDF is encrypted, if it does not have any open password set, Google Chrome should not ask the password.
 

Comment 1 by shima...@gmail.com, May 18 2017

Chrome stable version does not show this problem.

Comment 2 by shima...@gmail.com, May 18 2017

As for 256-bit AES (level 3) PDF, even Chrome dev version does not suffer from this problem.

Comment 3 by shima...@gmail.com, May 21 2017

59.0.3071.61(Official Build)beta (bit) shows this problem as well.
Components: Internals>Plugins>PDF
This is probably  bug 725267 . Let me verify...
Cc: pbomm...@chromium.org abdulsyed@chromium.org
Labels: M-59 ReleaseBlock-Stable OS-Chrome OS-Linux OS-Mac
Status: Available (was: Unconfirmed)
Mergedinto: 725267
Status: Duplicate (was: Available)
Wait, of course it is. Sorry we didn't notice this bug report earlier.

Sign in to add a comment