On Thu, Oct 23, 2014 at 10:34:41PM -0700, Bob Blick wrote:
> Looks like the function call that bricks the clones is named
> "BrickCloneDevices", see the screencap attached to this message on
> eevblog:
> http://www.eevblog.com/forum/reviews/ftdi-driver-kills-fake-ftdi-ft232/ms=
g535300/#msg535300

Yes, same image on twitter, but the poster says there on eevblog
"Function/variable naming and comments mine", and not FTDI's.

> Also, arstechnica has updated their article, Microsoft has told them the
> driver has been pulled from Windows Update:
> http://arstechnica.com/information-technology/2014/10/windows-update-driv=
ers-bricking-usb-serial-chips-beloved-of-hardware-hackers/

Says there FTDI acted, which would seem to be an admission of
responsibility.

"Yesterday FTDI removed two driver versions from Windows Update. Our
engineering team is engaging with FTDI to prevent these problems with
their future driver updates via Windows Update." -- arstechnica.com

> I'd like to find an easy non-destructive test to check if any of the
> devices I own have fake chips. I suppose someone will put one together
> in the near future.

Yes, from the disassembled code and the Linux kernel patch, it doesn't
look difficult at all.

--=20
James Cameron
http://quozl.linux.org.au/
--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.