Live data from Hacker News

Viewing profile — IainIreland

IainIreland

HN member
Joined
Fri, Aug 30, 2019, 4:49 PM UTC
HN karma
873
Public activity
84 items

About IainIreland

No profile information was provided.

Recent public activity

  1. comment
    Comment #48066518

    We have a bounty program. If you can find security bugs in Firefox, please let us pay you for them. You don't need to provide a fix; a testcase that crashes in an interesting way i…

  2. comment
    Comment #48064679

    I never got direct access to Mythos, so all I know is what I've seen from the quality of the bugs being produced. I also haven't been involved at the prompting end. So the best ans…

  3. comment
    Comment #48064308

    Yeah, the test with the patch also adds comments. The human reviewer had extra context available. I did get Opus to do an audit for similar problems elsewhere, to supplement the in…

  4. comment
    Comment #48056874

    If I had to guess, I'd say that AI is better at finding TOCTOU bugs than fuzzing because it starts by looking at the code and trying to find problems with it, which naturally leads…

  5. comment
    Comment #48056690

    The same is also true of a good security researcher, and has been for a long time. The question is mostly whether it takes long enough to come up with a testcase that we've managed…

  6. comment
    Comment #48056320

    I work on SpiderMonkey, so I mostly looked at the JS bugs. It was a smorgasbord of various things. Broadly speaking I'd say the most impressive bugs were TOCTOU issues, where we ch…

  7. comment
    Comment #48056230

    Yeah, fuzzing, sanitizers, and bug bounties were our main pre-AI tools for finding bugs.

  8. comment
    Comment #48056218

    There doesn't have to be a huge qualitative discontinuity between Opus and Mythos. It's just that Mythos has reached a threshold where it's finally smart enough that putting it in …

  9. comment
    Comment #48056110

    I work at Mozilla; I fixed a bunch of these bugs. In general, I would say that our use of "vulnerability" lines up with what jerrythegerbil calls "potential vulnerability". (In cas…

  10. comment
    Comment #47770652

    This is really cool. Thanks for the write-up, Chris! I kept waiting for "sea of nodes with CFG" to be shortened to SeaFG, and it never happened. I guess maybe it's ambiguous out lo…

  11. comment
    Comment #45594345

    One clear use case for GC in Rust is for implementing other languages (eg writing a JS engine). When people ask why SpiderMonkey hasn't been rewritten in Rust, one of the main tech…

  12. comment
    Comment #45582360

    Cranelift does not use copy-and-patch. Consider, for example, this file, which implements part of the instruction generation logic for x64: https://github.com/bytecodealliance/wasm…

  13. comment
    Comment #45379467

    Yeah, SM will compile functions with try/catch/finally, but we don't support unwinding directly into optimized code, so the catch block itself will not be optimized.

  14. comment
    Comment #45379227

    I don't know how JSC handles it, but in SM `eval` has significant negative effects on surrounding code. (We also decline to optimize functions containing `with` statements, but tha…

  15. comment
    Comment #44879797

    This isn't about languages; it's about hardware. Should hardware be "higher-level" to support higher level languages? The author says no (and I am inclined to agree with him).

  16. comment
    Comment #44063970

    This is really impressive analysis.

  17. comment
    Comment #44033574

    This doesn't read as AI-generated to me at all. The prose isn't polished enough to be AI. AI generation is unlikely to produce missing spaces like "...which are not readable to hum…

  18. comment
    Comment #43345852

    Copy and paste all four lines at once.

  19. comment
    Comment #43250915

    Taking a quick look at the JSC code, the main difference is that CacheIR is more pervasive and load-bearing. Even monomorphic cases go through CacheIR. The main justification for C…

  20. comment
    Comment #43248439

    asm.js solves this in the specific case where somebody has compiled their C/C++ code to target asm.js. It doesn't solve it for arbitrary JS code. asm.js is more like a weird fronte…

  21. comment
    Comment #43248405

    The main thing we're doing differently in SM is that all of our ICs are generated using a simple linear IR (CacheIR), instead of generating machine code directly. For example, a si…

  22. comment
    Comment #43248140

    We talk about this a bit in our CacheIR paper. Search for "IonBuilder". https://www.mgaudet.ca/s/mplr23main-preprint.pdf

  23. comment
    Comment #41115053

    I believe the technical term for the property that existing JS engines lack here is "safe for space". The V8 bug ( https://issues.chromium.org/issues/41070945 ) has already been li…

  24. comment
    Comment #40870625

    I can't speak for any other engines, but in SpiderMonkey a BigInt is a GC-managed object with a one-word header containing the sign bit, the length, and some GC bookkeeping bits, a…

  25. comment
    Comment #40754247

    This seems unlikely, given that the moai were mostly carved from tuff from a specific crater ( https://en.wikipedia.org/wiki/Rano_Raraku ), whereas the stone gardens are made of "f…