We know to Godel that some problems are independent, i.e. it can't be resolved. It's likely that some famous problems are independent, and thus infinitely difficult.
It is perhaps the hardest problem that has been resolved
No it's not. If Claude just solved the Riemann Hypothesis (if that is later proven to be the case), the only cringeworthy thing is your response to his completely understandable description of the events.
It's not beautiful, it's cringy. Good prose does transmit a feeling, but this isn't good prose, and the feeling it does impart is one of excessive, saccharine indulgence. So apart from the writing, the feeling it transmits is also cringy.
Beauty, and cringe is subjective. I am not sure why you are trying to argue in absolutes here. For me, his prose transmits a feeling of beauty, awe, curiosity, for you it reads as cringe. That's fine.
Even if LLMs were never invented, the Rust proponents were obviously completely right from the start. It was a silly state of affairs that, for decades, (performant) software was not memory-safe by default. The price was always going to one day be paid on that.
It's patched so anyone can upgrade to the latest nginx to fix it, thankfully. I agree that just shutting off HTTP/2 is probably non-ideal for a lot of web services.
Neither Ubuntu nor Debian have released patches yet, so if you're using one of these mainstream distributions and install nginx through the distro's package manager, you can't easily "upgrade to the latest nginx" yet. You can however disable HTTP/2 for now.
Both the Debian and the Red Hat packaging systems are awfully convenient ways to build software from source. It has to be, that's package maintainers do daily. They will install all dependencies, apply the distribution specific patches, build, and package in one operation.
Should your distributor fall of the face of the Earth and you still need to patch software, it is often the fastest way to take the source package, put the security patch in the patch directory, and run.
There is more it, such as versioning it between the last release but below the official upgrade so it's convenient when the offical one comes along, and preparing keys if you require signatures, but that's basically it.
Not quite. The kernel bug is only the worker-to-root step. Code execution as the nginx worker through the two HTTP/2 CVEs needs nothing but HTTP/2 enabled. Three of the five CVEs don't need HTTP/2 at all: one is HTTP/3 with an upstream, one is resolver + variable proxy_pass + subrequests, and one is the mail proxy with auth_http.
Luckily we could not see your face during writing this, as I’m pretty sure no serious person in the industry can say this with a straight face… Maybe Theo de Raadt, but there it is a running joke I guess.
Not saying that thie image is affected (I don't know), but small footprint does not guarantee security either. It can hit systems of any complexity these days.
As a Redhat container developer (IIRC) put it a long time ago: Containers do not contain.
Especially with docker everything running as host root opens new problems. Rootless containers as podman are more complex, so more code again. And user namespaces had their own vulnerabilities.
That was in 2014/15 in regards to docker, I think rootless podman with enforced capability reduction and tuned apparmor or selinux is a tad different now.
That is a very well written page. I am pleasantly surprised that they provide detailed instructions to verify the package signature before installation.
FWIW, for nodes that don't have packages, I compiled from source under /opt and deploy scripts check equal or higher version so it will auto switch back when the new packages are installed. Seemed less risky than disabling http 2.
The distributions can customize packages with sensible defaults. Debian usually does, and is incredibly convenient. They usually disable features most people don't use, and allow you to easily switch them on if you choose.
It was patched but the docker containers were a few hours behind, I nearly had to build from source on a few servers, until I noticed they were pushing all the tags as I was patching a few hours after the release was cut
I slightly lean towards it not being an attack but, yes, we should all remain agnostic.
One reason is that if a company is under attack, 1) usually, you can tell you're under attack, and 2) immediately broadcasting "the outage is due to an attack" gives you a bit more PR cover than "umm we fucked something up badly". Companies are generally incentivized to reveal when an outage is due to something they did not directly cause.
I am thankful there are at least some politicians who recognize there is a serious possibility AI may get really, really powerful really soon and really fast.
Either people simply do not think AI will ever get that good, let alone get super good very soon, or they think it but are engaging in some sort of magical thinking about the potential consequences.
I can get the former; it is very uncertain how rapidly capabilities might improve. But if you hypothetically take for granted the potential timelines (which one can be totally justified in not doing!), then the rationalists are just obviously completely correct.
The rationalists really worried about this stuff do in fact think Anthropic is deeply evil and is close to causing horrible catastrophes. You might not be aware of the schisms that have been created as a result of this. Of course they want them shut down or halted.
The more moderate rationalists who are less of doomers basically have similar thoughts on AI as the median Anthropic employee and exec. They believe the upsides of AI are so great, and the grave risks manageable and preventable enough, that AI is worth trying to create.
(I've been a member of the rationalist community since around 2014. Meaning, I am someone who found the SSC blog back then and who comments in their comment section; you don't need to live in California to be a rationalist. Being a rationalist basically means "do you read Eliezer Yudkowsky and Scott Alexander and Kelsey Piper and consider them to be more correct than most other people are". No sexual atypicalities required.)
This is the exact kind of article I find deeply self-important and pretentiously delusional, ironically enough.
Sure, the biology point is fair. The rest is very silly. It moving on to say Bill Gates is therefore wrong to fear the pace of AI improvement is extremely silly.
Freezing/bouncing also lets you have more determinism.
Plugins with (often intentional) indeterminism in them, variations in OS and CPU architecture, variations in how fast their CPU is (a billion plugins on a track may run smoothly for one person and destroy someone else's machine), variations in sample rate, etc. can subtly or substantially affect how something sounds.
And in general it just makes things way easier to share even ignoring the issues of getting people to install the same plugin at the same version and the IP issues.
reply