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.

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

fuzzing protocols not supported in the build #96

Closed
bagder opened this issue Dec 22, 2023 · 1 comment
Closed

fuzzing protocols not supported in the build #96

bagder opened this issue Dec 22, 2023 · 1 comment

Comments

@bagder
Copy link
Member

bagder commented Dec 22, 2023

Currently we build a set of different fuzzers for different protocols and we build a generic one for "all" protocols.

We build several specific ones for protocols that can't be fuzzed because our build does not build with necessary third party libraries:

  • the rtmp* ones need librtmp
  • scp and sftp need a SSH library
  • ldap(s) need OpenLDAP

Maybe we should just disable those or add additional libraries to the build?

The generic curl_fuzzer builds and specify "all" protocols:

  allowed_protocols =
    "dict,file,ftp,ftps,gopher,gophers,http,https,imap,imaps,"
    "ldap,ldaps,mqtt,pop3,pop3s,rtmp,rtmpe,rtmps,rtmpt,rtmpte,rtmpts,"
    "rtsp,scp,sftp,smb,smbs,smtp,smtps,tftp";

But this also means that it will try a lot of protocols that are not supported in the build as listed above. Should we perhaps remove those unsupported protocols from the list?

@cmeister2
Copy link
Collaborator

cmeister2 commented Dec 22, 2023 via email

bagder added a commit that referenced this issue Jan 15, 2024
Disable the protocols that need 3rd party dependencies to get added to
the build and therefore do not work in the current build.

Fixes #96
bagder added a commit that referenced this issue Jan 15, 2024
Disable the protocols that need 3rd party dependencies to get added to
the build and therefore do not work in the current build.

Fixes #96
@bagder bagder closed this as completed in 36b380e Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants