The right way to do this is to hire a group of developers and have test volunteers report workflow problems - then FIX them - then iterate. That's the point of choosing an open source solution.
Eventually there would be no problems remaining.
But so many possible scenarios exist that it's impossible to guess what happened here.
PS _NSA_KEY
There are apparently other unpatched vulnerabilities that are known but 'too busy':
It sounds like this fix got done because it was 'accidentally' posted as a public PR.
Yeah, the threat actor would need a foothold on the PXE network, which is a private VLAN (or better) in the competent case.
That's why we worry about APT's and such.
Granted, you'll find people on certain cloud providers who do far too much on a public IP.
Not that SCOTUS (nor any high court in the EU or other countries) has concluded this determination, but so far the general claim is that AI-generated content (images, movies, writing), while it may (or rather, does) contain copyright violations for stealing from others, it itself can't be copyright protected because no human was involved in making the final product. It is automatically public domain.
So that leaves the question - at what point does a vibe-code project be considered public domain and thus not protected by a license?
Straczynski shared his experiences working with Koenig on his FB page. A good read.
What if someone has fifty windows open with fifty tabs each?
Asking for a friend.
Solid effort - good job.
It's a bummer if any of the employees got rug-pulled but many of the best employees will strike out on their own, form new companies with working conditions they value, and likely hasten Skydance's demise.
nah, a RS code can correct a tiny bit of loss but two metadata copies can correct a bad sector or even track if you're lucky.
Different requirement spaces.
The idea this guy has might make embedded devices slightly more long-lasting.
They usually have quantity one of a cheap storage part and a bad block in the wrong place could brick the whole thing.
It would only be useful in the case where maybe the build is 12MB and the chip is 16.
Most vendors won't ever pay extra for this.
I suspect the people who hate it don't have problems it solves.
Maybe a very basic home laptop is fine with SysV today and they don't want to learn anything new.
Personally I've been able to retire thousands of lines of scripts I'd written to handle complex things with many edge cases and ugly devops modules that are no longer needed with more recent releases.
There's just no userland interface to many of the events it can respond to and it's not easy to write a new C++ daemon to handle each need that comes up.
At this point it's largely a functional API to kernel events in the way I use it. That's the DOTADIW perspective for me. I still have services call my scripts where it doesn't handle what I need. It would be crazy to ever expect it to handle everything.
But just because I need to handle complex things at scale sometimes doesn't mean everybody else does. If I want to run debian with X11 and emacs and you want to run Devuan with Wayland and vi, you'll get no argument from me.
Who has time for drama these days?
This discussion on their inclusion in Mozilla is quite revealing:
https://bugzilla.mozilla.org/s...
Elsewhere it's claimed that they used a FIPS HSM to generate their keys.
I did not see who their auditor was.
Did eMudhra lie?
Did the auditor lie?
Are FIPS HSM's backdoored?
Do we have another Dual_EC_DRBG situation on our hands here?
If nobody is lying we could have just seen a huge cyberwar or false flag averted. Essential crypto gear could be totally buggered still.
PS Remember when Mozilla gave CACert absolute hell for years when they were tremendously more competent?
I thought we lured them all onto Facebook then ran for the hills?
"So why don't you make like a tree, and get outta here." -- Biff in "Back to the Future"
