If user has manually unlocked USB drive, don't re-prompt for pasphrase #1462
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
If a user has unlocked their Export device (i.e. via the commandline or by opening Nautilus in
sd-devices
and inputting the passphrase), recognize that the drive is unlocked and don't ask again for passphrase before exporting documents.Returns a status code from the disk checks run in
sd-export
(This will also enable us to incorporate other response/status codes, for example to distinguish between LUKS and Veracrypt devices, in future).Note Changes must be tested with corresponding changes in
sd-export
and released together.Fixes #1734 (Together with corresponding sd-export PR)
Towards freedomofpress/securedrop-workstation#265
Test Plan
TK
Checklist
If these changes modify code paths involving cryptography, the opening of files in VMs or network (via the RPC service) traffic, Qubes testing in the staging environment is required. For fine tuning of the graphical user interface, testing in any environment in Qubes is required. Please check as applicable:
If these changes add or remove files other than client code, the AppArmor profile may need to be updated. Please check as applicable:
If these changes modify the database schema, you should include a database migration. Please check as applicable:
main
and confirmed that the migration applies cleanlymain
and would like the reviewer to do so