-
Notifications
You must be signed in to change notification settings - Fork 58
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
when creating a root CA, get SAN error on key creation #1
Comments
Yep that's definitely a bug. Creating a root CA should at least work with the default values. |
The issue is caused by newer versions of OpenSSL which enforce subjectAltName in all certificates.
Certainly some thought needs to be spent on a sane default for this. |
@redredgroovy any chance of getting this or something similar merged? |
@redredgroovy anything? @hakt0r any chance you could create a pull request to this repo from your fork? It looks like the pull request you created on Sep 21, 2017 is against your own fork |
So I tried @hakt0r 's fix, made a presumptive PR (sorry about that) and it still isn't working. I'm looking forward to a solution though, I really need this to work right now ;-) Thanks. |
I can confirm that #3 works for me |
when running
create-root-ca -d $ROOT_CA_DIR
, on a default Raspbian distro, from current HEAD (97d8496), I get a config file error during RSA key generation. I don't have the full text of the error, but it's essentially aSTR_COPY:variable has no value:conf_def:584:line 91
and line 91 of ca.conf issubjectAltName = $ENV::SAN
. If I export an env var SAN="DNS.1=blah" etc, the key creation, and thus create-root-ca, succeeds.I don't know if I missed something from the README, but if I have not, something should be added to it, or a default value etc provided so an initial run doesn't fail, or if it fails, it fails with some guidance to the user.
The text was updated successfully, but these errors were encountered: