-
Notifications
You must be signed in to change notification settings - Fork 6
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
How to run a test server #2
Comments
HttpServer is your best bet for a full server that stays up.
|
Also, if you would like to use your own certificate and you are on mono, it should be added to the certificate store using the |
As Antoine says, if your goal really is to test miTLS, you should not use FlexTLS as it is design to break the security properties of miTLS using the low level modules instead of the verified state machine. Just in case you are interested to know what happens with the FlexTLS failure : miTLS supported ciphersuites are listed here : |
I've already done that for the FlexApps tool, and didn't have to configure it there, so I assumed that HttpServer will default to the same one; help message not mentioning certificates in the context of --local-name didn't help either. I also did try to connect with the SNI of the certificate I did install and it still was failing...
Curious choice, given that TLS_RSA_WITH_AES_128_CBC_SHA is the mandatory to implement one from RFC 5246. |
I want to run a set of tests against the miTLS implementation. For that I want a server that stays up and handles all connections as they come.
When I use
./FlexApps.exe -s fh --accept 127.0.0.1:4433 --server-cert mitls
the server closes as soon as a single client finishes communication.Moreover, connecting to it while advertising support for just the
TLS_RSA_WITH_AES_128_CBC_SHA
ciphersuite causes it to crash:When I tried to start the
echo
andHttpServer
they complained about missing certificate:and, for HttpServer:
So, how can I start a server that stays up and supports all the ciphers miTLS supports?
The text was updated successfully, but these errors were encountered: