A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!
Had a similar issue with tlp recently. I just happened to notice the laptop battery was at 100%, and said it was charging. It double and triple checked the config file, but the tlp-stat -b still showed 90%-100%.
Turns out tlp, at some point, started ignoring /etc/tlp.conf, and was pointing to /etc/default/tlp
/etc/ssh/ssh.d/
You mean /etc/ssh/sshd_config.d?
Fixed it. Thanks
You for got the d!
sshd_config
picard_facepalm.png. can you tell I just Tab through terminal?
I could even go further into saying: always test every change you make, do not assume the change has been made because you updated a file.
Good advice. One should always test, for correctness, not just infer.
Show your effective sshd server config: sudo sshd -T
This is good advice in general. Think of it like penetration testing. You really should verify what you can actually access remotely on a device and not assume you have any level of protection until you’ve tried it.
Log files can also contain signs of attack like password guessing. You should review these on a regular basis.
OpenSSH right? What version?
No issues with Dropbear