Stranger Strings: An exploitable flaw in SQLite

Re:Stranger Strings: An exploitable flaw in SQLite by ghoward on Tuesday October 25, 2022 @11:24AM (#33331841)

SQLite is used in places that Rust has no compiler for and that no other language has a compiler for.

One severe CVE in about 20 years is no reason to rewrite in another language and remove support for some platforms.

[ Parent | on HN ]

Re:Stranger Strings: An exploitable flaw in SQLite by nicoburns on Tuesday October 25, 2022 @11:48AM (#33332197)

In the long term, I hope C stops being the default language that hardware vendors provide for their hardware.

[ Parent | on HN ]

Re:Stranger Strings: An exploitable flaw in SQLite by ghoward on Tuesday October 25, 2022 @11:50AM (#33332222)

Me too, but I also hope Rust is not that default language.

[ Parent | on HN ]

Re:Stranger Strings: An exploitable flaw in SQLite by threatofrain on Tuesday October 25, 2022 @01:08PM (#33333345)

Just how many machines are we talking about? Does anyone have estimates?

[ Parent | on HN ]

Re:Stranger Strings: An exploitable flaw in SQLite by ghoward on Tuesday October 25, 2022 @01:36PM (#33333705)

Probably every Airbus A350 XWB and a lot of GM, Nissan, and Suzuki cars. Maybe also a few or a lot of General Electric products. [1]

The Library of Congress also recommends it for preservation of digital content, which would be harder if Rust compilers were lost. If all C89 compilers were lost, it would be much more simple to create a new one to compile SQLite than it would be to recreate a Rust compiler.

[1]: https://www.sqlite.org/famous.html

[ Parent | on HN ]

Re:Stranger Strings: An exploitable flaw in SQLite by admax88qqq on Thursday October 27, 2022 @01:48PM (#33361276)

I'm not saying we need to rewrite SQLite and I'm not sure why everyone is assuming I suggested rust.

But people need to consider how much testing SQLite did and still hit memory vulnerabilities when they consider picking up C for a new project.

[ Parent | on HN ]