@erl what's a _catholicism grade_ steeple?
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).
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
What about using sources from version control instead of from released tarballs?
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
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
Aaah, I didn't realize that sign was important there.
Yet another even worse ISA fanfiction from yours truly
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?
@sophieschmieg and beyond MACs, I suppose?
@koakuma I'm still unused to that model :)
Where does the call instruction store the return address in that model?
I enjoy things around information theory (and data compression), complexity theory (and cryptography), read hard scifi, currently work on weird ML (we'll see how it goes), am somewhat literal minded and have approximate knowledge of random things. I like when statements have truth values, and when things can be described simply (which is not exactly the same as shortly) and yet have interesting properties.
I live in the largest city of Switzerland (and yet have cow and sheep pastures and a swimmable lake within a few hundred meters of my place :)). I speak Polish, English, German, and can understand simple Swiss German and French.
If in doubt, please err on the side of being direct with me. I very much appreciate when people tell me that I'm being inaccurate. I think that satisfying people's curiosity is the most important thing I could be doing (and usually enjoy doing it). I am normally terse in my writing and would appreciate requests to verbosify.
I appreciate it if my grammar or style is corrected (in any of the languages I use here).