[gs-bugs] [Bug 691256] OwnerPassword and UserPassword don't work as device parameters

bugzilla-daemon at ghostscript.com bugzilla-daemon at ghostscript.com
Mon Sep 27 15:23:19 UTC 2010


http://bugs.ghostscript.com/show_bug.cgi?id=691256

--- Comment #2 from Ray Johnston <ray.johnston at artifex.com> 2010-09-27 15:23:18 UTC ---
I think this is similar to the problem that pdfwrite opens, but never closes
until Ghostscript exits (we have an open enhancement for that).

The .setdevice (and setpagedevice) both are defined as clearing the current
page of any marks, so we shouldn't have to check to see if the page is
'marked'. Thus, I would guess this statement from Ken would be operable:

> pdfwrite really needs to have the encryption
> filter set up before anything starts making marks; on the other hand, as long
> as the setpagedevice is encountered before any marking operations then it
> would be valid to alter the passwords.

Specifically, we can assume that the page is not marked (actually discard
any previous marking operations prior to the setpagedevice/.setdevice action.

There may be an issue that we don't (in the pdfwrite device) know when this
occurs, and maybe we need to have the pdfwrite put_params close the device
when certain parameters get set (such as passwords) just as raster devices
close when the geometry or color depth changes so the device gets re-opened
and can reestablish with the new parameters.

I suggest further discussion on IRC if needed to make sure I am understanding
the issue correctly.

-- 
Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the gs-bugs mailing list