the debian cve tracker also links to that page, but they have written 7.0-rc7 besides it.

https://security-tracker.debian.org/tracker/CVE-2026-31431

the openwall link has some comments that talk about the delayed patches, Greg KH also commented.

and the patch to the kernel was commited on 1th of April.

are you sure? what I have seen in git patch dates is 11th for the unreleased 7.0, and yesterday for the LTS versions

tbh they could have boasted even less bytes by just having everything in a zlib.decompress()

I regularly see a surprising amount of lemmy neighbours by their names, but not by their profile pictures, as voyager does not support showing them

I think they mentioned issues and pull requests

last year when Serinus changed the moderation policy that the “narrative” that trans people are not real or are mentally ill or whatever to not be considered hate speech and thus not to be removed automatically, following the similar change at Facebook.

wow, that’s wild. they do have quite a few highly questionable decisions, to put it gently. maybe we should treat them like we do .ml, and encourage people to move to other instances, while generally not participating in their communities

this defense edit does not make sense. no, volunteer foss engineers don’t need to stay clear of popular projects. if the allegations in the replies are true, I’m genuinely sorry for that, but that’s not a risk of being a foss developer, that is a risk of discussing on the internet.

if people are harassing you, you should report them to the admins.

this shit stirrer ex-googler really does not understand the signals people are giving… apparently the community response is “hilarious”, the moderators removing their toots at both instances are “overzealous” for acting upon multiple reports and giving a proper hilarious removal reason.

“everyone is dumb but me!” lol… (not a quote)

this person is really butthurt that people are telling them they have acted very irresponsibly.

really this is the better version??

for that matter they can to an extent. they could be probing ports on localhost and your network. only HTTP protocol though, but through timings they could probably differentiate between open, closed and filtered ports

the browser in voyager is probably your default browser over customtabs

and because of at the very least leaking, even verifying identity is not sufficient to verify humanity

It seems you don’t understand the idea, which wouldn’t be that people would be forced to disclose their identity on social media. Instead, social media would be required to check that users are who they say they are.

that makes no sense whatsoever. you are saying your name is “Hapankaali”. do you have any documents proving that you are actually “Hapankaali”? if you don’t, how are you planning to prove you are who you claim to be?

no, into the front. Otherwise it would still be usable while charging

no they didn’t, yes it could have happened:

1. GCC: exists, not too good messages
2. rust gets made
3. rust gets popular
4. gcc error messages get improved by good example of rust

gcc is not a dead project. it is continuously maintained. its improvements can be influenced by other projects like rust

they didn’t say otherwise

preferring Rust over Rust? what do you mean?

do you think loosely typed python is easy to read and maintain?

an llm slopbot generates messages that are leagues more coherent and easier to understand

or didn’t have a defense against a 0 day.

firewalls are not for defending against 0 days. it is about access control, and reducing, sometimes even minimizing access to potentially vulnerable services. firewalls are not an infallible security tool, but there is no such thing either. the reason to use it is to restrict access such that fewer attackers can take advantage of a potential vulnerability.

there are intrusion detection/prevention systems that could do more, but it’s unlikely they will protect against 0 days, because 0 days are undiscovered and unknown issues.

So the vlan doesn’t do anything either way.

it does. its useful to force traffic through a firewall. its for limiting what has access to what. if you wouldn’t use vlans, hosts on the network would not care about your firewall because they can just go straight to the destination.

I’m not sure I understand your argument, but I think what you say is, firewalls are not infallible so they are useless

Then I was not sure what you meant by this:

I don’t actually know if this is the right way to calculate it, but if for each disk you count the time separately, and add it together for a combined MTBF, then that is 20 out of the 136 MTBF years.

5 years of drive runtime for one drive. 20 “years” for 4 drives, 40 “years” for 8 drives. I say “years” because the way I mean it is like this: running 4 drives for 10 minutes is 40 minutes of combined drive runtime. running 4 drives for 5 years is 20 years of drive runtime. I think calculating it like this can be compared to MTBF. but again, I’m not totally confident that it really works this way.

All in all, I am at this point only trying to track down and relay what I’m seeing about SAS vs SATA.

I think it might be because SATA drives you normally run across, especially in laptops, are not the enterprise kind, but consumer drives built from cheaper components and simpler designs. and those are lower quality. while SAS drives are always enterprise grade.

but still, in my experience SATA drives can have a long life too. but it may be more unpredictable than enterprise SATA/SAS drives

HP says that SAS is more reliable

could be controller chips and cable quality. but also, SFF-8644 type SAS connector can be used to attach a drive to multiple HBA cards as I heard, maybe even multiple machines, for redundancy