New answers tagged

1

The server didn't accept the key your client provided. The client provided only "/Users/kosmos/.ssh/id_rsa_old", guessing that's not the key that's in your authorized_keys file on the remote server. Check the auth.log on the server, it should contain something helpful as to why. If the public key for that id_rsa_old is in your authorized_keys file on that ...


2

Would echo everything that gf_ said. However, to answer the question, yes you can. By default Let's Encrypt recreates the key and the cert at renewal. This makes implementing HPKP difficult if you want to pin at the leaf, which you probably should do in case intermediate changes (like it did in March 2016). So you've several options around this if you ...


3

Some words of caution to begin with: Know what you're doing, if you're planing to implement HPKP. If you don't do it right, or "if bad things happen", which aren't under your control, you might render your domain unusable. Be sure to test your setup with a domain which isn't that important, or with a very short cache time, like ten seconds for example. ...



Top 50 recent answers are included