

a bad code
just one?
- ‘a code’ - a password
- ‘code’ (mass noun) - programming instructions, for example


a bad code
just one?


but 12-24hrs of downtime every few years seems like a highly reliable system


I hate OpenWrt and everything not normal GNU/systemd software.
I’m out. I’ve been doing this 33 years, but this rot can’t be helped. There is nothing normal about Systemd.
Good luck, though.


Ah, but container-impaired. That’s too bad.
I changed to the BSD license 20 years ago for new stuff.
In enforcing the GPL on one of my projects and sharing code back to the source, as initially agreed by their boss, 3 Korean guys went to jail when the boss changed his mind, and the charge was corporate espionage.
Fsf declined to pursue it. I certainly could not as a volunteer. I came away from the experience feeling that the GPL is toothless, and I gave up on it.


a custom software
“Software” and other “mass” nouns don’t get an article like that.
You gotta pick a lane.
POPs has a place as a protocol, even today. IMAPs is the norm but the right job needs the right tool.
MAPI is trash.


If we had everything in ansible it would be 5 minutes
Ansible at the day-job takes about 45 min to do a patch. As someone who’s used a fair number of alternatives, maybe consider anything else on the planet?
But, seriously. The response to this particular sploit wasn’t really “config management”-y. It was a simple process that cron generally handled anyway, and network segregation and firewalling allowed us to prioritize easily. My worry is that there are some core architectural decisions you may need to revisit in the post-mortem on this, because there may be some fundamental changes required to get sensible wins in the future.
(If you’re on containers, I weep for your validation challenges; also, get bazel)


Potential Linux security vulnerabilities.


there built in kneejerk
WHERE built in the kneejerk?




The article feels like an LLM helped write it
Nah. It’s got a ‘millennial’ amount of run-on sentences and comma-splice issues; stuff an LLM wouldn’t do.





rebuilding internet facing servers
Because of one vulnerability?
Jebus. Response at one site was a 10-minute thing and then letting cron do the work.
Where the hell is your D-R? I worry you’ve made some very non-optimal decisions in the past and are taking on way too much work now.


Jamie is a cool guy. He’s also super smart. But he’s not infallible, and so I must secure this and only run it from the internal admin network. Because that’s best-practice.


You understand that, with a store-and-forward service, speed doesn’t mean a damned thing, right?
You DO get that … right?
It’s like gauging English spelling based on what’s popular on Youtube.
most of them citing the unix principle as the main argument.
It’s like building codes. You don’t always know you need a smoke detector, but we have 6 in this apartment.
People suggesting the Unix philosophy needs to prove itself have issues incorporating anyone else’s experience into their own. It’s okay, but watch for that oppositional disorder.
I would be surprised if you didn’t have your own boundaries
Of course I do. And when provided good arguments, I redraw my boundaries.
This is the difference between policies and religion: one of them is open to debate.
(My take is simple, but similar: today I accept the “caveat venditor” policy, and I watch it like anything else, like we do)


firmwares
Just ‘firmware’, still. It never gets an S.
No.