linux-kernel

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] [day] [month] [year] [list]

Date:   Sun, 29 May 2022 13:21:07 +1000
From:   Tom Fitzhenry <tom@...-fitzhenry.me.uk>
To:     Michael Walle <michael@...le.cc>
Cc:     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>,
        Martijn Braam <martijn@...xit.nl>,
        linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: ...

On 25/5/22 08:30, Michael Walle wrote:
> Yes that would be great. Could also be one of the other
> 25h vendors, usually the continuation code is just ignored.
> I'd bet it some china SPI flash.

Physical inspection of the SPI NOR chip shows the chip is a 
"SiliconKaiser SK25LP128" on it. Thanks to biktorgj[0] for finding that.

Per 
https://github.com/Yatekii/jep106/commit/caa92b6f811609d49b46777fce0d1f84a3550c31, 
SiliconKaiser is a vendor rename from Chingis introduced in JEP106BD, at 
0x25 in bank/continuation 8.

Unfortunately I have been unable to find a datasheet for this chip.

I will add a siliconkaiser.c file with this chip "sk25lp128" using the 
SNOR_ID3 API, and submit a patch once I have tested this.

It's confusing that the chip's returned JEDEC ID has no continuation 
codes to reflect being in bank 8. Does this risk collisions if another 
25h vendor uses the same JEDEC ID?

0. https://github.com/Biktorgj