when i try to log into my BBB by connecting it to my raspberry pi i get a warning that says remote host identification has changed. i am using sudo ssh 192.168.7.2 to log in and thats when i get the error.
but if i try logging in using sudo ssh 192.168.6.2 it gives me the log in on the terminal as root@192.168.6.2 and ask for a password. i try temppwd nothing. i trying root nothing. i try just hitting enter and nothing.
when i use my windows machine i can log in using putty and 192.168.7.2 and i can log in as either debian or root.
any suggestions?
Never mind i figured it out
sudo ssh 193.168.7.2 -l debian
Then used temppwd that worked
when i try to log into my BBB by connecting it to my raspberry pi i get a warning that says remote host identification has changed.
That’s ssh warning you… hey something changed… make sure your connecting to what you actually want to, then reset the error message. (Debian tells you how to fix it…)
i am using sudo ssh 192.168.7.2 to log in
sudo ssh …
Don’t do that, call ssh as normal user, doing ‘sudo’ is a terrible habit for normal user programs.
and thats when i get the error.
but if i try logging in using sudo ssh 192.168.6.2 it gives me the log in on the terminal as root@192.168.6.2 and ask for a password. i try temppwd nothing. i trying root nothing. i try just hitting enter and nothing.
root user has been disabled by default for a few years now, it’s password was never that. (It was worse… root )
when i use my windows machine i can log in using putty and 192.168.7.2 and i can log in as either debian or root.
any suggestions?
Run, this to see if it even came up on the Pi…
sudo ifconfig -a
Otherwise, how exactly are your powering your BBB plugged into the Pi? BBB needs 5v 1a…
Most Pi power supplies aren’t rated for Pi plus 1A more…
My bet, your power starved…
Regards,
when i try to log into my BBB by connecting it to my raspberry pi i get a
warning that says remote host identification has changed. i am using sudo
ssh 192.168.7.2 to log in and thats when i get the error.
but if i try logging in using sudo ssh 192.168.6.2 it gives me the log in
on the terminal as root@192.168.6.2 and ask for a password. i try temppwd
nothing. i trying root nothing. i try just hitting enter and nothing.
when i use my windows machine i can log in using putty and 192.168.7.2 and
i can log in as either debian or root.
any suggestions?
Don't use sudo ssh!
Do this instead:
ssh debian@192.168.6.2
The password for user debian is temppwd.
Silly question: why do you need "sudo"? (Oh, is that 193 a typo? The
normal private LAN prefix is 192.168).
The only thing I can see that getting you is that SSH will attempt to
pass the credentials of the root user as the login to the BBB end. Without
"sudo" it would have defaulted to passing credentials as the R-Pi regular
user (pi, if you haven't changed it). Passing the target (BBB) login name
supercedes either of those defaults.
I haven't checked the syntax for SSH in Linux, but under Windows it
appears that using "user@address"
C:\Users\Wulfraed>ssh debian@192.168.7.2
The authenticity of host '192.168.7.2 (192.168.7.2)' can't be established.
ECDSA key fingerprint is
SHA256:K22aW35XI0ZGh32/KHvHQTsCDl7hRzRHGuuoKJ8EtNU.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.7.2' (ECDSA) to the list of known
hosts.
Debian GNU/Linux 9
does the same as the "address -l user" option (and is actually documented
in the Debian ssh command:
usage: ssh [-1246AaCfGgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec]
[-D [bind_address:]port] [-E log_file] [-e escape_char]
[-F configfile] [-I pkcs11] [-i identity_file]
[-J [user@]host[:port]] [-L address] [-l login_name] [-m
mac_spec]
[-O ctl_cmd] [-o option] [-p port] [-Q query_option] [-R
address]
[-S ctl_path] [-W host:port] [-w local_tun[:remote_tun]]
[user@]hostname [command]
I've never dug into SSH deep enough to set up security files on both
ends. With the proper security entries AND with identical user names on
both ends, "ssh hostname" is sufficient to connect and log-in with no
password prompts. But since BBB default is to lock out root login, and the
user accounts are different "debian" vs "pi", such a feature isn't useful
-- it makes sense in an environment where every computer has been
configured with every username...
>Never mind i figured it out
>sudo ssh 193.168.7.2 -l debian
>Then used temppwd that worked
Silly question: why do you need "sudo"? (Oh, is that 193 a typo? The
normal private LAN prefix is 192.168).
The only thing I can see that getting you is that SSH will attempt to
pass the credentials of the root user as the login to the BBB end. Without
"sudo" it would have defaulted to passing credentials as the R-Pi regular
user (pi, if you haven't changed it). Passing the target (BBB) login name
supercedes either of those defaults.
I haven't checked the syntax for SSH in Linux, but under Windows it
appears that using "user@address"
Same for Linux. This is "standard" for ssh.