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

Unable to perform SSL connections with Jetty #15

Open
bissim opened this issue Jan 25, 2018 · 0 comments
Open

Unable to perform SSL connections with Jetty #15

bissim opened this issue Jan 25, 2018 · 0 comments
Labels

Comments

@bissim
Copy link
Collaborator

bissim commented Jan 25, 2018

It looks like Jetty agrees on using Elliptic Curve Cryptography while connecting via HTTPS to servers; however, this causes an error that ultimately results in Diffie-Hellman keypair for communication not being generated, thus throwing com.amazonaws.SdkClientException: Unable to execute HTTP request: java.lang.RuntimeException: Could not generate DH keypair (it may be another exception class rather than SdkClientException).

A workaround is presented in this question reporting the same kind of issue: the -Dcom.sun.net.ssl.enableECC=false arg must be passed to VM in order for Jetty server to continue execution.

Indeed, adding the VM argument to MasterServerMain run configuration makes the trick; however I don't know how to programmatically configure this argument nor if it's even right to disable ECC. Someone suggests that this issue may be caused by outdated BouncyCastle version. I'll try to look into the issue, however for the time being I'll stick around with the VM argument since I could not otherwise test EC2 instance generation and administration.

@bissim bissim added the bug label Jan 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant