In light of the Debian OpenSSL security issue
(http://lists.debian.org/debian-security-announce/2008/msg00152.html)
I've regenerated the server keys, even though they weren't affected
according to the tools provided by the debian folks to check if the
keys where blacklisted. Better safe than sorry and all that.
The new key fingerprints are:
67:fc:12:1f:e6:23:42:c7:9e:be:8a:2b:40:63:32:c3 (dsa)
49:60:1f:71:90:8b:cc:48:a2:29:f8:a2:3a:1a:53:43 (rsa)
When you try to push you'd see a message like this:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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)! It is also possible that the RSA host key has just been
changed.
Remove gitorious.org from your ~/.ssh/known_hosts and on the next push
check that the fingerprints match the above, and accept if they do.
Thank you for your understanding.
- Johan
The SSH daemon was upgraded around that time.
> I have deleted and re-added my (RSA) key at gitorious once more, but
> this did not seem to change anything.
>
> I'm using SSH, version OpenSSH_4.6p1 Debian-5ubuntu0.4, OpenSSL 0.9.8e
> 23 Feb 2007
What's your key fingerprint? There's a couple that's been blacklisted
because if the debian issue. Have you regenerated your keys according
to the debian/ubuntu security advisory (see
http://www.ubuntu.com/usn/usn-612-2)? I strongly encourage any Debian
and Ubuntu users to that.
>
> Regards,
> David.
Cheers,
JS