lists.openwall.net   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  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <06ce3d8eabd689f8755021d7ce08c3e0@walle.cc>
Date:   Tue, 23 Nov 2021 15:01:10 +0100
From:   Michael Walle <michael@...le.cc>
To:     Alexander Sverdlin <alexander.sverdlin@...ia.com>
Cc:     linux-mtd@...ts.infradead.org,
        Tudor Ambarus <tudor.ambarus@...rochip.com>,
        Pratyush Yadav <p.yadav@...com>,
        Miquel Raynal <miquel.raynal@...tlin.com>,
        Richard Weinberger <richard@....at>,
        Vignesh Raghavendra <vigneshr@...com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mtd: spi-nor: mt25qu: Ignore 6th ID byte

Hi,

Am 2021-11-23 13:40, schrieb Alexander Sverdlin:
> On 23/11/2021 09:14, Michael Walle wrote:
>>> 
>>> Some people ask themselves why this table keeps growing if there is 
>>> SFDP...
>>> I see the point in fixups, but maybe at some point we will be able to 
>>> support
>>> some devices just out of the box?
>> 
>> Are these features detectable by SFDP? Without knowing anything, as 
>> you ignored
>> my former question, I'd say no.
> 
> Well, I just had nothing to say on your question.
> It wasn't my intention to study security features of a chip, which I 
> don't use.

Like I said, without that information its hard for me do decide if we 
can just
ignore that last byte. (And yes I've already tried to get that NDA PDF 
via $WORK,
but I don't have high hopes with that).

-michael

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ