Sebas07

Thanks to whom it may concern. I downloaded the today's version and it did connect..

bedna, see - i tried your way on a raspi 3B+ with the last minimal armbian and it worked like your case like a charm - on my Win11 with putty. If you look a bit back to my post with the attached "ssh_debian.txt" - that is what I get when I use a debian as ssh client! ssh client and the odroid ssh server cannot agree on how to connect UNLESS I dumb it down as seen in the command line - and then "1234" is not accepted.. So - armbian "odroid XU4" does not behave like "raspi"!

hm yes. I am not a Linux guru and would have liked to get a base for an up-to-date omv8. For me to just burn a recent armbian image on a Odroid hc2 - what a schmuck can do based on simple how-to's - this is not it. I see that you would have to modify the sd card up-front with either a key entrance to ssh or with another user. Console is "out" for a headless install and I do not have an XU4 so that you could do console/hmi supported install first steps. I think I call it a day. Thanks for all the support.

Thank you for your comment. From a debian i can go to a stop with the reply of: "Unable to negotiate with xyz port 22: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1" If I dumb the system down I go to the password exchanges with the attached ssh debug and the system does not accept the "1234" password and stops then. edit - frustrating because another odroid bookworm with the same ssh config file is available like a charm... ssh_debian.txt

ok - so - by the book - burned one of the last bookworm images (Armbian_25.5.1_Odroidxu4_bookworm_current_6.6.88_minimal.img) - sshd-config file is attached (note "PubkeyAuthentication yes" and "#PasswordAuthentication yes" ) no connection - see attached "ssh_neu.txt" - can't negotiate the keything reburned image and changed the sshd config to "PubkeyAuthentication no" and "PasswordAuthentication yes" and got as ssh response the "ssh2.txt". So 2 times not even got to a password request. What to do ??? regards sshd-config.txt ssh_neu.txt ssh2.txt

bedna, that is not a "putty only" behavior. Attached the verbose output using the Win11 ssh client - same same I see only to pull the SD card, mount it on another linux system and then have a look at the ssh server and general system settings edit: i put that sd card into another SBC (odroid hc4), mounted that card, chroot, gave a passw to root, created another superuser etc. no change - ssh does not recognize any of these users. This is bad for morale.. ssh1.txt

ref. to Igor: I think the system runs fine because i can ping and because there is actually a ssh server active. Due to that I have a Odroid HC2 and not the XU4, I have no console and have to rely on ssh. I used putty and the ssh client in the "advanced IP scanner" - www.advanced-ip-scanner.com: both seem to connect but 1234 just does not work. In that Debian raspberry I used the normal ssh client and in WIN10/11 also the ssh client from the command line. All of these three ssh clients were not able to connect to the Odroid due to a different level of keystrength and procedure. I try the WIN11 ssh client to accept the situation and will come back edit: I needed to use these command options to connect to the ssh server from the WIN11 ssh client: ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 -oHostKeyAlgorithms=+ssh-dss -oCiphers=+aes128-cbc -oMACs=+hmac-sha1 That is a pile of ancient security settings! Anyway - even now the 1234 did not work. in verbose mode I got no alarms from the ssh connection

Thanks for the comments. Still no joy. I tried another SD card with etcher and then switched over to armbian imager. Same result: with putty you can connect through ssh, set "root" as username and then the "1234" is not accepted anymore. That also with another ssh client (not putty) and the Win11 built in one. Both ssh clients mention the low security of the sha1 systemin armbian and accept the override. P.S. - Same with one of the last bookworm images P.P.S - same using putty on a WIN10 system "login as: root further authentification required root@IP-address password: 1234 access denied" once more: tried ssh through a raspi in the network. the raspi cannot connect to the armbian: the raspi does not like to use diffie-hellman-group1-sha1 the raspi does not like to use ssh-dss does that tell anything?

that is why i am confused, I used the one image from here (armbian.com) https://www.armbian.com/odroid-xu4/ edit: what happens if the SBC starts the first time and you cut the power before hooking up with ssh - does it fall back to other credentials? P.P.S: did a new install and 1234 just got me a "access denied" on the first attempt directly after boot

Hello! I wanted to install the Armbian 26.2.1 Minimal / IOT to an Ordoid HC2 (using the XU4 distro). Download ok - sha hash is ok - balena etcher ok - startup - ok. Problem: When I log in the first time with "root", the "1234" as first password is not accepted. Also, PUTTY warns that ths ssh of the armbian uses only "Diffie-hellmann-group1-sha1" which (for PUTTY) is a bit unsecure. Any idea about the password issue?