From: Markus Vervier <markus.vervier@x41-dsec.de>
To: git@vger.kernel.org
Subject: Covierty Integration / Improvement
Date: Fri, 1 Apr 2022 22:49:48 +0200 [thread overview]
Message-ID: <10fd679a-eb94-5380-2070-699f1b56a7b1@x41-dsec.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
Dear git developer team,
X41 is processing the current RfP and some questions came up regarding
the improvement / integration of Coverity Scans for git and the
estimation of the required work:
- Was there a special purpose for the Coverity integration (e.g. custom
queries for variant analysis or regression testing?) or did you try to
integrate it as a best practice / general security hygiene tool?
- Could you tell us more about the amount and types of false positives
and problems you've faced trying to eliminate them? This will help us to
understand the expectations / requirements for a successful integration
of Coverity.
- Could we get access to a sample of the scan results?
Many Thanks
Markus
--
Markus Vervier (Managing Director)
X41 D-Sec GmbH, Dennewartstr. 25-27, D-52068 Aachen
T: +49 241 9809418-0, Fax: -9
Unternehmenssitz: Aachen, Amtsgericht Aachen: HRB19989
Geschäftsführer: Markus Vervier
[-- Attachment #2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 6214 bytes --]
next reply other threads:[~2022-04-01 21:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 20:49 Markus Vervier [this message]
2022-04-03 21:36 ` Covierty Integration / Improvement Junio C Hamano
2022-04-03 23:16 ` Theodore Ts'o
2022-04-04 10:14 ` Ævar Arnfjörð Bjarmason
2022-04-05 22:22 ` Johannes Schindelin
2022-04-05 22:17 ` Johannes Schindelin
2022-04-06 15:08 ` Johannes Schindelin
2022-04-06 17:55 ` Theodore Ts'o
2022-04-06 20:20 ` Junio C Hamano
2022-04-07 11:49 ` Johannes Schindelin
2022-04-07 7:21 ` Markus Vervier
2022-04-07 11:58 ` Johannes Schindelin
[not found] ` <CAJY0qZLwQJ_6Me1em4X6M=YJb0O2+7rSYeKisLFOGH7_BW3Lww@mail.gmail.com>
[not found] ` <CAJY0qZJaBvwA19PN=Gm4c5gSVqYYBOoVwgF=1mZTNEjmXFSc7A@mail.gmail.com>
2022-05-10 17:46 ` Derek Zimmer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10fd679a-eb94-5380-2070-699f1b56a7b1@x41-dsec.de \
--to=markus.vervier@x41-dsec.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).