News for hackers. Stuff that matters.
Re:FreshTomato by smallerfish on Tuesday September 14, 2021 @08:15AM (#28523522)
It's maybe an unfair bar for open source projects, but I'd love to see a third party audit of the source code (and binaries). Downloading a binary that all of my network traffic goes through is...trusting. (And I have done so the past - dd-wrt & tomato; and, sure, it's not a ton different from using out of the box firmware from e.g. Tp-Link or Ubiquiti)
Re:FreshTomato by quesera on Tuesday September 14, 2021 @09:08AM (#28524166)
My logic is this:

Open source router firmware: a) is derived from well-established Linux/BSD networking stacks, b) has a smaller installed user base, so is a less-attractive target, and correspondingly c) has a lower value of exploit, which is more likely to be CVE'ed for reputation than sold for cash.

An audit would be interesting and welcome, but I have more ambient confidence in open source router firmware than vendor firmware. There's nothing unusual about the hardware in these things that the vendor has special knowledge of.

Also, most alternative firmwares have better performance, a better UI, are more frequently updated if bugs are found, and have more features than most stock firmware.

I've used OpenWRT, DD-WRT, and Tomato on inexpensive consumer routers in the past. Never regretted any of them. I purchase home router hardware specifically by the compatibility lists.

Re:FreshTomato by smallerfish on Tuesday September 14, 2021 @09:21AM (#28524360)
Yeah, it's a fair point that e.g. broadcom firmware is a good target (https://www.cvedetails.com/vendor/5420/Broadcom.html) because it's widely deployed.