News for hackers. Stuff that matters.
Re:Memory Safe Languages in Android 13 by ghostwriter on Thursday December 01, 2022 @05:21PM (#33823796)
> We have no ssl library written in a memory-safe, functional language that has been proven correct that has dominated the space. Heartbleed wasn't yesterday.

Heartbleed didn't affect https://hackage.haskell.org/package/tls even though it isn't formally verified.

Re:Memory Safe Languages in Android 13 by harry8 on Thursday December 01, 2022 @05:27PM (#33823878)
Does anybody at all use that library in production at scale, ever? Genuine question. Maybe they do?

Why hasn't this really good result meant _everybody_ now uses that library by default and has to justify using something else?

There is something here not being discussed, what is it?

Re:Memory Safe Languages in Android 13 by ghostwriter on Thursday December 01, 2022 @05:46PM (#33824070)
There's a hint it was used at Dell in some capacity 6 years ago, judging by this comment https://www.reddit.com/r/haskell/comments/5gyrdv/what_is_war... The thread discusses "warp-tls" which is a webserver extension that uses that "tls" package as a dependency for TLS support.
Re:Memory Safe Languages in Android 13 by harry8 on Thursday December 01, 2022 @07:13PM (#33825007)
Ok but this is surely not compelling evidence of literally anything. Perhaps, in fact, the opposite. This is what we have for evidence and nothing more then WHY???

There is something here, at least one thing, that seems to be dominating outcomes, and is not being discussed.

Nobody has even a half-suggestion of what it might be and that is not making it (or them) go away as problems that are not being solved.

Re:Memory Safe Languages in Android 13 by roca on Friday December 02, 2022 @01:49AM (#33827652)
rustls isn't formally verified but no critical CVEs have been found in it yet. The only CVE is one DoS.

And I don't know about "used at scale" but we use it in production for Pernosco.