I have successfully written an Akka.net actor that communicates using System.Tcp(), how can I now convert this to use SSL?
I can't find anywhere on the Akka.net web site, except for this posting on github, which says 'it'll be done soon' in 2015.
In case anyone ever asks this question again, my solution was to create an Actor that implemented a tcp connection with optional SSL (using SSLStream) that was compatible with the original System.Tcp().
Related
I am trying to design something to authenticate my VERNEMQ mqtt broker clients using a SQL Server backend. I've read about webhooks and can use it but the deal breaker being that it does not support HTTPS. Was wondering if we can make vernemq directly authenticate from SQL Server, I've seen existing implementations on cockroach DB/Mongo/MySQL.
I think your 2 best options are a) to develop a native Plugin, possibly over ODBC driver, or b) contribute HTTPS WebHooks support to the VerneMQ project.
(as a maintainer of the project, I can say that PR's are always welcome ;)
I have an existing client that is written in ActionScript that I want to completely replace.
Python and Twisted appear to be the ideal candidate. No changes to the server are allowed.
1..What are the possible stumbling blocks?
2..Is it probable that Twisted can be used to create a bit perfect network connection that would be the same as the current client?
The connection is authenticated and uses SSL.
This is too hard to answer without knowing everything about your current client. Try something, and if you have a problem, ask a separate question.
Yes. Twisted doesn't have any restrictions on what kind of network traffic it can create.
Twisted does support SSL out of the box.
I'm struggling with Netty 4.0.8 Websocket client example and SSL and I can't seem to be able to send data to the Netty SSL websocket server example. Although there have been many posts around this issue, (I went through all, I believe), and the most common suggestion is to just add an sslHandler to the beginning of the pipeline, it doesn't work. Handshake seems to be successful as it is also indicated to a relevant question here.
I remember being in the same situation with version 4.0.0, but I somehow managed to get it working. However, things (and API) changed when I upgraded to 4.0.8.
Can the Netty developers add a working Websocket SSL client example to the examples? Many people struggle with this issue and that would be useful. Maybe the solution is just too simple, but an example would clear things. Again, sorry for reposting a question that might be already there, but the relevant question has also been unanswered and my reputation is just too low to add a comment to other relevant questions :)
I seem to have found a solution to my own question. The sample code on the client uses the channel.write() method, which seems not to send the messages to the Websocket ssl server. By using the channel.writeAndFlush() instead, messages are correctly sent to the server.
SharpPcap is a great library. I'm building http packet viewer for linux using it and it works fine! However is it possible to capture and decrypt ssl traffic? From one hand it would be exactly what ssl is designed against and so I would say the answer is no. On the other hand I see things like PacketDotNet.LinuxSLLPacket which give hope. So is this possible and if so where could I get some info on how to do this?
You should look at mitmproxy. It does exactly what you want it to do.
The way it works is by allowing you to set your proxy settings to mitmproxy running on 8080 by default. You install the certificate for the mitmproxy on your machine, phone, browser and it will essentially provide you with a man-in-the-middle.
An internal team, separate from my own, has stated that they prefer to do incoming authentication based on client certificates. Which sounds good to me, except that I haven't messed with them before and aren't quite sure where to start researching (Wikipedia went straight into a lot of detail that I'm not sure is pertinent to what I need to find out). If I have an IIS6 server with a web app that runs under an AD user account, what steps should I take to eventually fire off a request from that web app to a remote server, via .NET (I'm guessing HttpWebRequest)? I do see that we have an internal trusted certificate authority and all. Remote server is running Apache on Linux boxes.
I'm essentially in learning mode, not necessarily looking for a blow-by-blow list of what needs to happen (though if I could learn how it works while learning how to do it, that'd be nice too :) ... do you have any resources I could start looking into in order to figure out how to successfully authenticate securely via SSL with this remote server and communicate with it via client certs? Probably from creation of the client cert on up, though I'd like to more fully understand how it all works in the first place.
Here is a link - http://support.microsoft.com/kb/315588. Hope this helps with what you are looking for.