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

Issue 754: cert with SHA512 #810

Closed
wants to merge 2 commits into from
Closed

Issue 754: cert with SHA512 #810

wants to merge 2 commits into from

Conversation

juergenzimmermann
Copy link

See discussion at #754

@juergenzimmermann
Copy link
Author

@shakyShane the -subj section just provides the answers which you submitted interactively.

@shakyShane
Copy link
Contributor

Ahh oh ok. Thanks very much :)

@shakyShane
Copy link
Contributor

Will get this in asap

@shakyShane
Copy link
Contributor

screen shot 2015-09-07 at 09 40 19

@shakyShane
Copy link
Contributor

^ what I see using those certs...

@juergenzimmermann
Copy link
Author

192.168.xx.xx is our ip domain. I've no idea how OpenSSL is introducing the ip address into the cert. I'll try my 2 commands as mentioned in issue 754 instead of your adapted shell script.

@shakyShane
Copy link
Contributor

It's my ip domain also. But, it also gives me that error if I access it through localhost:3000 or the ip you see above

@juergenzimmermann
Copy link
Author

I tried these commands as you can see at https://github.com/juergenzimmermann/browser-sync/tree/cert_sha512/lib/server/certs. 2 CI checks are still pending.

openssl genrsa -out server.key 8192
openssl req -new -x509 -sha512 -key server.key -out server.crt -days 3650 -subj "/CN=localhost/O=Internet Widgits Pty Ltd/ST=Some-State/C=AU"

@jonricaurte
Copy link

This does not work for me either. It says your connection to address is encrypted using an obsolete cipher suite.

@shakyShane shakyShane closed this Oct 22, 2015
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

Successfully merging this pull request may close these issues.

None yet

3 participants