Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OWNER PASSWORD REQUIRED ERROR #28

Closed
palewire opened this issue Oct 19, 2011 · 7 comments
Closed

OWNER PASSWORD REQUIRED ERROR #28

palewire opened this issue Oct 19, 2011 · 7 comments
Labels

Comments

@palewire
Copy link
Contributor

Anything I can do to blow through this?

$ docsplit pages fileName.pdf
Error: Failed to open PDF file: 
   fileName.pdf
   OWNER PASSWORD REQUIRED, but not given (or incorrect)
Errors encountered.  No output created.
Done.  Input errors, so no output created.
@jashkenas
Copy link
Member

Yep -- try qpdf --decrypt ... or use Preview to open it, and then to Print -> Save as PDF.

If you can't open it in Preview without the password, then it's truly locked down.

@palewire
Copy link
Contributor Author

Thanks. Would it be possible to bake this into docsplit? I feel more than obliged to contribute at this point.

@jashkenas
Copy link
Member

Hmm. Perhaps it would. We'd have to be able to detect the password protection ... but maybe a try/catch is good enough for getting that done. It would also be one more dependency, so making it optional would be ideal: if qpdf is installed, enable the feature, otherwise, no worries.

@palewire
Copy link
Contributor Author

My Ruby fu is weaker than a Drake rhyme, but would that be somewheres around here?

@jashkenas
Copy link
Member

Yep: https://github.com/documentcloud/docsplit/blob/master/lib/docsplit.rb#L104

But that doesn't tell you why it broke, so we don't just want to catch all exceptions ... only the ones where the PDF has an encryption problem.

@jashkenas jashkenas reopened this Oct 19, 2011
@palewire
Copy link
Contributor Author

Okay. I have to grind some work stuff yet today, but I'll try to get back to this and stop being a total leech.

@palewire
Copy link
Contributor Author

Closing as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants