Live data from Hacker News

Maybe you shouldn't install new software for a bit

xeiaso.net

431–440 of 497 posts

Re: Maybe you shouldn't install new software for a bit

#431

Am I missing part of the article? This seems like 2 sentences saying "don't install anything cause some Linux LPEs came out." I don't understand why this is on the frontpage of HN.

As the author of it I'm as confused as you are. It's frontpage number 68 for me, next time is ultimate nice.

Re: Maybe you shouldn't install new software for a bit

#432

Earlier quoted context omitted.

FreeBSD is not a distro. It's not even Linux; it's a completely different kernel and operating system that traces back to even before Linux. It's honestly closer to Darwin than it is to Linux; macOS is technically a BSD. (Not FreeBSD though.)

Darwin is its own thing really. There are parts from BSD, there are also parts from Mach and there are also unique parts.

Of course. Linux does not share any heritage with BSD though.

Re: Maybe you shouldn't install new software for a bit

#433
post #191

Earlier quoted context omitted.

I worked for one company where we were super conservative. Every external component was versioned. Nothing was updated without review and usually after it had plenty of soak time. Pretty much everything built from source code (compilers, kernel etc.). Builds [build servers/infra] can't reach the Internet at all and there's process around getting any change in. We reviewed all relevant CVEs as they came out to make a…

I would rather work with a company that updates continuously, while also building security into multiple layers so that weaknesses in one layer can be mitigated by others. For example, at one company I worked for, they created an ACL model for applications that essentially enforced rules like: “Application X in namespace A can communicate with me.” This ACL coordinated multiple technologies working together, includin…

> I would rather work with a company that updates continuously, while also building security into multiple layers so that weaknesses in one layer can be mitigated by others.

Sorry, if you are updating continuously, that there is at least one layer that you failed to build any security into.

Re: Maybe you shouldn't install new software for a bit

#434
post #65

Earlier quoted context omitted.

So, to play Pandora, what if the net effect of uncovering all these unknown attack vectors is it actually empties the holsters of every national intelligence service around the world? Just an idea I have been playing with. Say it basically cleans up everything and everyone looking for exploits has to start from scratch except “scratch” is now a place where any useful piece of software has been fuzz tested, property t…

New software is being generated faster than it can be adequately tested. We are in the same place we’ve always been; except everything is moving much too fast.

I'm somehow reminded of Wile E Coyoto running off a ledge, staying afloat until he realizes there is no more ground under his feet.

Re: Maybe you shouldn't install new software for a bit

#435
This is why I usually try to lean toward software versions with LTS (Long Term Stable) versions - especially if they are more minimalist / run leaner. Theoretically you get all the security patches (if needed - of course you can vet updates still and test) and less bugs and vulnerabilities through less new features.

Reducing attack surface and software complexity will (theoretically) reduce the number of possible exploits regardless of what new tool or process attackers discover.

Re: Maybe you shouldn't install new software for a bit

#436
post #411
post #204

Earlier quoted context omitted.

Thank you for reminding us all that you AI bros are still the most obnoxious people there are.

Indeed, yet another proof, there's the part of HN crowd which is passive aggressive, dismissive, and dishonest in the very scientific possible sense. Won't make my day harder than it is, but is a very weak signal. If I'm to be offended by a single thing in your post that is calling me (names) - is AI Bro. This was undeserved, and cannot be farther from the truth. Not to miss the fact your comment is entirely off topi…

This seems like a very emotional response, which is off-topic for HN. Consider using facts and logic to make calm, rational arguments.

Re: Maybe you shouldn't install new software for a bit

#437

Earlier quoted context omitted.

Darwin is its own thing really. There are parts from BSD, there are also parts from Mach and there are also unique parts.

Of course. Linux does not share any heritage with BSD though.

Except that they are both based on Unix and (generally) made to run on x86 processors. Which is a pretty big similarity

Re: Maybe you shouldn't install new software for a bit

#438

Earlier quoted context omitted.

I've kept hearing about BSD recently, how hard is it to actually switch to? I'm guessing Linux executables don't work on it since it's not Linux, do all your packages have to be made specifically for BSD?

My experiences from dabbling with it a few months ago: In general everything needs to be compiled for FreeBSD, but the ports collection is quite extensive. For example you will find Firefox, wayland, GNOME, KDE, xfce, … even dotnet was on there. Problems arise with properietary stuff like Spotify, Widevine DRM etc. However, FreeBSD has a Linux emulation layer (providing syscalls), dubbed ‘Linuxulator’. I managed to r…

I could be wrong but I think Jails are separate from containers on BSD?

Re: Maybe you shouldn't install new software for a bit

#439

For the newer players who have gotten into continuous integration and containerized builds, consider checking on your systems to be sure you're not pulling 'latest' across a bunch of packages with every build. We set up our base containers with all the external dependencies already in them and then only update those explicitly when we decide it's time. This means we might be a bit behind the bleeding edge, but we're…

Sounds like a good time to setup a test environment that does pull latest!

Re: Maybe you shouldn't install new software for a bit

#440

"Don't update your systems for a while" is exactly what an attacker would say. If you can't trust your update sources, you have bigger problems.

If I'm being really frank, are system updates not more disruptive, destructive and result in more data loss and downtime than all the attacks you'll experience in your lifetime? (unless you're a high value business target ofc, I'm talking for personal machines) In my book, having unattended-upgrades or windows update run amok on your system is functionally worse than a rootkit.

This is why you always have a test environment and good, tested backups that are easy and quick to roll back to. Even if something makes it past test (or there is an install problem with a patch that is otherwise fine) you can just roll back.

For personal machines without those resources you are a bit of a hard place - although many OS and software these days have long term stable versions and the ability to defer auto patches by a week or two

Post reply on HN