From: <Mario.Limonciello@dell.com>
To: <yehezkelshb@gmail.com>
Cc: <mika.westerberg@linux.intel.com>, <pmenzel@molgen.mpg.de>,
<andreas.noever@gmail.com>, <michael.jamet@intel.com>,
<ck@xatom.net>, <linux-kernel@vger.kernel.org>,
<anthony.wong@canonical.com>
Subject: RE: USB devices on Dell TB16 dock stop working after resuming
Date: Wed, 20 Nov 2019 17:41:43 +0000 [thread overview]
Message-ID: <291d19c96463462b911988d47b9a6a0d@AUSX13MPC105.AMER.DELL.COM> (raw)
In-Reply-To: <CA+CmpXubOwsradq=ObUF-h6WBpRF3tDx9TqaUO8TeJDqvdeGPg@mail.gmail.com>
> > But I mean this is generally an unsafe (but convenient) option, it means that you
> > throw out security pre-boot, and all someone needs to do is turn off your
> machine,
> > plug in a malicious device, turn it on and then they have malicious device all the
> way
> > into OS.
>
> Only if the attacker found how to forge the device UUID (and knew what UUIDs
> are allowed), isn't it? Unless you take into account things like
> external GPU box,
> where it's pretty easy to replace the card installed inside it.
Notice, I never said it was easy :)
In order to turn that on something like that "generally" safely you need to have
mitigations like pre boot DMA protection in place.
next prev parent reply other threads:[~2019-11-20 17:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 13:13 USB devices on Dell TB16 dock stop working after resuming Paul Menzel
2019-11-04 14:24 ` Mika Westerberg
2019-11-04 14:44 ` Mika Westerberg
2019-11-04 15:44 ` Mika Westerberg
2019-11-04 15:49 ` Mario.Limonciello
2019-11-04 16:11 ` Paul Menzel
2019-11-04 16:17 ` Mario.Limonciello
2019-11-04 16:22 ` Paul Menzel
2019-11-04 16:21 ` Mika Westerberg
2019-11-19 16:55 ` Paul Menzel
2019-11-19 17:20 ` Paul Menzel
2019-11-20 10:50 ` Mika Westerberg
2019-11-20 14:15 ` Mario.Limonciello
2019-11-20 15:23 ` Mika Westerberg
2019-11-20 17:06 ` Mario.Limonciello
2019-11-20 17:16 ` Yehezkel Bernat
2019-11-20 17:41 ` Mario.Limonciello [this message]
2019-11-20 17:43 ` Mika Westerberg
2019-11-20 17:39 ` Mika Westerberg
2019-11-22 10:50 ` Mika Westerberg
2019-11-22 11:05 ` Paul Menzel
2019-11-22 11:29 ` Mika Westerberg
2019-11-22 11:33 ` Paul Menzel
2019-11-22 11:41 ` Mika Westerberg
2019-11-25 9:20 ` Mathias Nyman
2019-11-26 11:33 ` Paul Menzel
2019-11-26 12:44 ` Mathias Nyman
2019-12-20 14:25 ` Paul Menzel
2019-12-23 9:39 ` Mathias Nyman
2020-01-17 9:56 ` Paul Menzel
2020-01-17 18:33 ` Mario.Limonciello
2020-01-18 9:15 ` Paul Menzel
2020-01-27 22:16 ` Paul Menzel
2020-02-05 13:10 ` Paul Menzel
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=291d19c96463462b911988d47b9a6a0d@AUSX13MPC105.AMER.DELL.COM \
--to=mario.limonciello@dell.com \
--cc=andreas.noever@gmail.com \
--cc=anthony.wong@canonical.com \
--cc=ck@xatom.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=pmenzel@molgen.mpg.de \
--cc=yehezkelshb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).