Op Mon, 19 Feb 2018 21:19:27 +0100 schreef Hess THR
:
I mean.. did it ever happened in the history that a microphone driver
sent its data via the network?
Quite unlikely with open source drivers. And even load-modules can be
checked to see which kernel functions they
On Mon, Feb 19, 2018 at 09:19:27PM +0100, Hess THR wrote:
> I mean.. did it ever happened in the history that a microphone driver sent
> its data via the network?
>
> if these attacks aren't very likely, then I was just loudly thinking..
>
> wouldn't it be great to held some idea day for:
diot ideas, but maybe 1 great, who knows.
> Sent: Monday, February 19, 2018 at 8:58 PM
> From: "Hess THR" <hessnovth...@mail.com>
> To: misc@OpenBSD.org
> Subject: Re: noob question: driver separation?
>
> Hello,
>
> nono, just in theory.. or it doesn't worth it
Hello,
nono, just in theory.. or it doesn't worth it?
> Sent: Monday, February 19, 2018 at 11:05 AM
> From: "Boudewijn Dijkstra" <mailinglists.boudew...@indes.com>
> To: misc@openbsd.org
> Subject: Re: noob question: driver separation?
>
> Op Fri, 16 Feb 20
Op Fri, 16 Feb 2018 21:51:12 +0100 schreef Hess THR
:
Hello,
are there any (at least on plan or theoretical level) that drivers will
be/are/would be separated? ex.:
- touchpad drivers shouldn't have to do anything with network access
- wireless drivers shouldn't be
Hello,
are there any (at least on plan or theoretical level) that drivers will
be/are/would be separated? ex.:
- touchpad drivers shouldn't have to do anything with network access
- wireless drivers shouldn't be able to touch anything from ex.: /home
- graphics/wireless/sound/disk/etc.
6 matches
Mail list logo