Funnily enough, this is what a chromebook was made to do. A computer that was only a browser. Unfortunately, the hardware was severely underpowered, and the custom software wasn’t as flexible as a simple Linux desktop is capable of. (Almost no software support outside of Google)
Yes, but I usually add my public key to the authorized_keys file and turn off password authentication once i do login with a password. On top of that, I have a sshpass one line command that takes care of this for me. It’s much easier than trying to manually type a password for the next time. I save it and just run it every time I think about using password login. Next time I need to ssh, I know the password login is not necessary.
sshpass -p ‘PASSWORD’ ssh USER@IP.ADDRESS “echo ‘`cat ~/.ssh/id_rsa.pub`’ > ~/.ssh/authorized_keys && echo ‘Match User !root
PasswordAuthentication no
Match all’ > /etc/ssh/sshd_config’ && exit” && ssh USER@IP.ADDRESS
At the next reboot, your system will now only accept key logins, except for root. I hope the root user password is secure. I don’t require it for root because if a hacker does gain shell access, a password(or priv esc exploit) is all they need to gain root shell. It is also a safety net in case you need to login and lost your private key.
an linux operating system made by the KDE team
I always shy away from newer tech because of lackluster documentation and poor leadership. The latter is rare enough. Without proper documentation, I feel like I have to read the code and make my own notes to put into their documentation platform. Which is not what I want to do when I use it. Contributing is nice, but when doing something a core member would do without credit, it will dissuade me from participating.
Likely prohibitively expensive, will take a long af time to reach wider markets and most likely never pass trials
All my predictions