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

4.3.2 SSL #7

Open
p-b-west opened this issue Feb 23, 2018 · 2 comments
Open

4.3.2 SSL #7

p-b-west opened this issue Feb 23, 2018 · 2 comments

Comments

@p-b-west
Copy link
Contributor

I find this section ambiguous.

Is this the necessary sequence.

  • Generate a self-signed root certificate for localhost, ensuring that the cert contains a Subject Alternative Name.

  • If the generated certificate is not in pem format, use openssl to convert to pem.

  • Use keytool to create a Java Keystore containing the self-signed certificate.

  • Add :ssl configuration to shadow-cljs.edn, either relying on the default values or specifying actual values.

@thheller
Copy link
Contributor

thheller commented Feb 23, 2018

Yeah that section is rough.

You need a trusted certificate for whichever host you are going to be using. Generating the cert could probably be automated. Getting the OS to trust it is the tricky part. I only got it working on macOS, which doesn't help me anymore since I'm now on Windows. Didn't figure out how to do it here yet.

keytool itself couldn't import the .p12 files generated by the macOS tool directly so I had to convert it first. This might not be required at all for other platforms. keytool can also generate certs but I didn't figure out how to get macOS to trust those.

I don't know what generating certs for testing is still so damn complicated.

I also switched to using undertow recently which I think is able to use pem files directly but I didn't test that enough yet.

@p-b-west
Copy link
Contributor Author

keytool itself couldn't import the .p12 files generated by the macOS tool directly so I had to convert it first.

I just got that to work. I had to have a password on the .p12 certificate, and I used the same password for the keystore.jks file, but it created the keystore without complaining.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants