However, looking at the Pentium Overdrive pinout the extra row of pins doesn’t seem to be at all essential. There is a number of extra power points and some signalling pins to support L1 cache coherency when using write-back. Nothing too much to worry about.
In Canada you can still buy that over the counter. You get id-ed and they keep a record of your purchases, but since it's now generic pills it is now much cheaper than it was before
"Viable" as in "you have no other choice sometimes". This forces you to deal with 3 libraries each with their own quirks, pitfalls and incompatibilities. Sometimes you even deal with dependencies reimplementing some parts in a 4th or 5th library to deal with shortcomings.
I really don't care that much which of them survive, I just want to rely on less of them
My take on that is that it's up to the kernel maintainers to unban them. If they end up the investigation with: "Yeah, that was bad but we won't do anything about it", it's unlikely to get the banning side to move an inch.
This indeed looks like a FUD statement, implying that they can have an infinite amount of potential vulnerabilities. Realistically though, writing parsers that do not yield control of your whole device is not that complex. The people exploiting iOS zero days can certainly do it.
It seems to be a retaliatory measure against this:
> When Cellebrite announced that they added Signal support to their software, all it really meant was that they had added support to Physical Analyzer for the file formats used by Signal.
Your case is valid about potential judiciary impact, but it would require for Signal to monitor cases involving Cellebrite and step forward to help the defense while unprompted to do so. Furthermore, Cellebrite clients seems to include entities that do not care so much about a fair trial.
Uh... sure, if you say so.