2014-10-29 1 views
0

우분투의 정확한 32를 사용하고 14.04로 전환했습니다. Jeffrey Way의 설정 (https://github.com/JeffreyWay/Vagrant-Setup)을 사용합니다. 'vagrant ssh'를 실행하여 로그인하고 사용자 이름/암호 root/root를 사용하여 루트에 로그인 할 수 있습니다.방랑제에 다른 배포판을 설치했습니다. 이제는 SSH를 MySQL에 넣을 수 없습니다.

나는 GUI에 대한 속편 프로를 사용해보십시오, 나는 다음과 같은 오류가 발생합니다 :

Used command: /usr/bin/ssh -v -N -o ControlMaster=no -o ExitOnForwardFailure=yes -o ConnectTimeout=10 -o NumberOfPasswordPrompts=3 -i /Users/chrisfarrugia/.vagrant.d/insecure_private_key -o TCPKeepAlive=no -o ServerAliveInterval=60 -o ServerAliveCountMax=1 -p 2222 [email protected] -L 52688/127.0.0.1/3306 -L 52689/127.0.0.1/3306 

OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011 
debug1: Reading configuration data /etc/ssh_config 
debug1: /etc/ssh_config line 20: Applying options for * 
debug1: Connecting to 127.0.0.1 [127.0.0.1] port 2222. 
debug1: fd 3 clearing O_NONBLOCK 
debug1: Connection established. 
debug1: identity file /Users/chrisfarrugia/.vagrant.d/insecure_private_key type -1 
debug1: identity file /Users/chrisfarrugia/.vagrant.d/insecure_private_key-cert type -1 
debug1: Enabling compatibility mode for protocol 2.0 
debug1: Local version string SSH-2.0-OpenSSH_6.2 
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 
debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 pat OpenSSH* 
debug1: SSH2_MSG_KEXINIT sent 
debug1: SSH2_MSG_KEXINIT received 
debug1: kex: server->client aes128-ctr [email protected] none 
debug1: kex: client->server aes128-ctr [email protected] none 
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent 
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP 
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent 
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY 
debug1: Server host key: RSA 9d:7c:86:00:20:5a:ca:ef:a0:8a:01:c6:ad:34:cf:de 
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 
@ 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 RSA key sent by the remote host is 
9d:7c:86:00:20:5a:ca:ef:a0:8a:01:c6:ad:34:cf:de. 
Please contact your system administrator. 
Add correct host key in /Users/chrisfarrugia/.ssh/known_hosts to get rid of this message. 
Offending RSA key in /Users/chrisfarrugia/.ssh/known_hosts:1 
RSA host key for [127.0.0.1]:2222 has changed and you have requested strict checking. 
Host key verification failed. 

내가 잘못 여기서 뭐하는 거지? Sequel Pro에서 내 설정을 캡쳐 한 스크린 샷입니다. enter image description here

답변

3

내 대답을 찾았습니다. known_hosts 파일에서 이미 127.0.0.1에 대한 항목을 제거해야만했습니다.

파일 위치는 ~/.ssh/known_hosts입니다.

관련 문제