Replies: 10 comments 7 replies
-
Hi @Memphizzz thank you for your kind words. If the server and client both have If you wish to enforce that the certificates can be validated, set If you want to make sure the client and server use the certificates to authenticate with one another, set The primary reason for these default values is to make it easy to get moving with SSL. Thanks for the note on the README - I'll take care of that right now! Cheers, Joel |
Beta Was this translation helpful? Give feedback.
-
Hi @jchristn, thanks for your quick reply! Oh and I think that it should be "Connect()" instead of "Start()" for the WatsonTcpClient in the example ;) |
Beta Was this translation helpful? Give feedback.
-
Hi @Memphizzz in your case you'd want to install the certificate into the certificate store on each machine (on Windows, start > run > certmgr.msc) to import the PFX file into the 'Personal' store (you can either do this under 'current user' or 'local machine' - use 'local machine' unless you do this under the same context as the user under which WatsonTcp will be running). Once the certificate is loaded on both client and server:
I'll amend the README again - thanks for pointing it out! Please let me know if this works. |
Beta Was this translation helpful? Give feedback.
-
Hi @jchristn thanks for getting back to me this quickly again. The server is a ubuntu server running the exe under mono and the client is a windows desktop application, you wouldn't happen to know how to put that pfx into ubuntu's store? |
Beta Was this translation helpful? Give feedback.
-
I unfortunately don't have experience doing this in Ubuntu, but I did find this: https://askubuntu.com/questions/645818/how-to-install-certificates-for-command-line Out of curiosity, any reason you are using Mono instead of .NET Core or .NET 5? |
Beta Was this translation helpful? Give feedback.
-
I see, I will try that, thanks! It's an old project and I haven't bothered converting it to .NET Core yet since it has a lot of dependencies which I would have to check if they are .NET Core compatible as well. |
Beta Was this translation helpful? Give feedback.
-
Sweet! If you happen to take notes and get it working, I'd love to use them as the basis for a wiki article. (If you have time of course!) |
Beta Was this translation helpful? Give feedback.
-
Of course, I will report back as soon as I got it working ;) |
Beta Was this translation helpful? Give feedback.
-
Moved to Discussion |
Beta Was this translation helpful? Give feedback.
-
Good afternoon, would you be able to confirm how you point the watsontcp to an installed certificate in the certificate store? The examples I found point to using a test.pfx which if I have a cert in a store I dont have? Thanks :) |
Beta Was this translation helpful? Give feedback.
-
Hi there,
first of all, thank you very much for WatsonTcp and the time and effort you must have put into this great library!
I've just turned on SSL using a pfx file (with no password) which I copied to both machines. Just to see what would happen if the client had the incorrect certificate, I created another one and let the client connect using that. To my surprise there was no error and the client and server communicated just fine. Is this intended?
I've used this to create the certificates:
https://github.com/Azure/azure-xplat-cli/wiki/Getting-Self-Signed-SSL-Certificates-(.pem-and-.pfx)
Btw, the example on the front page shows "new WatsonTcpSslServer" but that class doesn't exist, instead the WatsonTcpServer takes the SSL related parameters.
Beta Was this translation helpful? Give feedback.
All reactions