Memory Safety Bugs in Rust Standard Library

(forge-blog.github.io)

43 points | by pjmlp 2 days ago

6 comments

  • hingler36 8 minutes ago
    I've always felt that parts of the Rust standard library to be weirdly un-rusty. Like indexing a vector panicking instead of returning a Some(T) in case the index is out of bounds. It's easy to avoid if you put the effort in of course, but it did always feel weird that one of the first data structures you learn has this behavior right out of the gate.
  • nektro 31 minutes ago
    > Pattern 2: Trusting user-provided implementations to be correct

    reminds me of the tales from https://oxide.computer/blog/iddqd-unsafe

  • nektro 56 minutes ago
    > Notes from Microsoft Security's Frontier Offensive Research & Generative Exploitation Lab.
  • not_a_bot_4sho 45 minutes ago
    A good use for AI
  • senderista 32 minutes ago
    I sure wish they'd rewrite the Azure Linux VM Agent in Rust. That thing normally burns 10-15% of a core, and also blocks VM restart for tens of minutes, god knows why.
    • loeg 16 minutes ago
      I've seen certain MSFT engineers get a lock ordering warning from taking mutexes in a wrong order and "fix" it by using a spin loop + try lock instead.
  • mesm7903 9 minutes ago
    [flagged]