Steps to repro: 0) Open http://acroeng.adobe.com/Test_Files/security/MacUpperAsciiPasswords/MyOpenPasswordIs_gar%C3%A7on.pdf in evince 1) Type the correct password, "garçon" Result: Error: Incorrect password Error: Couldn't read xref table Poppler 0.4.x branch from today. Works fine in xpdf 3.01.
Created attachment 3365 [details] [review] add password support to test-poppler-glic So you can actually try this in poppler :)
Neither does the poppler decrypt its own test case at http://webcvs.freedesktop.org/*checkout*/poppler/test/unittestcases/PasswordEncrypted.pdf?rev=1.1
(In reply to comment #2) burner@phoenix:~/Desktop$ evince PasswordEncrypted.pdf Error: Unsupported version/revision (4/4) of Standard security handler Error: Incorrect password (I do type 'password' when evince asks). burner@phoenix:~/Desktop$ evince --version Gnome evince 0.5.2 burner@phoenix:~/Desktop$ pkg-config --modversion poppler 0.5.1
I recently stumbled on a file that gave me the same problem. The password contained the letter 'ä' that was encoded with iso-latin 1 (gives the number 227) and when I try to write the same character in evince on my FC5-system I get the utf-encoded caracheter instead (numbers 195 and 164). XPDF handles the problem fine but I have not looked at the code to see if it defaults to latin-1 or if it does some clever encoding-conversions. I think this is unrelated to the problem with comment #2 as the test-case is with a unsupported version of the protocol but I bet it is the same encoding-trouble that chpe is reporting.
The problem with #4 is probably that we don't support AES128 encryption yet.
This looks like an 8-bit cleanliness problem.
I have done some investigation - the password needs to be in Latin1 encoding to work correctly.
Works in Qt4 (if you do the right encoding), so the problem isn't in poppler. Either this in an evince problem after all, or the glib front end needs to be enhanced.
Fixed in both master and poppler-0.6.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.