| Summary: | Make okular bruteforce all its kdewallet-stored passwords on new pdfs which require one. | ||
|---|---|---|---|
| Product: | [Applications] okular | Reporter: | blibberblubb <twinbase> |
| Component: | general | Assignee: | Okular developers <okular-devel> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | wishlist | CC: | twinbase |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
blibberblubb
2008-11-08 17:55:35 UTC
Bruteforcing passwords for a corner-case like your? Sorry, it won't be. If you need to manager your password in a smarter way, use KWalletManager. Okular do and will use at most only one password (its own) for every document. This is hardly a corner case.. recurring passwords from the same author are quite common. What would be indeed useful and clean is storing a password per document author, and try that single password, no "bruteforcing" involved. Anyway, this could be easily done in a wrapper script, if only okular supported a --password option. If you don't care about security that is.. Well, I'm sorry I used the "brute-force" term. In my humble opinion it would be quite useful for say, governments which use the same password for their documents on a per-month basis, or a group of persons working on a project, using the same passwords.. The suggestion by Ionut Ciocirlanm, setting it up in a "Try passwords per author" way would perfectly suit my needs and at least eases those other usecases. So I reopen this wish as it still appears valid and not so much corner-caseish to me. Trying passwords per author, other than being nonsense, it quite weak as reference to the document itself. It people or entities reuse the same password for many documents, that's their "fault". Okular will not do any job in relating two different documents, especially when it comes to passwords. Sorry. |