Skip to content

Commit

Permalink
Remove references to flag-for-reply
Browse files Browse the repository at this point in the history
  • Loading branch information
rocodes committed Jun 28, 2021
1 parent f813de4 commit 030a1e0
Showing 1 changed file with 0 additions and 7 deletions.
7 changes: 0 additions & 7 deletions docs/admin/known_issues.rst
Original file line number Diff line number Diff line change
Expand Up @@ -27,13 +27,6 @@ Current known issues
- Printer support is limited to specific models by Brother and HP, and printing
different file types is not as reliable yet as under Tails. Support for
additional non-networked printers will be added in a future release.
- "Flag for reply" functionality is not implemented in the *SecureDrop Client*.
This is used when a source's reply key was not created on their first
submission and needs to be created on their next visit.
If you are logged into the SecureDrop Client, and the reply feature for a
source is disabled for more than a minute, they must be flagged for reply in
the *Journalist Interface* - see the `SecureDrop "Flag for Reply"
documentation <https://docs.securedrop.org/en/stable/journalist.html#flag-for-reply>`_ for more information.
- Currently, only app-based two-factor authentication (TOTP) is supported.
- The SecureDrop Client can only be configured with a single *Submission Key*.
If the *Submission Key* for your SecureDrop server was rotated in the past,
Expand Down

0 comments on commit 030a1e0

Please sign in to comment.