Show newer

@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?)

@b0rk huh, I must be mistaken about something because I thought that stash's reflog behaves normally. Thanks, will take a look at it when I'm next at something more computer-like than a phone.

Yet another even worse ISA fanfiction from yours truly 

@koakuma ah, so raising the stack pointer in some sense invalidates the part of the stack that's not legal to access. Thanks, that makes sense.

Yet another even worse ISA fanfiction from yours truly 

@koakuma so what's the additional weakening of the mem model here?

Yet another even worse ISA fanfiction from yours truly 

@koakuma

Aaah, I didn't realize that sign was important there.

Yet another even worse ISA fanfiction from yours truly 

@koakuma

What _would_ allow one to read writes to the same mem loc done at a different ST in this model? I'd expect function arguments to require that.

@sophieschmieg well, if I have a PRF I can make all of cryptography out of it :P

But I do mostly get the concept. Are you intentionally including handshakes of any kind in the fancy part?

@koakuma

Where does the call instruction store the return address in that model?

Show older
Qoto Mastodon

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