pinentry should be able to check whether new passphrases satisfy the passphrase constraints before sending the passphrase to the gpg-agent, so that the user can modify the new passphrase without having to retype it completely. This check should only be performed if the passphrase constraints are enforced.
Description
Description
Revisions and Commits
Revisions and Commits
rG GnuPG | |||
rG9832566e4512 agent: Add checkpin inquiry for pinentry | |||
rG5976d293ef9b agent: Add checkpin inquiry for pinentry | |||
rP Pinentry | |||
rPd285c2cb1f61 qt: Make sure the message box is centered on top of the pinentry | |||
rPfefd730651b6 qt: Improve message shown if passphrase does not satisfy constraints | |||
rPf622321df5bb qt: Cancel timeout on more user interactions | |||
rPb0969ef692ac qt: Check passphrase constraints before accepting passphrase | |||
rP8f5d4532fbd6 Add support for passphrase constraints options and checkpin inquiry |
Status | Assigned | Task | ||
---|---|---|---|---|
Resolved | • aheinecke | T5517 Improvements for symmetric encryption | ||
Resolved | • ikloecker | T5532 pinentry: Add support for checking passphrase constraints to pinentry-qt |
Event Timeline
Comment Actions
Notification when trying to enter passphrase that does not satisfy multiple constraints:
Notification when trying to enter passphrase that is too short:
Notification when trying to enter empty passphrase:
Notification when trying to enter passphrase that does not satisfy multiple constraints:
Notification when trying to enter passphrase that is too short: