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.

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

Improve documentation for --pass param to certutil #35432

Closed
wants to merge 1 commit into from

Conversation

vikene
Copy link
Contributor

@vikene vikene commented Nov 10, 2018

Better explaination for --pass parameter in documentation for elasticsearch-certutil.
Resolves: #35285

Verified

This commit was signed with the committer’s verified signature.
Kikobeats Kiko Beats
Better explaination for --pass parameter in documentation for elasticsearch-certutil.
@tvernum tvernum self-requested a review November 11, 2018 23:13
@tvernum tvernum added >docs General docs changes v7.0.0 :Security/TLS SSL/TLS, Certificates v6.6.0 v6.5.1 labels Nov 11, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security

@tvernum
Copy link
Contributor

tvernum commented Nov 11, 2018

@elasticmachine test this please

@tvernum tvernum changed the title Fix for Issue #35285 Improve documentation for --pass param to certutil Nov 11, 2018
Copy link
Contributor

@tvernum tvernum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @vikene, sorry it took so long to review this.

I think the way you've structured the information makes a lot of sense, but I've left some suggestions about the exact phrasing.

Keys stored in PKCS#12 format are always password protected.
Keys stored in PKCS#12 format are always password protected. However, it supports
the password to be _blank_. If you want to specify a _blank_ password without
prompt, use '--pass ""' (with no '=').
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the way this has been structured, but I think we can tighten up the wording a bit.
What do you think of:

Keys stored in PKCS#12 format are always password protected, however,
this password may be _blank_. If you want to specify a blank password
without a prompt, pass `--pass ""` (with no `=`) on the command line.

+
Keys stored in PEM format are password protected only if the
`--pass` parameter is specified. If you do not supply an argument for the
`--pass` parameter, you are prompted for a password.
`--pass` parameter, you are prompted for a password. It does not support having
_blank_ as password.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion

`--pass` parameter, you are prompted for a password.
Encrypted PEM files do not support blank passwords (if you do not
wish to password-protected your PEM keys, then do not specify
`--pass`). 

If you want to specify a _blank_ password (without prompting), use
`--pass ""` (with no `=`).
If there is a requirement to create an unencrypted PEM file skip '--pass'
parameter.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this advice can be incorporated into the paragraph above it.

@tvernum
Copy link
Contributor

tvernum commented Dec 17, 2018

@vikene Do you think you'll have a chance to look at this again, or would prefer that we pick it up internally?

@vikene
Copy link
Contributor Author

vikene commented Dec 19, 2018

@tvernum I am sorry missed those notification, sure. I will do those changes asap.

@tvernum
Copy link
Contributor

tvernum commented Mar 27, 2019

Closing in favour of #40137

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>docs General docs changes :Security/TLS SSL/TLS, Certificates v6.5.1 v7.2.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Documentation of elasticsearch-certutil is wrong for parameter --pass
6 participants