Sebas07 Posted 21 hours ago Posted 21 hours ago 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? 0 Quote
Werner Posted 18 hours ago Posted 18 hours ago Armbian default login and password is always root and 1234. If this does not work, the image is not genuine. 0 Quote
Sebas07 Posted 14 hours ago Author Posted 14 hours ago (edited) 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 Edited 13 hours ago by Sebas07 0 Quote
Igor Posted 12 hours ago Posted 12 hours ago 2 hours ago, Sebas07 said: did a new install and 1234 just got me a "access denied" on the first attempt directly after boot Trouble with SSH client or failed SD card could explain this. We didn't change anything in this regard. SSH settings are Debian / Ubuntu defaults. We are not altering this. I tested latest image on XU4 and - it worked. 0 Quote
eselarm Posted 1 hour ago Posted 1 hour ago 20 hours ago, Sebas07 said: 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. If I understand you correctly: root via ssh is not allowed by default I usually setup (new) SBC's in a different way, but last time testing 2 of my boards with 26.2 minimal/IoT fresh image was via serial console, have not used ssh and certainly not putty. If no (serial) console, you might also have sme networking firewall issues somewhere in Windows or so, although would be vary rare. Have you setup a normal user first via (serial) console first? 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.