Closed Bug 1923037 Opened 11 months ago Closed 9 months ago

Integrate CryptoFuzz in NSS CI

Categories

(NSS :: Test, task)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mdauer, Assigned: mdauer)

References

Details

Attachments

(3 files, 1 obsolete file)

No description provided.
Blocks: 1923038
Attachment #9434004 - Attachment description: WIP: Bug 1923037 - Integrate CryptoFuzz in CI → Bug 1923037 - Integrate CryptoFuzz in CI, r?djackson,#nss-reviewers
Attachment #9434004 - Attachment description: Bug 1923037 - Integrate CryptoFuzz in CI, r?djackson,#nss-reviewers → Bug 1923037 - Integrate Cryptofuzz in CI, r?djackson,#nss-reviewers

Cryptofuzz determines based on the initial bytes in a testcase which module to run first to then compare to the results of the existing other modules. If the specified module doesn't exist, it returns a std::nullopt and no differential testing is done. Since we are only compling with NSS and Botan, but using the public OSS-Fuzz corpus, this would result in a lot of wasted cycles. We can override this behaviour with --force-module=nss.

Attachment #9439018 - Attachment description: Bug 1923037 - Force Cryptofuzz to use NSS in CI, r?djackson,#nss-reviewers → Bug 1923037 - Tweak options for Cryptofuzz in CI, r?djackson,#nss-reviewers
Attachment #9439070 - Attachment description: WIP: Bug 1923037 - Fix fuzzers on 32-bit → WIP: Bug 1923037 - Fix Cryptofuzz on 32-bit
Attachment #9439018 - Attachment description: Bug 1923037 - Tweak options for Cryptofuzz in CI, r?djackson,#nss-reviewers → Bug 1923037 - Force Cryptofuzz to use NSS in CI, r?djackson,#nss-reviewers
Attachment #9439070 - Attachment is obsolete: true
Type: enhancement → task
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: