| 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
| ||
|
Message-ID: <ccca1437bf0885924619271a3f3ddd17af018149.camel@amazon.de>
Date: Fri, 16 Jun 2023 13:44:01 +0000
From: "Manthey, Norbert" <nmanthey@...zon.de>
To: "keescook@...omium.org" <keescook@...omium.org>
CC: "Woodhouse, David" <dwmw@...zon.co.uk>,
"Stieger, Andreas" <astieger@...zon.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Linux kernel Coverity model file
Dear Kees,
some time ago you pointed me at the github copy of the Coverity model
that is used for the Linux kernel analysis [1].
I investigated the effect of using this model, and compared defects
reported with and without the model. Before I deep dive into
modifications, I wanted to understand whether there is a more recent
version (the current one is about 4 years old). I currently have no
access to the public linux dashboard to directly check the effect
there.
In case there is a more recent model file, can you please update the
github repository?
In case I find additions, is the following a good procedure to share
model updates? I would run an analysis on a defined Linux commit with
the current model and the proposed additions, and would report the
effect on the reported defects. Is there anything else I am missing?
Best,
Norbert
[1] https://github.com/kees/coverity-linux
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
Powered by blists - more mailing lists