-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
Conversation
Better explaination for --pass parameter in documentation for elasticsearch-certutil.
Pinging @elastic/es-security |
@elasticmachine test this please |
There was a problem hiding this 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 '='). |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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.
@vikene Do you think you'll have a chance to look at this again, or would prefer that we pick it up internally? |
@tvernum I am sorry missed those notification, sure. I will do those changes asap. |
Closing in favour of #40137 |
Better explaination for --pass parameter in documentation for elasticsearch-certutil.
Resolves: #35285