Skip to content

Instantly share code, notes, and snippets.

@Palantir555
Last active April 29, 2016 19:42
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save Palantir555/de23c2ceb5355efe6ec105a8d2d73486 to your computer and use it in GitHub Desktop.
Save Palantir555/de23c2ceb5355efe6ec105a8d2d73486 to your computer and use it in GitHub Desktop.

At this point we're just reading the data inside a device we own. It's all pefectly legal (UK). In the next stage of the process we're gonna start seeing private information regarding not just this device but also operational services from the ISP.

  1. The router I'm reversing is not from my ISP. I got it from Amazon so there would be no binding contract associating me to the company;
  2. It has never been connected to external networks
  3. You should never hit an external network with any kind of private info obtained from reversing a device
  4. These posts are not about TalkTalk or Huawei particularly. They are about exposing generalised bad practices in embedded development; users should know exactly which devices they can trust with their privacy and security and which ones they shouldn't. Developers should also be aware of which techniques are being used to attack their services so they know how to protect against them
  5. These kind of security issues have been exposed countless times in the past, and documented over and over again. Apparently no amount of exposure is enough; many companies are not willing to pay the money and effort it takes to do things right. Here's to hoping some day it will be
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment