Sebas07 Posted 23 hours ago Posted 23 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 20 hours ago Posted 20 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 17 hours ago Author Posted 17 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 15 hours ago by Sebas07 0 Quote
Igor Posted 14 hours ago Posted 14 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 3 hours ago Posted 3 hours 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
bedna Posted 1 hour ago Posted 1 hour ago (edited) 2 hours ago, eselarm said: If I understand you correctly: root via ssh is not allowed by default Unless they have changed something very recently, you can login as root via ssh on first-run. I double checked /etc/ssh/sshd_config on an armbian install image I had downloaded, and: # Authentication: #LoginGraceTime 2m PermitRootLogin yes #StrictModes yes #MaxAuthTries 6 #MaxSessions 10 PubkeyAuthentication yes <snip> # To disable tunneled clear text passwords, change to no here! #PasswordAuthentication yes #PermitEmptyPasswords no And inside /etc/shadow (default 1234 passwd): root:$y$j9T$SAPCtO/l2ZIj6A2frqTza/$.Z8dP41gzqRHoIS8PvXFn9fghf9rgkGqAWgXVRW4dg6:20234:0:99999:7::: So that should not be an issue here. (and there are keys inside /etc/ssh that I assume can be used at first login, I have never tried) Sounds more like a faulty sd-card that gets mounted read-only, that can cause stuff like this happening. (as mentioned earlier by Igor) Try with a different sd-card (and use armbian-imager instead of balena) and see if the same happens on another card. Edited 1 hour ago by bedna 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.