Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PoC fuzzing beaconmock #1848

Closed
5 tasks
corverroos opened this issue Mar 1, 2023 · 1 comment
Closed
5 tasks

PoC fuzzing beaconmock #1848

corverroos opened this issue Mar 1, 2023 · 1 comment
Assignees
@dB2510
Labels
protocol Protocol Team tickets

Comments

@corverroos
Copy link
Contributor

corverroos commented Mar 1, 2023 •
edited by dB2510
Loading

🎯 Problem to be solved

As part of our testing strategy, we have identified that fuzzing of the charon code base is required. There are three layers to fuzz test:

  • blackbox: upstream beacon API, downstream VC client, libp2p peers.
  • component: fuzzing "events" send and requested between components.
  • function: fuzzing function inputs.

This ticket is aimed at a PoC of blackbox testing, specifically beaconAPI fuzzing.

🛠️ Proposed solution

  • Approved design doc: link
  • Core team consensus on the proposed solution

The aim would be to run fuzzing as part of compose.
But for that, we need to be able to fuzz beaconmock.
Identify how this would work and implement a basic fuzzing test focussing on one or two beacon mock endpoints.

🧪 Tests

  • Tested by new automated unit/integration/smoke tests
  • Manually tested on core team/canary/test clusters
  • Manually tested on local compose simnet
@github-actions github-actions bot added the protocol Protocol Team tickets label Mar 1, 2023
@dB2510 dB2510 mentioned this issue Mar 25, 2023
Merged
obol-bulldozer bot pushed a commit that referenced this issue Mar 27, 2023
@dB2510
testutil/beaconmock: initial PoC for beacon fuzz (#1929)
3b3ef1b 
Adds initial PoC for beacon fuzz to fuzz test charon where beacon mock returns random/malicious responses to charon.

category: feature
ticket: #1848
@dB2510
Copy link
Contributor

dB2510 commented Mar 29, 2023

Closed by #1929

@dB2510 dB2510 closed this as completed Mar 29, 2023
@dB2510 dB2510 mentioned this issue Mar 29, 2023
Closed
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dB2510 dB2510

Labels
protocol Protocol Team tickets
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@corverroos @dB2510