So if I'm right, there's only 8 bytes that are used for encryption key in the Libre 2 protocol. 64-bit is not much for a key. Are they just using DES? I have the cyphertext, and what I _think_ is the correct cleartext. What's my best option to figure this out?
Easiest way with this little info would be imo by far to dig into the binary / driver that would be doing the encryption. Assuming it's available and it's not going through e.g. an online blackbox service.
-
-
I took your advice btw. And indeed we would have never figured anything out otherwise because it seems overly messy. Clearly a "roll your own crypto because you're just trying to make it hard for the next guy".
-
Are they just trying to be annoying or is it a case of "regulations means we have to do this"? I know for example the FTC has stupid rules around what users should be allowed to do with wireless equipment, and routers / wireless NICs end up implementing DRM to enforce that...
- 2 more replies
New conversation -
-
-
It's done locally. Been running traces without network to remove that option. The binary appears to have some anti debug features this time around. My ability with binary reversing is significantly limited, I'm a protocol kind of guy...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.