Conversation

Notices

1. Matthew Garrett (mjg59@nondeterministic.computer)'s status on Monday, 29-Jul-2024 14:42:59 JST Matthew Garrett

   • qdot

   @qdot hey uh for reasons I'm wondering whether you have a list of devices with protocols that haven't been reimplemented yet

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Monday, 29-Jul-2024 14:42:57 JST Foone🏳️‍⚧️

     in reply to

     • qdot

     @mjg59 @qdot I'd also like to know, for what I think are similar reasons

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Thursday, 15-Aug-2024 07:16:50 JST Foone🏳️‍⚧️

     in reply to

     • qdot

     @mjg59 @qdot and I'd be happy to take a long at any that @mjg59 doesn't want. It's always fun to be able to using reverse engineering for good instead of evil.

   • Matthew Garrett (mjg59@nondeterministic.computer)'s status on Thursday, 15-Aug-2024 07:16:51 JST Matthew Garrett

     in reply to

     • Foone🏳️‍⚧️
     • qdot

     @qdot @foone yes pls

   • qdot (qdot@buttplug.engineer)'s status on Thursday, 15-Aug-2024 07:16:52 JST qdot

     in reply to

     • Foone🏳️‍⚧️

     @foone @mjg59 Ok, so, coming back to this multiple weeks later... >.>

     Most of our RE is incredibly easy, since it's just "take apart android app and read BLE code".

     There's a few devices we haven't handled yet either have embedded encryption, or are using qt/flutter for their apps (or both), which makes reversing more work than we're really interested in.

     If either of you are still interested in looking at this, I can provide play store/android app links to those.