thestig: is this working as intended? Seems like more of a feature request than a security bug to me.

It's a prevention against shooting oneself in the foot, and not a robust security measure. The document asks the viewer to not save it unprotected, and its up to the viewer to comply. But there will always be ways around this, and a web search for "saving password protected pdf without password" gives a lot of alternate ways of doing the same thing. 

It would be nice to do this, but I agree with comment 2.

A web search will provide you ways to break security , It doesn't mean you
can't secure a feature.

It doesn't ask a user whether it is saving it with protection or not .

If chrome is providing a feature to browse a protected PDF document like
adobe reader it should handle all the scenarios I believe .


On Thursday 24 November 2016, thes… via monorail <monorail+v2.1931360713@
chromium.org
<javascript:_e(%7B%7D,'cvml','monorail%2Bv2.1931360713@chromium.org');>>
wrote:

 Issue 729141  has been merged into this issue.

I'm going to mark this as wontfix, because the design of the feature is so fundamentally flawed as to be worthless.  

Restating the situation:

Authors of PDFs can fool themselves into thinking that they can restrict certain features like printing or copying through the password mechanism, but there is no way for the mechanism to actually make the guarantee. The problem is that PDF has spec'd something that's not possible to achieve in the real world.