Erik Moeller
Erik Moeller
Noted in #2507.
This will be addressed in the rewrite.
There are a couple of artifacts referenced in the docs already: - Downloadable equipment labels: https://docs.securedrop.org/en/release-0.12.2/hardware.html#labeling-equipment - Installation worksheet linked from: https://docs.securedrop.org/en/release-0.12.2/before_you_begin.html - Sample privacy policy: https://docs.securedrop.org/en/release-0.12.2/deployment/sample_privacy_policy.html I think the...
Since this issue was opened, some improvements have been implemented, such as auto-resuming downloads and displaying download progress. Further work on download reliability will focus on the rewrite; the download...
This will need to be implemented in the new client, though likely as a post-1.0.0 feature. Keeping open for now, but can be closed and re-scoped if needed.
We suspect (but don't know for sure) that double-encryption is very rare in practice. Given time constraints, I don't think we'll be able to build a user-friendly path here for...
Deferred again for now since it's a fairly rare case, but we'll aim to get to it in sprint n+1 or n+2.
The checkmark positioning looks great to me. How do you want to resolve naming ambiguity e.g. if there are two Mikes? Usernames are required to be identical, but first names...
This will need to be implemented in the new client, though likely as a post-1.0.0 feature. Keeping open for now, but can be closed and re-scoped if needed.
@deeplow Let us know how you're approaching this in the openQA context and if this is useful to keep open for tracking purposes.