Open NateChoe1 opened 1 month ago
For what it's worth, I'm pretty sure every Netlify website has the same public key, so you probably shouldn't use that as an authentication mechanism. I'd recommend creating a PGP key and publishing that instead.
For what it's worth, I'm pretty sure every Netlify website has the same public key,
Oh wow! This is vital information. Thank you so much for bringing it up!
I'd recommend creating a PGP key and publishing that instead.
Sadly, I'd have to sign the entire website for that to take effect. I find it difficult to extract a representation of the website that's convenient for checking. And since I haven't purchased a domain name, there seems to be no good way of authenticating myself. I'll remove the public key thing for now.
Using
openssl x509
, I was able to extract this information about your public keyAs far as I can tell, the public key has changed to
04 64 c3 ab 83 a1 9f 9b f7 ff e5 00 bf 41 ae cd d1 cd 1c 5d 8d 4d 62 fb 0e e4 90 33 13 2d b5 45 91 e6 7a 26 a0 5e 01 ae 25 84 fb d5 88 23 7e 13 7e a9 d3 a5 de 69 2d 91 69 c3 12 86 5a 94 02 42 28
.