TIL about the box.leak() method in Rust: https://doc.rust-lang.org/std/boxed/struct.Box.html#method.leak
This leaks the box, but it also gives you a reference that can live longer! E.g. you can leak a Box<u64> and treat it as 'static.
It makes sense, but being able to use a value after leaking is new idea to me.
miniblog.
Related Posts
I'm coming round to the view that services should avoid implementing their own username and password system. It's easy to screw up (cf crypto) such that a DB compromise leaks users' passwords for other sites.
It's also more convenient for users, who don't need a pw manager.
Re-linking the OpenBSD kernel on every boot, to make info leaks harder: https://www.bleepingcomputer.com/news/security/openbsd-will-get-unique-kernels-on-each-reboot-do-you-hear-that-linux-windows/ (innovative and in principle any OS could)
"Since I'd worked for days to find somewhere to insert a single char, I also added a comment" https://neilmitchell.blogspot.com/2013/02/chasing-space-leak-in-shake.html (fixing space leaks)