From: Johan Hovold <johan@kernel.org>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: Greg KH <gregkh@linuxfoundation.org>,
russ.dill@gmail.com, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: serial: Perform verification for FTDI FT232R devices
Date: Thu, 23 Oct 2014 13:19:27 +0200 [thread overview]
Message-ID: <20141023111927.GD6641@localhost> (raw)
In-Reply-To: <20141023121815.1d8ef21d@alan.etchedpixels.co.uk>
On Thu, Oct 23, 2014 at 12:18:15PM +0100, One Thousand Gnomes wrote:
> > > drivers/usb/serial/ftdi_sio.c | 111 +++++++++++++++++++++++++++++++++++++++++-
> > > drivers/usb/serial/ftdi_sio.h | 41 ++++++++++++++++
> > > 2 files changed, 151 insertions(+), 1 deletion(-)
> >
> > Funny patch, you should have saved it for April 1, otherwise people
> > might have actually taken this seriously :)
> >
> > Patches as performance art, now I've seen everything...
>
> Chuckle. Sillyness aside a pure detection version of that patch might be
> useful so it can warn users "Running Windows may damage your adapter" 8)
>
> Is the 0x0000, 0x0401 they end up with consistent - can we add that to the
> default table so end users can at least make use of devices that have
> been attacked by malware ?
Way ahead of you. ;)
http://marc.info/?l=linux-usb&m=141405129201389&w=2
Johan
next prev parent reply other threads:[~2014-10-23 11:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 8:52 [PATCH] usb: serial: Perform verification for FTDI FT232R devices russ.dill
2014-10-23 9:40 ` Greg KH
2014-10-23 9:53 ` Frans Klaver
2014-10-23 11:18 ` One Thousand Gnomes
2014-10-23 11:19 ` Johan Hovold [this message]
2014-10-23 12:55 ` Mark Brown
2014-10-27 10:58 ` Oliver Neukum
2014-10-27 11:09 ` Oliver Neukum
-- strict thread matches above, loose matches on Subject: below --
2014-10-23 12:44 Hector Martin
2014-10-23 14:14 ` Russ Dill
2014-10-23 17:05 ` Hector Martin
2014-10-24 6:22 ` Perry Hung
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141023111927.GD6641@localhost \
--to=johan@kernel.org \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=russ.dill@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.