This was very informative, thanks!
Reverse-engineering an encrypted IoT protocol
11–20 of 44 posts
Re: Reverse-engineering an encrypted IoT protocol
#12> Sniffing the traffic from the device showed that it was connecting out to tcp.goodwe-power.com:200001
Is 200001 the right port number? Very good read anyways.
Re: Reverse-engineering an encrypted IoT protocol
#13Next time you find yourself reverse engineering a weird protocol - use ImHex. You can literally define patterns (in a C++ / Rust -like language) so that your binary file gets highlighted and processed. I can't recommend it enough - it's perfect for the job and it's free and Open Source. https://imhex.werwolv.net/
Just piggybacking here to mention a variety of other "interpret structured binary data" tools. Apparently I collect links to these (:
* fq - like jq for binary data: https://github.com/wader/fq
* Kaitai Struct - https://kaitai.io/
** visualizer, for the above: https://github.com/kaitai-io/kaitai_struct_visualizer/
* HexFiend - a hex editor, but with "binary templates" feature : https://github.com/HexFiend/HexFiend
** binary templates, for the above: https://github.com/HexFiend/HexFiend/blob/master/templates/T...
* binspector - https://github.com/binspector/binspector
* binary-parsing - a collection of links to similar such tools : https://github.com/dloss/binary-parsing
* unblob - https://github.com/onekey-sec/unblob
* ImHex, which you mention
Re: Reverse-engineering an encrypted IoT protocol
#14You should check out Recessim: https://recessim.com/
I think you would like the community.
Re: Reverse-engineering an encrypted IoT protocol
#15This reads similar to an intercom I am still in the process of trying to write a client for: https://grdw.nl/2023/01/28/my-intercom-part-1.html . Seeing nmap, wireshark, poor security. It definitely feels the same.
Re: Reverse-engineering an encrypted IoT protocol
#16He mentioned having a private, firewalled VLAN. Is there anywhere to get more info or example setups for the beginner homelabber? I've got Unifi gear, I poke around the interface. I realize I can make new VLANs, but what makes them isolated/private?
Also I see his complaints about half assed security but I actually am kind of relieved. If the security was implemented well we wouldn't be able to make our own man-in-the-middle prometheus exporters!
Re: Reverse-engineering an encrypted IoT protocol
#17Next time you find yourself reverse engineering a weird protocol - use ImHex. You can literally define patterns (in a C++ / Rust -like language) so that your binary file gets highlighted and processed. I can't recommend it enough - it's perfect for the job and it's free and Open Source. https://imhex.werwolv.net/
Just piggybacking here to mention a variety of other "interpret structured binary data" tools. Apparently I collect links to these (: * fq - like jq for binary data: https://github.com/wader/fq * Kaitai Struct - https://kaitai.io/ ** visualizer, for the above: https://github.com/kaitai-io/kaitai_struct_visualizer/ * HexFiend - a hex editor, but with "binary templates" feature : https://github.com/HexFiend/HexFiend **…
is binwalk still used these days?
Re: Reverse-engineering an encrypted IoT protocol
#18He mentioned having a private, firewalled VLAN. Is there anywhere to get more info or example setups for the beginner homelabber? I've got Unifi gear, I poke around the interface. I realize I can make new VLANs, but what makes them isolated/private? Also I see his complaints about half assed security but I actually am kind of relieved. If the security was implemented well we wouldn't be able to make our own man-in-th…
A VLAN is private/isolated to the extent that you don't route it to other networks. You could just block traffic between that vlan and the wan, or even potentially between it and any other vlans on your lan.
Re: Reverse-engineering an encrypted IoT protocol
#19> Sniffing the traffic from the device showed that it was connecting out to tcp.goodwe-power.com:200001 Is 200001 the right port number? Very good read anyways.
[deleted]
Re: Reverse-engineering an encrypted IoT protocol
#20Next time you find yourself reverse engineering a weird protocol - use ImHex. You can literally define patterns (in a C++ / Rust -like language) so that your binary file gets highlighted and processed. I can't recommend it enough - it's perfect for the job and it's free and Open Source. https://imhex.werwolv.net/
Thanks!