Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
create SHA256 certs so browser devtools don't complain all the time #1707
Edit to @KaiRo-at: are you sure about that?? Although moving to sha256, we still have a self-signed cert so my suspicion about Chrome/Chromium & FF still with warnings. Did you have any test?
Edit to @KaiRo-at part 2: I'm used to check contributors (coders/testers/etc) profiles and try to understand -not "investigating"- because I think we're not numbers/accounts/bytes, but humans (yep, your blog!), so hope you'll enjoy and you'll stay! :)
Yes, it doesn't solve the self-signed cert issue (on initial connection), but browser (at least Firefox) developer tools complain at every request (including the API ones) if a SHA1 cert is used, no matter is self-signed or not, and no matter if an exception exists. And that is annoying when doing development work and trying to find real messages in the Web Console. That's why I looked into this in the first place. ;-)