ubuntu managed to disable root login, no matter what is set in /etc/ssh/sshd_config so all ssh-copy-id root@123.123.123.123 fails the only possible way to login straight as root (only on test systems!) is to 1. manually create mkdir /root/.ssh/ touch /root/.ssh/authorized_keys […]
scroll down to: “how to access user-dev-admin’s home network boxes from anywhere via reverse-ssh-tunnel! :D” ssh tunnel remote deviceD’s port access a device’s port that is only available via a specific machine 😀 or in other words: ssh-tunnel port of […]
GNU Linux howto ssh sshd config hardening security guide per default Debian (unfortunately) does not log ssh logins (why? afraid of harddisk overflows?) every user and admin wants to see “who and what is going on” the system usefull also […]
the idea is: ssh is running on 22 what if user can connect localport 2222<->22 and user can then connect to localport:2222 and it will be forwarded to localport:22? and YES IT IS POSSIBLE 🙂 which the massively complex socat: […]
imho git is a bitch it’s not intuitive it’s not easy but at least pray it’s a well thought out system (it works for Linus does not mean it works for all) https://dwaves.de/2016/10/01/githhub-com-cheat-sheet/ home of git’s git repo: https://git-scm.com/ # […]
situation: one is userA but wants to ssh login to server with ipv4: 123.123.123.123 via userB (dedicated user for that server/task). so what one does is: make sure one can login as userB than as userA: userA: ssh -v -i […]
0. generate keys on client ssh-keygen -t ed25519 -C “comment for what this keypair is for” when asked for passphrase, do not enter anything… cat .ssh/id_ed25519.pub # copy this line ssh-ed25519 ALOTOFRANDOMNUMBERSANDLETTERSMopLe comment # ssh into qnap ssh -v admin@192.168.0.123 […]