You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the fuzzers added to the develop branch of libiec61850 about 2 years ago are not currently integrated into OSS-Fuzz. This means they are not being continuously run to help uncover potential vulnerabilities.
I have experience with integrating fuzzers into OSS-Fuzz and would be happy to assist in setting up the necessary configuration. By integrating the existing fuzzers and adding more fuzzers to cover additional components of the library, we can significantly improve the robustness and security of libiec61850.
I would be glad to work on a pull request that accomplishes these goals. By expanding the fuzzing coverage and leveraging the power of OSS-Fuzz, we can proactively identify and fix vulnerabilities, ensuring the long-term reliability and security of libiec61850.
Please let me know if you have any feedback or concerns regarding this. I'm excited about the opportunity to contribute to the robustness of the library through enhanced fuzzing techniques.
The text was updated successfully, but these errors were encountered:
I noticed that the fuzzers added to the
develop
branch of libiec61850 about 2 years ago are not currently integrated into OSS-Fuzz. This means they are not being continuously run to help uncover potential vulnerabilities.I have experience with integrating fuzzers into OSS-Fuzz and would be happy to assist in setting up the necessary configuration. By integrating the existing fuzzers and adding more fuzzers to cover additional components of the library, we can significantly improve the robustness and security of libiec61850.
I would be glad to work on a pull request that accomplishes these goals. By expanding the fuzzing coverage and leveraging the power of OSS-Fuzz, we can proactively identify and fix vulnerabilities, ensuring the long-term reliability and security of libiec61850.
Please let me know if you have any feedback or concerns regarding this. I'm excited about the opportunity to contribute to the robustness of the library through enhanced fuzzing techniques.
The text was updated successfully, but these errors were encountered: