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

A suggestion about specifying a source of secure randomness for better security #14026

Open
Gax-c opened this issue Apr 30, 2024 · 4 comments
Open

Comments

@Gax-c
Copy link

Gax-c commented Apr 30, 2024

Hello everyone! I'm new to netty and when I was browsing the code I found the following code in JdkSslServerContext.java here:

            ctx.init(keyManagerFactory.getKeyManagers(),
                    wrapTrustManagerIfNeeded(trustManagerFactory.getTrustManagers()),
                     null);

The code here use a "null", which means using the default securerandom. Although securerandom has already provided enough security, specifying one will ensure better security. For example, using SunJSSE.cryptoProvider for fip mode will be better.

@hyperxpro
Copy link
Contributor

Looks valid. @normanmaurer WDYT?

@normanmaurer
Copy link
Member

@hyperxpro @Gax-c I think we could add another constructor that take one ?

@hyperxpro
Copy link
Contributor

Yup. Shall I go ahead with a PR?

@normanmaurer
Copy link
Member

@hyperxpro sure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants