tredre3
Neither have I, I think you goofed up on your acronyms? For a driver as embedded as crowdstrike you need to recompile, there's no other way around it. Linux doesn't provide anything stable to target and a shim won't cut it in this case.
> the service ran as root, it UPDATED ITS OWN BINARIES as root!
Would you prefer if Linux allowed local users to replace the kernel and/or its modules without root? What kind of faux-outrage is this?
The NY Post is crass, we all know that. But if that's your best example of their malfeasance, then I guess they aren't that evil after all.
The math is a lot less impressive when you do it with 2^48 or 2^64.
The thing is, asking nicely doesn't always work. Sure, automated tools like docker/incus/wireguard/tailscale will respect it. But admins who don't want to be stuck typing long addresses? Not so much. I've lost count of how often I encounter a network admin that manually set their prefix to some fcXX::, when it's not outright fc00::.
Of course you can (and should) blame this on admins and not on IPv6, but then the same could be said of IPv4 where adding entropy to 10.X.X.0 is the usual recommended way of doing things.
- Rust didn't exist at the time
- Go didn't exist at the time
- nodejs didn't exist at the time
- Java and Python likely used too much resources for a once-in-a-while used GUI
Irrational hatred aside, that's literally what PHP was designed for.
That's it. The comparison is indeed burger delivery vs drive-through/takeout. Cooking is irrelevant in the equation.
The "version 2 of the License, or (at your option) any later version"
language in the GPL copying file is not - and has never been - part of the
actual License itself. It's part of the _explanatory_ text that talks
about how to apply the license to your program, and it says that _if_ you
want to accept any later versions of the GPL, you can state so in your
source code.
The Linux kernel has never stated that in general. Some authors have
chosen to use the suggested FSF boilerplate (including the "any later
version" language), but the kernel in general never has.
In other words: the _default_ license strategy is always just the
particular version of the GPL that accompanies a project. If you want to
license a program under _any_ later version of the GPL, you have to state
so explicitly. Linux never did.
"The Dune books were all about islam, the movies are not; Today I will analyze what was lost in translation and why they did it!" doesn't have the same ring to it than "ISLAM IS BEING ERASED BY HOLLYWOOD!"
The fact that we do proves that ICs are equally to blame, because evidently the majority of them love using AI.
That being said let's keep in mind that the latest wave of moving-away-from-MS-Office is using OnlyOffice this time and I believe it might work. OnlyOffice actually wants to entice MS Office users. And thus it is more compatible, has a much closer/better UX, and despite being a web app it is somehow more responsive than LibreOffice.
But apache + mod_php hasn't been the default setup for a very long time, that's what people are trying to tell you. Given your expertise, you must know that already. So I have to conclude that you're arguing in bad faith because it's the only setup you can break.
Multiplexing is the default in HTTP/2 and 3. So you're still wrong.
Because unless your desktop is dedicated to banking, there's always the chance that one of your other activities will install malware. If you don't use FDE (the majority of people) and you saved your banking password in the browser rather than a password manager (likely a scary amount of people), then theft is also an issue.
Neither of those things are really a problem on a mobile device.
Nobody would move all their money out of the country they live in.
Just because there are juggernauts ("the big five/six") doesn't mean it's an oligopoly. This isn't like telecom where there are only 3 choices (4 in some provinces) and nobody else can enter the game because it costs too much.
But I have spent/wasted enough time online to know that Conservatives do truly believe that the CBC is very biased against them and thus should be defunded (or, alternatively, they often suggest giving the same amount of money to Rebel News).
It's almost always better (in my experience) to use auto increment internally, and assign a random hash (or UUID) to each public-facing record. All your SQL will be faster at the cost of one lookup (trivially cached) to match the requested hash/uuid to PK. Of course this requires discipline across the team and, in that sense, "just always use uuidv4" is easier.
https://www.postgresql.org/docs/current/functions-uuid.html#...
uuid_extract_timestamp ( uuid ) → timestamp with time zone
Extracts a timestamp with time zone from a UUID of version 1 or 7. For other versions, this function returns null. Note that the extracted timestamp is not necessarily exactly equal to the time the UUID was generated; this depends on the implementation that generated the UUID.
uuid_extract_timestamp('019535d9-3df7-79fb-b466- fa907fa17f9e'::uuid) → 2025-02-23 21:46:24.503-05The article specifically says those tests didn't correlate with the result of the scans. Why do you call BS on it?
This could not be further from the truth. Backwards compatibility is a big reason why PHP doesn't have <your favorite missing feature that is totally a dealbreaker and PHP is thus unusable>. Odds are if you look at their RFCs and internals mailing list you'll likely find proposals and even implementations for any BC-causing feature you can think of.
The point of getting the second bank account is to reduce the blast radius if the agent goes haywire, I suppose?
But then you'll have to manually top up that account every now and then, how does it solve your initial problem?
Exactly, most projects have a license of some kind, they aren't "free-for-all-do-whatever."
MIT requires attribution. Forcing enforcement of this cannot be done without copyright law. You can argue that attribution is stupid and nobody deserves credit for their work (which might be increasingly true in a post-LLM world), but you can't speak on behalf of all projects that chose those license and say "it's what they want!"
That kind of action would penalize their users far more than it would hurt the evil corporation that slighted them. Not to mention they'd lose users. People who choose quad9 likely aren't too keen with DNS tempering.
But yeah, take that sony-or-whatever!
Your agent can't help you before the patch is rolled out, so let's not lose sight that the fix to this vulnerability will be:
apt update && apt upgrade
If you didn't know how to keep your server up to date before agents, then perhaps a managed hosting service would be a better fit?
Obviously it's been overprescribed. Old school doctors likely still do prescribe it too easily. And new docs often plainly refuse to prescribe it at all. The solution doesn't have to be black or white. Doctors have the ability to limit the number of pills per month a patient can get, imagine that! It doesn't have to be nothing at all vs as-needed-which-means-the-full-30-pills-every-month-inviting-the-patient-to-start-taking-it-daily. It can be "give 5-10 pills per month".
That way the doctor can monitor the patient needs more closely and effectively prevent both addiction and tolerance from developing (to preempt: no, most people cannot in fact easily source it from the black market, and doctor shopping is no longer a thing for controlled drugs thanks to the opiod crisis).