lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 12 May 2017 09:28:47 +0900
From:   AKASHI Takahiro <>
To:     "Luis R. Rodriguez" <>
Cc:     Greg Kroah-Hartman <>,
        Daniel Wagner <>,
        David Woodhouse <>,,
        Arend Van Spriel <>,
        "Rafael J. Wysocki" <>,
        "Li, Yi" <>,,, Petr Mladek <>,
        Johannes Berg <>,
        Emmanuel Grumbach <>,
        Luciano Coelho <>,
        Kalle Valo <>,
        Andy Lutomirski <>,
        David Howells <>,
        Peter Jones <>,
        "" <>
Subject: Re: [PATCH v6 3/5] test: add new driver_data load tester

On Thu, May 11, 2017 at 11:32:30AM -0700, Luis R. Rodriguez wrote:
> On Thu, May 11, 2017 at 11:26 AM, Luis R. Rodriguez <> wrote:
> >
> > It would seems to make sense to me to only need to verify files when read
> > for the first time, once its cache I don't see why we would re-verify them ?
> To be clear, the fw cache feature reads the files from the fs prior to
> suspend, and then uses the in-memory cache on resume. So it would make
> sense to me only to rely on fw verification on resume then when the fw
> cache is used ?

Good point. I was thinking of need for verification on resume.
As cache is not protected and visible to the kernel, some malware
might want to rewrite it :)

-Takahiro AKASHI

>  Luis

Powered by blists - more mailing lists