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

Fuzzing testing #1137

Closed
xlc opened this issue Feb 1, 2019 · 4 comments
Closed

Fuzzing testing #1137

xlc opened this issue Feb 1, 2019 · 4 comments
Labels
D2-substantial Can be fixed by an experienced coder with a working knowledge of the codebase. I5-enhancement An additional feature request. T10-tests This PR/Issue is related to tests.

Comments

@xlc
Copy link
Contributor

xlc commented Feb 1, 2019

It is important to ensure the substrate codebase is bullet proof and one way to detect potential issues is fuzzing testing.
Error like paritytech/substrate#1649 will be discovered on the first second of the fuzzing process.

All public interface should be fuzzed, including HTTP and WS RPC endpoints as well as the p2p protocol. This ensures malicious input cannot easily exploit / crash the nodes.
@cheme cheme self-assigned this Feb 4, 2019
@cheme
Copy link
Contributor

cheme commented Feb 25, 2019

I unassigned myself as I am not actively working on the task, and I do not want the assignment to prevent poeple from working on it. If someone take the task do not hesitate to contact me (I mostly run some low level fuzzing, but quickly reach some limitations).

@cheme cheme removed their assignment Feb 25, 2019
@Polkadot-Forum
Copy link

This issue has been mentioned on Polkadot Forum. There might be relevant details there:

https://forum.polkadot.network/t/how-to-make-a-fuzz-er-for-wasm-runtime/936/1

@ggwpez
Copy link
Member

ggwpez commented Aug 25, 2023

Its a quite general issue, but going to migrate anyway since more fuzzing is still a good idea IMHO.

@ggwpez ggwpez transferred this issue from paritytech/substrate Aug 25, 2023
@the-right-joyce the-right-joyce added T10-tests This PR/Issue is related to tests. I5-enhancement An additional feature request. D2-substantial Can be fixed by an experienced coder with a working knowledge of the codebase. and removed I5-tests labels Aug 25, 2023
@xlc
Copy link
Contributor Author

xlc commented Feb 28, 2024

We have a number of tools available so will close this.

@xlc xlc closed this as completed Feb 28, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Mar 26, 2024
@svyatonik
increase pause before pining Rialto nodes (paritytech#1137)
6d80241
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
D2-substantial Can be fixed by an experienced coder with a working knowledge of the codebase. I5-enhancement An additional feature request. T10-tests This PR/Issue is related to tests.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@xlc @cheme @bkchr @ggwpez @the-right-joyce @Polkadot-Forum