Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[docs] Journalist guide assumes that submission key requires a passphrase #4122

Closed
eloquence opened this issue Feb 12, 2019 · 0 comments · Fixed by #4413
Closed

[docs] Journalist guide assumes that submission key requires a passphrase #4122

eloquence opened this issue Feb 12, 2019 · 0 comments · Fixed by #4413
Labels
docs

Comments

@eloquence
Copy link
Member

The journalist guide currently states:

A prompt will ask you for the application PGP key passphrase to decrypt the document.

Aside from the inconsistent phrasing (see #2579), this assumption is not warranted. The SVS docs state that it is safe to generate the submission key without a passphrase, and they explain the process for doing so.

This statement therefore needs to be qualified to avoid confusion.
@eloquence eloquence added the docs label Feb 12, 2019
eloquence added a commit that referenced this issue May 7, 2019
@eloquence
Standardize Submission Key language and usage
ba2f23c 
This also revises the SVS instructions slightly (nowhere else
do we explicitly instruct people to use the SVS for _generating_
journalist keys, and in this context it feels more confusing than
helpful). It renames a file that used the old "application key"
term.

I chose to use the shorter "Submission Key" instead of
"SecureDrop Submission Key" since other terms like
*Journalist Workstation* are also SecureDrop-specific, and the
convention to italicize such terms makes it reasonably clear
that they carry a context-specific meaning.

Resolves #2579
Resolves #4122
eloquence added a commit that referenced this issue May 7, 2019
@eloquence
Standardize Submission Key language and usage
990b591 
This also revises the SVS description slightly (nowhere else
do we explicitly instruct people to use the SVS for _generating_
journalist keys, and in this context it feels more confusing than
helpful). It renames a file that used the old "application key"
term.

I chose to use the shorter "Submission Key" instead of
"SecureDrop Submission Key" since other terms like
*Journalist Workstation* are also SecureDrop-specific, and the
convention to italicize such terms makes it reasonably clear
that they carry a context-specific meaning.

Resolves #2579
Resolves #4122
@eloquence eloquence mentioned this issue May 7, 2019
Merged
1 task
kushaldas pushed a commit that referenced this issue Sep 25, 2019
@eloquence @kushaldas
Standardize Submission Key language and usage
d7f4740 
This also revises the SVS description slightly (nowhere else
do we explicitly instruct people to use the SVS for _generating_
journalist keys, and in this context it feels more confusing than
helpful). It renames a file that used the old "application key"
term.

I chose to use the shorter "Submission Key" instead of
"SecureDrop Submission Key" since other terms like
*Journalist Workstation* are also SecureDrop-specific, and the
convention to italicize such terms makes it reasonably clear
that they carry a context-specific meaning.

Resolves #2579
Resolves #4122
@eloquence eloquence mentioned this issue Oct 20, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
docs
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[docs] Standardize Submission Key language and usage freedomofpress/securedrop
1 participant
@eloquence