On 2014-08-07, Volker Braun <vbraun.n...@gmail.com> wrote: > ------=_Part_2987_239550037.1407372253692 > Content-Type: text/plain; charset=UTF-8 > > You should be getting: > > The authenticity of host 'trac.sagemath.org (128.208.178.249)' can't be > established. > ECDSA key fingerprint is 21:ba:10:2a:59:cd:7d:36:f7:4c:52:bf:fc:5e:0e:07. > Are you sure you want to continue connecting (yes/no)? > > Type "yes" when you see it the first time. The trac server's public key is > then saved and used in future connections to avoid man-in-the-middle > attacks. > > The "content of the public key file" is the whole content. > The "foo@bar.local" is just an arbitrary comment for you to remember what > that key is, anything else must match exactly.
there is some weirdness going on here; for me the key type is RSA, not ECDSA. (and fingerprint is different) Please also see the conversation at the bottom of #12375. > > > > On Tuesday, August 5, 2014 6:38:53 PM UTC+1, Paul Graham wrote: >> >> When i type in >> ssh g...@trac.sagemath.org info >> >> It says: >> >> The authenticity of host 'trac.sagemath.org (some IP address)' can't be >> established. >> ECDSA key fingerprint is (some hex string). >> Are you sure you want to continue connecting (yes/no)? >> >> I am new to this process and wasn't sure whether or not its safe to write >> down the IP address and hext string in the above message. But i dont know >> what to do with thiat message, as id like to get up and running. >> >> And relating to this, step 5. in the Manually Linking your Public Key to >> your Trac Account section of the dev guide: >> >> 5. Paste the content of your public key file (e.g. ~/.ssh/id_rsa.pub) >> >> I wasn't sure whether to copy and paste just the random string by itself, >> or the whole thing including the "ssh-rsa" and "foo@bar.local" parts, as >> like i said before, this is new to me :) >> >> Example key (not mine) taken from: >> http://git-scm.com/book/en/Git-on-the-Server-Generating-Your-SSH-Public-Key >> >> ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAklOUpkDHrfHY17SbrmTIpNLTGK9Tjom/ >> BWDSUGPl+nafzlHDTYW7hdI4yZ5ew18JH4JW9jbhUFrviQzM7xlELEVf4h9lFX5QVkbPppSwg0cda3 >> >> Pbv7kOdJ/MTyBlWXFCR+HAo3FXRitBqxiX1nKhXpHAZsMciLq8V6RjsNAQwdsdMFvSlVK/7XA >> t3FaoJoAsncM1Q9x5+3V0Ww68/eIFmb1zuUFljQJKprrX88XypNDvjYNby6vw/Pb0rwert/En >> mZ+AW4OZPnTPI89ZPmVMLuayrD2cE86Z/il8b+gw3r3+1nKatmIkjn2so1d01QraTlMqVSsbx >> NrRFi9wrf+M7Q== foo@bar.local >> >> > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
