-
Notifications
You must be signed in to change notification settings - Fork 7
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
Still works #4
Comments
I also recreated the cert (not sure if I needed) to added SANS with this page and added these SAN's from what the existing one has. I did leave it as key size 1024 as I'm not sure if SSLv3 has any limitations with key size. DNS:.ble2.sensornet.info, DNS:.blt2.sensornet.info, DNS:.cad2.sensornet.info, DNS:.dev.sensornet.info, DNS:.mdb.sensornet.info, DNS:.sensornet.info, DNS:*.tfl.sensornet.info, DNS:sensornet.info |
hey @jckruger are you going to release your updated version by any chance?
|
No I didn't get Python3 working but I have used the F5 to do it and it works well. Sorry I left the Python code as I have a working solution for my needs. I couldn't find a way to get the python 3 stuff working so abandoned it. I even tried older python but then had trouble finding repos that had all the dependencies. I'm sure there is a way with Python3 |
This is the code I am working with if anyone is interested 1 VIP with the SSL cert attached and this iRule
There is some debugging logging you could remove
This can be tweaked however you like You could use Cacti from a post a while ago [Efergy Engage Hub - Power Usage](https://forums.cacti.net/viewtopic.php?t=55314) You would just change the script to look for the text This should then work when you connect to the second VIP with cacti
|
Hey Aaron, I've had loads of troubles getting a python server to listen on SSLv3 in either python2.7 or 3x but I have managed to get the data from mine with an eval F5 that I tuned to listen on SSLv3 and log the data.
I hadn't sent it through to a server yet but have managed to get some data.
This is the iRule I set to log the data on the F5 just so I can see it. I'll send it to a port 80 service later into a database to then consume.
This is the result:
Looks like the value in the payload just continues to increase so I guess you just see what the value was between the 2 timestamps
The text was updated successfully, but these errors were encountered: