Viewing profile — staticassertion

Docker is a lot more than just an unprivileged user. In particular, it comes with a seccomp filter. A lot of LPEs are blocked by that filter. Docker is actually a quite decent secu…

The solution is to do exactly what you suggest - separate access. In CI this is a matter of having your "build/test" jobs happen separately from your "deploy/publish" jobs. The tri…

No. NPM's not particularly bad at all tbh.

Most of them definitely let you do that.

That seems like the opposite. Why would someone with high market value stay in one place? 2 years is basically optimal - you vest 50%, maybe collect a promotion, do some good work …

> The harder question is what the architecture around the vulnerability should look like. The principle is to make exploitation harder for an attacker even when a bug exists, so th…

I was rejecting your definition of the hard problem as it contains an assertion that a physicalist wouldn't accept. Yes, reduction would be one very viable strategy. It doesn't req…

> The hard problem identifies the in principle difficulty in explaining phenomenal consciousness, something not definable in terms of structure and function Great, I'm a physicalis…

That's like saying that "water" is a philosophical invention and so if you accept that water is a thing then you've put it into a special category. You can derive consciousness as …

That's true and probably a kinda critical distinction here. Facebook is sort of making the bet that they can not only treat the world like shit but their direct employees too.

You could have said this every year for so many years about so many companies. If people will work for Palantir, they'll work for Facebook. Facebook could be a lot worse and I thin…

> The no-AI policy of the Zig compiler project is for the compiler, other projects can do whatever they want. Well, presumably they want to contribute to the compiler. I know that …

Yes. The policy is pretty clear on what the rules are for LLM generated code. You need a reviewer to agree to review LLM generated code, you need to read the code yourself, etc.

I think that the only significant caveat here is the need for reviewers to opt in, otherwise it's effectively "you can do it if you are open about it and are responsible for the ou…

I guess that's the problem with the term. It should likely be left entirely out of a document like this since it's just confusing.

I'm not making a claim about this bug, I'm saying that oracles and leaks are common and that nginx seems like a good target for them.

What are you even talking about lol the policy doesn't imply that at all. That's in the "allowed with caveats" section. It's just saying to not open bug reports without first readi…

Information leaks are not uncommon at all. nginx seems like a good target for them as well (fork + exec == no re-randomize, so you have the ability to reexec your exploit a lot of …

> even when the rust-lang/rust repository itself largely forbids vibe coding. This policy does not seem to forbid vibe coding?

They're just giving examples of what you can do and explicitly saying so. Saying "you couldn't stop me" is completely missing the point. This is not very different from the Linux k…

This policy is straightforward and shouldn't be particularly controversial (I'm sure it will be bikeshedded to death though). It basically bans the obvious stuff ("don't just drop …

You should sandbox where you run the code. The thing is, it's very hard for me to know how to sandbox an install script, but it's actually quite easy (and my responsibility as the …

I assume that increasing the taxes would just lead to higher rents, right?