-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
EASYRSA_NO_PASS conflict with --passin and --passout #835
Comments
@seblu Thank you for reporting this issue. I understand the issue and think your proposal is a good approach:
|
Here is a draft patch to test:
|
Testing #839 welcome. |
Linking #733 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the current master, we can define
EASYRSA_NO_PASS
in thevars
file to enable globally --nopass.but the code checking for mutual exclusions is before loading variables from the
vars
file.As a consequence, a command exporting a pkcs12 file is generated with blank password with no warning.
In this case of exporting a p12, most UI do not accept empty password, and the best UX for easyrsa would be to let the global variable
EASYRSA_NO_PASS
to be overrided by command line when needed.The text was updated successfully, but these errors were encountered: