i'm not even saying "ugh security is hard" i'm saying the attack surface for ssh has been understood for Quite Awhile and we should have decent defaults to make it SAFE to use. Which means:
1. Deny root login
2. Deny password authentication
3. Require public-key authentication
4. Close off any deprecated key exchange methods
5. Auto-ban brute force attempts
That's like. A minimum best effort. Really.
I'm taking an algorithms course, where the mandatory exercises are given in the form of pdf.
The course requires that we submit these exact PDFs, filled out (multiple choice boxes, drawn diagrams, text fields etc).
But it's literally just a pdf with boxes and lines drawn.
It's a god damn algorithms course on an engineering uni.
Literally no one is printing, writing on, and then scanning the files in again.
Also literally no one enjoys editing pdfs directly.
LO-Draw has already messed up fonts and margins.
This morning I got up a little while before I actually had to.
Had breakfast, coffee. Messed around with #godot for shits and giggles, listened to Busdriver.
__Quality of Life__
@ashfurrow So I set the SSID for the wifi on it to "Wu Tang LAN" and five brown faced emojis and it got caught in a boot loop until it eventually factory reset itself
I like computers.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!
We adhere to an adapted version of the TootCat Code of Conduct and follow the Toot Café list of blocked instances. Ash is the admin and is supported by Fuzzface, Brian!, and Daniel Glus as moderators.
Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!