SensePostP4wnP1 by @mame82 for the @Raspberry_Pi Zero W is awesome, but needing a USB stem or cable makes for a clunky package. @RoganDawes found out that you can install Linux ON an LTE modem. It's the perfect platform for long or short distance P4wnP1 shenanigans! https://sensepost.com/blog/2023/p4wnp1-lte/
mame82 
- 928 Followers
- 114 Following
- 68 Posts
creator of P4wnP1, P4wnP1 A.L.O.A. and LOGITacker
Tom Gries (TOMO)Bei meinen Vorträgen zu P4wnP1 A.L.O.A. und dem Passwort-Cracking auf der #GPN21 bin ich von einigne nach den HID-Scripts und den Scripten für die Demolösung vom Passwort-Cracking gefragt worden. Ich hab sie euch unter https://github.com/tomo-one/GPN21 bereitgestellt.
CC: @mame82
radare 
Did you know that you can also use me for debugging canbus, serial or network protocols with the serial:// isotp:// socket:// io plugins? Should be easy to extend the support for usb sniffing and injection.
But here's a little demo using this feature (that's been supported since radare1 aka ~12 years)
Combined with the embedded js interpreter it can be used for fuzzing data communications and dissect packet structures
#ChatGPT finally accepts that it has not won (the AI behaved like SkyNet in preceding attempts)
Finally managed to play a successful round of Tic-tac-toe with #ChatGPT (after arguing about "vertical rows" vs "columns" for a while).
Runtime inspection of data sent out by TikTok !!before!! it gets encrypted:
Stumbled across one of my older "birdsite" threads on the topic, a step-by-step approach, which goes into detail about
- Android reversing utilizing @radareorg
- JNI specifics
- instrumentation with "Frida"
- combining everything with r2frida
Link (no idea how to "migrate" this thread to Mastodon tho):
https://twitter.com/mame82/status/1348993744775868417
In the first sentence of the last question, I wrote "would work" instead of "would not work" ... still #ChatGPT got the question and provided a meaningful answer.
Very impressive
6/6
Back to the real topic, give a understandable explanation on why this issue is relevant for HTTP2 (and less relevant for HTTP1) ... again, impressive answet