

Something like Ansible won’t help you the first time around, but it’ll make the next times easier.
Something like Ansible won’t help you the first time around, but it’ll make the next times easier.
There’s plenty of useful software in cars: collision avoidance systems, automatic braking systems, pedestrian detection systems, etc. Personally I love android auto / carplay for my audio books for my commute.
I also got very relevant results for that query.
You’re agreeing with something I didn’t state. I’m not defending the idea of introducing bugs through bad code and then blaming others. I think the way Linus responded to that was the issue.
I don’t think I am missing the forest. There’s not an issue with the idea of correcting a developer, but there is an issue in the way the correction was carried out. Just because something behaves “better” after punishment doesn’t mean the punishment was good. Ends justifying means and all.
“An oldie but a goodie”… What?! This shouldn’t be celebrated. What an absolutely unacceptable way to behave. Shame on anyone encouraging this.
Gosh I get unreasonably frustrated when someone says yeah but that’s just security through obscurity. Like yeah, we all know what nmap is, a persistent threat will just look at all 65535 and figure out where ssh is listening… But if you change your threat model and talk about bots? Logs are much cleaner and moving ports gets rid of a lot of traffic. Obviously so does enabling keys only.
Also does anyone still port knock these days?