From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Linux USB security holes.
Date: Wed, 8 Nov 2017 15:40:02 +0000 (UTC) [thread overview]
Message-ID: <otv8gi$jhi$1@blaine.gmane.org> (raw)
In-Reply-To: CAAD4mYjqpT8CLPSfsvHOOdaRSbacW6aJQc-4Wnde6iV1v45Y4w@mail.gmail.com
On 2017-11-08, R0b0t1 <r030t1@gmail.com> wrote:
> On Tue, Nov 7, 2017 at 11:08 PM, Dale <rdalek1967@gmail.com> wrote:
>> Howdy,
>>
>> I ran up on this link. Is there any truth to it and should any of us
>> Gentooers be worried about it?
>>
>> http://www.theregister.co.uk/2017/11/07/linux_usb_security_bugs/
>>
>> Isn't Linux supposed to be more secure than this??
>>
>
> In theory. There was no comment on the existence of such bugs in the
> Windows driver stack, but they likely exist. However, note:
>
> "The impact is quite limited, all the bugs require physical access to
> trigger," said Konovalov. "Most of them are denial-of-service, except
> for a few that might be potentially exploitable to execute code in the
> kernel."
Expecting a machine to be immune from DoS attacks by somebody who is
allowed to touch the machine is indeed delusion on a pretty grand
scale. Expecting a machine to be immune to other non-DoS attacks when
they can touch the machine is moderately deluded.
--
Grant Edwards grant.b.edwards Yow! Don't hit me!! I'm in
at the Twilight Zone!!!
gmail.com
next prev parent reply other threads:[~2017-11-08 15:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 5:08 [gentoo-user] Linux USB security holes Dale
2017-11-08 5:48 ` Adam Carter
2017-11-08 5:49 ` R0b0t1
2017-11-08 15:40 ` Grant Edwards [this message]
2017-11-08 5:53 ` J. Roeleveld
2017-11-08 19:35 ` [gentoo-user] " Ian Zimmerman
2017-11-09 6:10 ` J. Roeleveld
2017-11-08 6:02 ` [gentoo-user] " Dale
2017-11-08 6:10 ` R0b0t1
2017-11-08 6:48 ` R0b0t1
2017-11-08 7:24 ` Dale
2017-11-09 14:07 ` Taiidan
2017-11-08 15:23 ` Martin DiViaio
2017-11-08 21:02 ` Alan McKinnon
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='otv8gi$jhi$1@blaine.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox