Rooting, firmware analysis and persistent credentials of TP-Link TL-841Nblog.juni-mp4.com60 points by mindracer 4 hours ago
blutack 2 hours agoJust in case it helps anyone else, tio (https://github.com/tio/tio) is a great featureful alternative to picocom.pelasaco 2 hours agoi was searching for it today.. not available in my arch, unfortunately..dvdbloc an hour agoWhat’s your arch?
pelasaco 2 hours agoi was searching for it today.. not available in my arch, unfortunately..dvdbloc an hour agoWhat’s your arch?
BlackRabbit1 4 hours agoThe 841N works with OpenWRT. But AFAIR pretty much an EOL device with not much flash/ram.pelasaco 2 hours agothe idea is more to get into hardware hacking.. the hardware is kind of irrelevant ... the most important thing is a sane UART exposed, documentation, videos about it and etc..
pelasaco 2 hours agothe idea is more to get into hardware hacking.. the hardware is kind of irrelevant ... the most important thing is a sane UART exposed, documentation, videos about it and etc..
youareinsuffera 2 hours agoClearly the problem is the firmware was not written in Rust. I suggest a Rust rewrite so that these sort of errors will go away.pelasaco 2 hours ago:)wait until somebody read it.. its one vibe coding session away from done..
Just in case it helps anyone else, tio (https://github.com/tio/tio) is a great featureful alternative to picocom.
i was searching for it today.. not available in my arch, unfortunately..
What’s your arch?
The 841N works with OpenWRT. But AFAIR pretty much an EOL device with not much flash/ram.
the idea is more to get into hardware hacking.. the hardware is kind of irrelevant ... the most important thing is a sane UART exposed, documentation, videos about it and etc..
Clearly the problem is the firmware was not written in Rust. I suggest a Rust rewrite so that these sort of errors will go away.
:)
wait until somebody read it.. its one vibe coding session away from done..