Request for FIPS-Validated netty-tcnative release
k-raina opened this issue · comments
Currently, users must fork the repository and rebuild with the FIPS-validated boringSSL tar to achieve FIPS compliance.
Considering the growing demand for FIPS compliance in security-sensitive environments, an official netty-tcnative release supporting FIPS validation would greatly benefit the open-source community. This would simplify integration and provide a reliable, community-supported solution.
I'm willing to contribute by raising a pull request (PR) to help implement the FIPS-validated release.
I have no idea what this would entail at all, so if it's not too much work maybe do a PR and we can have a look ?
@normanmaurer Is there anyway we can help to include #821 in build process?
@normanmaurer Gentle nudge for above request. TIA