[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5j+_AwCDAqbNsH-nEZM3NhSq8jU1BbRZQJ041aab9nrF+g@mail.gmail.com>
Date: Fri, 18 Aug 2017 13:44:05 -0700
From: Kees Cook <keescook@...omium.org>
To: Ran Shalit <ranshalit@...il.com>
Cc: "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>
Subject: Re: hardening mmc driver
On Thu, Aug 17, 2017 at 10:57 PM, Ran Shalit <ranshalit@...il.com> wrote:
> Hello,
Hi!
> What action should be taken to make mmc driver secured ?
>
> If there any wiki or document, which can help to understand better
> when a driver (like mmc) is considered secured ?
I don't have any specific pointers at the moment, but I think the main
focus for drivers (or really any software) is being extremely careful
with data processing and the validation of command arguments. Never
assume the commands you're getting will follow an expected protocol:
pretend the device at the other end of the bus (or the bus itself!) is
trying to attack the driver. Same for any commands coming from
userspace.
Are there particular things you're concerned about for MMC security?
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
