4 ms·

I agree with your concern. As a temporary "workaround" I've updated the article with a SHA256 checksum of the key. I'll chase the Nginx team for serving this ke

I agree with your concern. As a temporary "workaround" I've updated the article with a SHA256 checksum of the key. I'll chase the Nginx team for serving this key over https

schoen 11y ago
Thanks for the update!
click170 11y ago
We should really be verifying the fingerprint of the key itself, even if it is served over HTTPS.