Show newer

@oldladyplays Yup. And for me it's still in the spirit of April Fool's because it causes confusion. (Also, hail Eris.)

@oldladyplays

The way I decided to celebrate April Fool's is to tell people a puzzle that causes confusion (because two contradictory things seem to be very obviously true), such that they learn something nontrivial by resolving that confusion. An extremely nice property of that is that it isn't spoiled by first asking them whether they want to partake.

@rq is the source of your confidence empirical or theoretical?

@tqbf what is exactly the chief engineer theory?

@jannem @ChasMusic @carol

Trusting trust only applies if we're taking about something that's a dependency of the compiler (or rather of the toolchain). Otherwise this is just the tedious problem of whether the build process is deterministic (e.g. does it include current time somewhere in the output?).

@aeva

Also, its activation conditions were pretty strict (both at build time as well as at runtime), so there's a good chance it wouldn't enable itself there even if the malicious sources were used.

@aeva it was only (fully) present in _source tarballs_ from maintainer (but not in the repo), so that depends on where guix was getting its sources from.

@erl you mean a steeple as in the tower that is often placed on top of a church and might sometimes contain a bell?

@niconiconi do you use something other than skin oil for that?

@erl what's a _catholicism grade_ steeple?

@q3k

Re the supposed killswitch: I don't get the point of a killswitch. Where would malware authors use it?

@Conan_Kudo @jwf I'm somewhat concerned that the site ignores the hypothesis that the attacker compromised Lasse's dev environment (I think it does by stating free of caveats that tarballs signed by Lasse were created by Lasse).

@yossarian

Sure, it's not a general solution to the "malicious committer" problem, but it _is_ a solution to _this_ attack. (Obviously, if we were doing that, the attacker would choose a different attack, though potentially risking a larger chance of discovery.)

@luis_in_brief @cfiesler in this case this wasn't even adversarial testing, just testing on the typical questions that might be expected

@yossarian

What about using sources from version control instead of from released tarballs?

@delroth

It sounds like it might make sense to deny access to testdata until the build is don (i.e.in nix terms, until the normal output is fully written out), because it's easiest to hide random cruft there.

Is this something that might be semi practical to do in nixos?

@b0rk use custom work trees for any scripts that have to commit changes they make to avoid having to deal with dirty work tree and impact of untracked files on the script's behavior

@kravietz

If you already had to do countersinked holes or chamfers on all edges, is I'd appreciate knowing how you did they. (These two are examples of things that I find tedious in solvespace and would love to have a better approach to.)

@b0rk so the only way to get it back is to find the hash in terminal scroll back. Sigh...

@b0rk oh. Then I was mistaken and you can lose the thing being popped :( (I assume it doesn't get added to the global reflog?)

Show older
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.