Ubuntu Core on Raspberry Pi ssh failed
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I am attempting to install and use the Ubuntu Core distro on a Raspberry Pi 3 for the first time.
My SD card is formatted in MS_DOS FAT and the the ISO is flashed onto the card.
I have gone through the process of attaching my Pi to a monitor and keyboard and supplying my Ubuntu One email address.
At the end of the process, the monitor supplies ssh details for connecting to the Pi.
I have also generated an id_rsa.pub key and supplied it to my Ubuntu One ssh keys area.
With all that done, when I try to ssh into the Pi, I get one of 2 messages.
The first message I got was:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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:QrfHNJLLJ4wjeQAPoVK+W0lhI7pfww3liCVI3/IoJCk.
Please contact your system administrator.
Add correct host key in /Users/userx/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /Users/userx/.ssh/known_hosts:29
ECDSA host key for 192.168.0.14 has changed and you have requested strict checking.
Host key verification failed.
After a while, it didn't report the above message but instead requested a password - which by definition Ubuntu Core is not supposed to utilise.
I need help please.
ssh ubuntu-core
edited Mar 14 at 11:31
pa4080
12.3k52256
asked Mar 14 at 11:20
sisko
1351110
add a comment |Â
up vote
0
down vote
favorite
I am attempting to install and use the Ubuntu Core distro on a Raspberry Pi 3 for the first time.
My SD card is formatted in MS_DOS FAT and the the ISO is flashed onto the card.
I have gone through the process of attaching my Pi to a monitor and keyboard and supplying my Ubuntu One email address.
At the end of the process, the monitor supplies ssh details for connecting to the Pi.
I have also generated an id_rsa.pub key and supplied it to my Ubuntu One ssh keys area.
With all that done, when I try to ssh into the Pi, I get one of 2 messages.
The first message I got was:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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:QrfHNJLLJ4wjeQAPoVK+W0lhI7pfww3liCVI3/IoJCk.
Please contact your system administrator.
Add correct host key in /Users/userx/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /Users/userx/.ssh/known_hosts:29
ECDSA host key for 192.168.0.14 has changed and you have requested strict checking.
Host key verification failed.
After a while, it didn't report the above message but instead requested a password - which by definition Ubuntu Core is not supposed to utilise.
I need help please.
ssh ubuntu-core
edited Mar 14 at 11:31
pa4080
12.3k52256
asked Mar 14 at 11:20
sisko
1351110
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am attempting to install and use the Ubuntu Core distro on a Raspberry Pi 3 for the first time.
My SD card is formatted in MS_DOS FAT and the the ISO is flashed onto the card.
I have gone through the process of attaching my Pi to a monitor and keyboard and supplying my Ubuntu One email address.
At the end of the process, the monitor supplies ssh details for connecting to the Pi.
I have also generated an id_rsa.pub key and supplied it to my Ubuntu One ssh keys area.
With all that done, when I try to ssh into the Pi, I get one of 2 messages.
The first message I got was:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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:QrfHNJLLJ4wjeQAPoVK+W0lhI7pfww3liCVI3/IoJCk.
Please contact your system administrator.
Add correct host key in /Users/userx/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /Users/userx/.ssh/known_hosts:29
ECDSA host key for 192.168.0.14 has changed and you have requested strict checking.
Host key verification failed.
After a while, it didn't report the above message but instead requested a password - which by definition Ubuntu Core is not supposed to utilise.
I need help please.
ssh ubuntu-core
edited Mar 14 at 11:31
pa4080
12.3k52256
asked Mar 14 at 11:20
sisko
1351110
I am attempting to install and use the Ubuntu Core distro on a Raspberry Pi 3 for the first time.
My SD card is formatted in MS_DOS FAT and the the ISO is flashed onto the card.
I have gone through the process of attaching my Pi to a monitor and keyboard and supplying my Ubuntu One email address.
At the end of the process, the monitor supplies ssh details for connecting to the Pi.
I have also generated an id_rsa.pub key and supplied it to my Ubuntu One ssh keys area.
With all that done, when I try to ssh into the Pi, I get one of 2 messages.
The first message I got was:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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:QrfHNJLLJ4wjeQAPoVK+W0lhI7pfww3liCVI3/IoJCk.
Please contact your system administrator.
Add correct host key in /Users/userx/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /Users/userx/.ssh/known_hosts:29
ECDSA host key for 192.168.0.14 has changed and you have requested strict checking.
Host key verification failed.
After a while, it didn't report the above message but instead requested a password - which by definition Ubuntu Core is not supposed to utilise.
I need help please.
ssh ubuntu-core
ssh ubuntu-core
edited Mar 14 at 11:31
pa4080
12.3k52256
asked Mar 14 at 11:20
sisko
1351110
edited Mar 14 at 11:31
pa4080
12.3k52256
asked Mar 14 at 11:20
sisko
1351110
edited Mar 14 at 11:31
pa4080
12.3k52256
edited Mar 14 at 11:31
pa4080
12.3k52256
edited Mar 14 at 11:31
pa4080
12.3k52256
12.3k52256
asked Mar 14 at 11:20
sisko
1351110
asked Mar 14 at 11:20
sisko
1351110
asked Mar 14 at 11:20
sisko
1351110
1351110
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
1
down vote
accepted
Delete known Hosts under ~/.ssh/known_hosts then try to reconnect. You should upload the public keys before you start Ubuntu Core configuration.
answered Mar 14 at 13:30
Rustam Isaev
514
The key I'm uploading is the contents of id_rsa.pub. However there is a known_hosts file which contains multiple keys from other ssh connections. Do I need to generate my Ubuntu One key in known_hosts and not id_rsa.pub ???
– sisko
Mar 14 at 14:24
Have you tried to use "ssh-keygen -R" command?
– mariaczi
Mar 14 at 14:27
Yes indeed! ssh-keygen -R 192.168.0.14
– sisko
Mar 14 at 14:53
The only thing I did differently in my initial attempts was setting the ssh-key after I configured the Raspberry Pi
– sisko
Mar 15 at 20:55
add a comment |Â
up vote
2
down vote
As you can read in this message you have saved this host in your know_hosts file. So now, you should remove it:
ssh-keygen -R IP_of_your_RPI
and after that try to ssh to your RPI.
But please remember, that you cann't have possibility to ssh to them on root account. It depends on ssh daemon configuration: "PermitRootLogin" option in /etc/sshd_config file.
answered Mar 14 at 11:26
mariaczi
31915
I have tried you solution before posting and again after reading your post. When I execute the ssh again, I'm asked to confirm I want to continue connecting and I of course respond 'yes'. However, I'm then asked for a password. I don't have one and from what I've read there shouldn't be a password request
– sisko
Mar 14 at 14:21
Which username are you using to SSH in? It should be the developer name you chose when creating your Ubuntu One account.
– Kyle
Mar 14 at 14:40
The username on the personal details page
– sisko
Mar 14 at 16:14
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Delete known Hosts under ~/.ssh/known_hosts then try to reconnect. You should upload the public keys before you start Ubuntu Core configuration.
answered Mar 14 at 13:30
Rustam Isaev
514
The key I'm uploading is the contents of id_rsa.pub. However there is a known_hosts file which contains multiple keys from other ssh connections. Do I need to generate my Ubuntu One key in known_hosts and not id_rsa.pub ???
– sisko
Mar 14 at 14:24
Have you tried to use "ssh-keygen -R" command?
– mariaczi
Mar 14 at 14:27
Yes indeed! ssh-keygen -R 192.168.0.14
– sisko
Mar 14 at 14:53
The only thing I did differently in my initial attempts was setting the ssh-key after I configured the Raspberry Pi
– sisko
Mar 15 at 20:55
add a comment |Â
up vote
1
down vote
accepted
Delete known Hosts under ~/.ssh/known_hosts then try to reconnect. You should upload the public keys before you start Ubuntu Core configuration.
answered Mar 14 at 13:30
Rustam Isaev
514
The key I'm uploading is the contents of id_rsa.pub. However there is a known_hosts file which contains multiple keys from other ssh connections. Do I need to generate my Ubuntu One key in known_hosts and not id_rsa.pub ???
– sisko
Mar 14 at 14:24
Have you tried to use "ssh-keygen -R" command?
– mariaczi
Mar 14 at 14:27
Yes indeed! ssh-keygen -R 192.168.0.14
– sisko
Mar 14 at 14:53
The only thing I did differently in my initial attempts was setting the ssh-key after I configured the Raspberry Pi
– sisko
Mar 15 at 20:55
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Delete known Hosts under ~/.ssh/known_hosts then try to reconnect. You should upload the public keys before you start Ubuntu Core configuration.
answered Mar 14 at 13:30
Rustam Isaev
514
Delete known Hosts under ~/.ssh/known_hosts then try to reconnect. You should upload the public keys before you start Ubuntu Core configuration.
answered Mar 14 at 13:30
Rustam Isaev
514
answered Mar 14 at 13:30
Rustam Isaev
514
answered Mar 14 at 13:30
Rustam Isaev
514
answered Mar 14 at 13:30
Rustam Isaev
514
514
The key I'm uploading is the contents of id_rsa.pub. However there is a known_hosts file which contains multiple keys from other ssh connections. Do I need to generate my Ubuntu One key in known_hosts and not id_rsa.pub ???
– sisko
Mar 14 at 14:24
Have you tried to use "ssh-keygen -R" command?
– mariaczi
Mar 14 at 14:27
Yes indeed! ssh-keygen -R 192.168.0.14
– sisko
Mar 14 at 14:53
The only thing I did differently in my initial attempts was setting the ssh-key after I configured the Raspberry Pi
– sisko
Mar 15 at 20:55
add a comment |Â
The key I'm uploading is the contents of id_rsa.pub. However there is a known_hosts file which contains multiple keys from other ssh connections. Do I need to generate my Ubuntu One key in known_hosts and not id_rsa.pub ???
– sisko
Mar 14 at 14:24
Have you tried to use "ssh-keygen -R" command?
– mariaczi
Mar 14 at 14:27
Yes indeed! ssh-keygen -R 192.168.0.14
– sisko
Mar 14 at 14:53
The only thing I did differently in my initial attempts was setting the ssh-key after I configured the Raspberry Pi
– sisko
Mar 15 at 20:55
The key I'm uploading is the contents of id_rsa.pub. However there is a known_hosts file which contains multiple keys from other ssh connections. Do I need to generate my Ubuntu One key in known_hosts and not id_rsa.pub ???
– sisko
Mar 14 at 14:24
The key I'm uploading is the contents of id_rsa.pub. However there is a known_hosts file which contains multiple keys from other ssh connections. Do I need to generate my Ubuntu One key in known_hosts and not id_rsa.pub ???
– sisko
Mar 14 at 14:24
Have you tried to use "ssh-keygen -R" command?
– mariaczi
Mar 14 at 14:27
Have you tried to use "ssh-keygen -R" command?
– mariaczi
Mar 14 at 14:27
Yes indeed! ssh-keygen -R 192.168.0.14
– sisko
Mar 14 at 14:53
Yes indeed! ssh-keygen -R 192.168.0.14
– sisko
Mar 14 at 14:53
The only thing I did differently in my initial attempts was setting the ssh-key after I configured the Raspberry Pi
– sisko
Mar 15 at 20:55
The only thing I did differently in my initial attempts was setting the ssh-key after I configured the Raspberry Pi
– sisko
Mar 15 at 20:55
add a comment |Â
up vote
2
down vote
As you can read in this message you have saved this host in your know_hosts file. So now, you should remove it:
ssh-keygen -R IP_of_your_RPI
and after that try to ssh to your RPI.
But please remember, that you cann't have possibility to ssh to them on root account. It depends on ssh daemon configuration: "PermitRootLogin" option in /etc/sshd_config file.
answered Mar 14 at 11:26
mariaczi
31915
I have tried you solution before posting and again after reading your post. When I execute the ssh again, I'm asked to confirm I want to continue connecting and I of course respond 'yes'. However, I'm then asked for a password. I don't have one and from what I've read there shouldn't be a password request
– sisko
Mar 14 at 14:21
Which username are you using to SSH in? It should be the developer name you chose when creating your Ubuntu One account.
– Kyle
Mar 14 at 14:40
The username on the personal details page
– sisko
Mar 14 at 16:14
add a comment |Â
up vote
2
down vote
As you can read in this message you have saved this host in your know_hosts file. So now, you should remove it:
ssh-keygen -R IP_of_your_RPI
and after that try to ssh to your RPI.
But please remember, that you cann't have possibility to ssh to them on root account. It depends on ssh daemon configuration: "PermitRootLogin" option in /etc/sshd_config file.
answered Mar 14 at 11:26
mariaczi
31915
I have tried you solution before posting and again after reading your post. When I execute the ssh again, I'm asked to confirm I want to continue connecting and I of course respond 'yes'. However, I'm then asked for a password. I don't have one and from what I've read there shouldn't be a password request
– sisko
Mar 14 at 14:21
Which username are you using to SSH in? It should be the developer name you chose when creating your Ubuntu One account.
– Kyle
Mar 14 at 14:40
The username on the personal details page
– sisko
Mar 14 at 16:14
add a comment |Â
up vote
2
down vote
up vote
2
down vote
As you can read in this message you have saved this host in your know_hosts file. So now, you should remove it:
ssh-keygen -R IP_of_your_RPI
and after that try to ssh to your RPI.
But please remember, that you cann't have possibility to ssh to them on root account. It depends on ssh daemon configuration: "PermitRootLogin" option in /etc/sshd_config file.
answered Mar 14 at 11:26
mariaczi
31915
As you can read in this message you have saved this host in your know_hosts file. So now, you should remove it:
ssh-keygen -R IP_of_your_RPI
and after that try to ssh to your RPI.
But please remember, that you cann't have possibility to ssh to them on root account. It depends on ssh daemon configuration: "PermitRootLogin" option in /etc/sshd_config file.
answered Mar 14 at 11:26
mariaczi
31915
answered Mar 14 at 11:26
mariaczi
31915
answered Mar 14 at 11:26
mariaczi
31915
answered Mar 14 at 11:26
mariaczi
31915
31915
I have tried you solution before posting and again after reading your post. When I execute the ssh again, I'm asked to confirm I want to continue connecting and I of course respond 'yes'. However, I'm then asked for a password. I don't have one and from what I've read there shouldn't be a password request
– sisko
Mar 14 at 14:21
Which username are you using to SSH in? It should be the developer name you chose when creating your Ubuntu One account.
– Kyle
Mar 14 at 14:40
The username on the personal details page
– sisko
Mar 14 at 16:14
add a comment |Â
I have tried you solution before posting and again after reading your post. When I execute the ssh again, I'm asked to confirm I want to continue connecting and I of course respond 'yes'. However, I'm then asked for a password. I don't have one and from what I've read there shouldn't be a password request
– sisko
Mar 14 at 14:21
Which username are you using to SSH in? It should be the developer name you chose when creating your Ubuntu One account.
– Kyle
Mar 14 at 14:40
The username on the personal details page
– sisko
Mar 14 at 16:14
I have tried you solution before posting and again after reading your post. When I execute the ssh again, I'm asked to confirm I want to continue connecting and I of course respond 'yes'. However, I'm then asked for a password. I don't have one and from what I've read there shouldn't be a password request
– sisko
Mar 14 at 14:21
I have tried you solution before posting and again after reading your post. When I execute the ssh again, I'm asked to confirm I want to continue connecting and I of course respond 'yes'. However, I'm then asked for a password. I don't have one and from what I've read there shouldn't be a password request
– sisko
Mar 14 at 14:21
Which username are you using to SSH in? It should be the developer name you chose when creating your Ubuntu One account.
– Kyle
Mar 14 at 14:40
Which username are you using to SSH in? It should be the developer name you chose when creating your Ubuntu One account.
– Kyle
Mar 14 at 14:40
The username on the personal details page
– sisko
Mar 14 at 16:14
The username on the personal details page
– sisko
Mar 14 at 16:14
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1014853%2fubuntu-core-on-raspberry-pi-ssh-failed%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password