@scanlime Yeah.
Here's how @FTDIChip's new driver is intentionally and maliciously bricking clones.pic.twitter.com/87P12Mjco3
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@scanlime I use it as a crutch for x86, since I hate reading x86 asm (especially 32-bit). I must say it makes things much faster though.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This Tweet is unavailable.
-
@puellavulnerata@0xdeadbabe This is decompiled code. The redundancies are artifacts of the compiler and decompiler, most likely.
End of conversation
-
-
-
@munin@puellavulnerata Of course. It's not really "bricking", it's just setting the device ID to a value that the driver won't recognize.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@munin@marcan42@puellavulnerata The specific code won't, but the comments describe how to modify it so it does. Don't get any ideas!Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@munin@natashenka@puellavulnerata There's nothing new about being able to "brick" FTDI devices. You can do it with FTDI's own tools too.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@munin@marcan42@puellavulnerata Sadly, this is the case for a lot of chips. -
@munin@marcan42@puellavulnerata Won't tell you how many ATMEGAs I've accidentally put in "never works again" mode - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.