@creepy_owlet No, I did notice...
... but I am wondering why this went by so easily.
@creepy_owlet No, I did notice...
... but I am wondering why this went by so easily.
@gbraad
Because most people just "press ok to close that damn warning" ?
@creepy_owlet
$ git clone git@github.com:gbraad/vmproxy.git
Cloning into 'vmproxy'...
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
@gbraad have you missed the whole "GitHub put their server private RSA key in a GitHub repo and had to change it urgently" drama?
@gbraad
I know, but even then, you should only do that if you can verify in some official place what the fingerprint should be... But most guys I see in IT just type yes it delete "offending" keys. ¯\_(ツ )_/¯
@creepy_owlet
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.