Thank you. Is there any place where is documented how to get the new ssh key for the host whenever this happens again?
El lunes, 31 de octubre de 2016, 8:54:29 (UTC+1), François escribió: > > Add > trac.sagemath.org,104.197.143.230 ecdsa-sha2-nistp256 > AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBG+/AO490umZWuczUgClP4BgFm5XR9I43z4kf9f+pu8Uj6UvH/7Pz1oBkJ71xET+xTmecBHB2c9OwlgPjB70AB8= > > > as a single line at the end of .ssh/know_hosts > > François > > > On 31/10/2016, at 20:52, Marco Cognetta <cognett...@gmail.com > <javascript:>> wrote: > > > > There is no longer a line with trac.sagemath.org but when I try to > connect I do not get the option of adding it to the list of known_hosts. I > had this problem a few weeks ago and was able to fix it but I have > forgotten how... > > > > Thanks for your help thus far! > > > > On Monday, October 31, 2016 at 4:36:35 PM UTC+9, François wrote: > > Then, it may have been the wrong host. > > You should remove the line starting with > > trac.sagemath.org > > Once removed, the next time you connect to the trac > > server, you will be asked about adding it to the list of > > know_hosts. > > > > François > > > > > On 31/10/2016, at 20:27, Marco Cognetta <cognett...@gmail.com> wrote: > > > > > > I have done that but I still get the same error. How do I get the > correct information to put in known_hosts? > > > > > > On Monday, October 31, 2016 at 4:14:23 PM UTC+9, François wrote: > > > Removing the 4th line in your file > > > ~/.ssh/known_hosts > > > looks like it would do the trick. > > > I think it would be the 4th line but it could be > > > another one. It will almost certainly be another one > > > for other people. > > > > > > François > > > > > > > On 31/10/2016, at 20:10, Marco Cognetta <cognett...@gmail.com> > wrote: > > > > > > > > What is the fix for this? I have tried getting the updated trac and > testing my rsa keys. > > > > > > > > On Saturday, October 29, 2016 at 2:33:05 AM UTC+9, Dima Pasechnik > wrote: > > > > > > > > > > > > On Friday, October 28, 2016 at 5:01:54 PM UTC, jhonrubia6 wrote: > > > > Is not 104.197.143.230? > > > > > > > > > > > > > > > > OnoSendaiII:sage J_Honrubia$ host trac.sagemath.org > > > > > > > > trac.sagemath.org has address 104.197.143.230 > > > > > > > > > > > > the IP might have remained, but the (virtual) machine got changed, > and got SSH keys regenerated. > > > > > > > > > > > > > > > > > > > > El jueves, 27 de octubre de 2016, 20:29:30 (UTC+2), John Cremona > escribió: > > > > The machine hosting trac did change recently. > > > > > > > > On 27 October 2016 at 19:17, jhonrubia6 <javier_...@hotmail.com> > wrote: > > > > > After working on ticket #21052, I committed the changed file and > tried to > > > > > git trac push and get the error > > > > > > > > > > git_trac.git_error.GitError: git returned with non-zero exit code > (128) when > > > > > executing "git push trac > > > > > HEAD:refs/heads/u/jhonrubia6/add_pictures_to_implicit_plot3d_py" > > > > > > > > > > STDERR: > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > > > > > > > > > > STDERR: @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! > @ > > > > > > > > > > STDERR: > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > > > > > > > > > > STDERR: IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! > > > > > > > > > > STDERR: Someone could be eavesdropping on you right now > > > > > (man-in-the-middle attack)! > > > > > > > > > > STDERR: It is also possible that a host key has just been > changed. > > > > > > > > > > STDERR: The fingerprint for the ECDSA key sent by the remote > host is > > > > > > > > > > STDERR: SHA256:4Op/q3b5792x+F1lHSKRi5UIORAPDlIFVA5cUq9YVXI. > > > > > > > > > > STDERR: Please contact your system administrator. > > > > > > > > > > STDERR: Add correct host key in > /Users/J_Honrubia/.ssh/known_hosts to > > > > > get rid of this message. > > > > > > > > > > STDERR: Offending ECDSA key in > /Users/J_Honrubia/.ssh/known_hosts:4 > > > > > > > > > > STDERR: ECDSA host key for trac.sagemath.org has changed and > you have > > > > > requested strict checking. > > > > > > > > > > STDERR: Host key verification failed. > > > > > > > > > > STDERR: fatal: Could not read from remote repository. > > > > > > > > > > STDERR: > > > > > > > > > > STDERR: Please make sure you have the correct access rights > > > > > > > > > > STDERR: and the repository exists. > > > > > > > > > > > > > > > git trac config works fine without errors. > > > > > > > > > > but > > > > > > > > > > OnoSendaiII:sage J_Honrubia$ ssh g...@trac.sagemath.org info > > > > > > > > > > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > > > > > > > > > > @ 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 a host key has just been changed. > > > > > > > > > > The fingerprint for the ECDSA key sent by the remote host is > > > > > > > > > > SHA256:4Op/q3b5792x+F1lHSKRi5UIORAPDlIFVA5cUq9YVXI. > > > > > > > > > > Please contact your system administrator. > > > > > > > > > > Add correct host key in /Users/J_Honrubia/.ssh/known_hosts to get > rid of > > > > > this message. > > > > > > > > > > Offending ECDSA key in /Users/J_Honrubia/.ssh/known_hosts:4 > > > > > > > > > > ECDSA host key for trac.sagemath.org has changed and you have > requested > > > > > strict checking. > > > > > > > > > > Host key verification failed. > > > > > > > > > > > > > > > Any clue? > > > > > > > > > > -- > > > > > 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+...@googlegroups.com. > > > > > To post to this group, send email to sage-...@googlegroups.com. > > > > > Visit this group at https://groups.google.com/group/sage-devel. > > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > -- > > > > 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+...@googlegroups.com. > > > > To post to this group, send email to sage-...@googlegroups.com. > > > > Visit this group at https://groups.google.com/group/sage-devel. > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > > -- > > > 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+...@googlegroups.com. > > > To post to this group, send email to sage-...@googlegroups.com. > > > Visit this group at https://groups.google.com/group/sage-devel. > > > For more options, visit https://groups.google.com/d/optout. > > > > > > -- > > 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+...@googlegroups.com <javascript:>. > > To post to this group, send email to sage-...@googlegroups.com > <javascript:>. > > Visit this group at https://groups.google.com/group/sage-devel. > > For more options, visit https://groups.google.com/d/optout. > > -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
