Skip to content

fuzz: Implement connect_block harness (PR #35850) - Follow-up 2 of 3 #540

Description

@kevkevinpal

mentioned in: bitcoin#35850

bitcoin#35850 (comment)

"Thanks everyone for the feedback and sorry for taking a bit to respond. I took most suggestions. I'm running the target again to get a shiny new coverage report.

A follow up could be to investigate if we can make this harness find https://bitcoincore.org/en/2026/05/05/disclose-cve-2024-52911/

(at)dergoegge I'll look into this more, but would this not be prevented by our fuzz determinism in the testing setup? If so, maybe we can try it after adding a littleFUZZ_NONDETERMINISM=1.
" - marcofleon

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    followupThis is a possible follow-up someone can work onneed to confirmNeed to confirm if this is still needed or already done

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions