8 ms·
A look at home routers, and a surprising bug in Linux/MIPS
- sctb 8y agoWe've updated the submission from a tweet (https://mobile.twitter.com/dotMudge/status/1073676580289945600 https://mobile.twitter.com/dotMudge/status/10736765802899456...) to its linked article.
- lambda 8y agoHmm. The tweet, and thread on Twitter, has more actual information on the vulnerability than the page you linked to. You have to click through to the actual paper to get the additional information. I feel like the Twitter link gives a better quick summary information.
- sctb 8y agoI think clicking through to actual papers is something HN is up for!
- lucb1e 8y agoThen why not just link the paper? I personally like the summaries. Papers are typically written to sound smart, not to read nicely. HTML scales, users can configure the font, you can click pictures to enlarge... but instead we choose to use PDFs. Why? I speculate it is because everyone else who sounds smart does it. This particular paper is not as bad as most (no serif font, 8pt text, small and unreadable diagrams, references instead of practical links) so it's definitely not all directed at this particular paper, but I do question the usefulness of linking to a longer text instead of to a useful summary that has a link to the longer text. GP is right in that the first 15 words of the tweet told me more than the whole 269 word blog post. I also recognized the author on Twitter but not on the blog. I'm happy the tweet is still linked in the comments.
- lambda 8y agoYes, my point is, either leave the link to the Twitter thread (which also contains a link to the paper), or link directly to the paper. Linking to this summary page, which contains a brief abstract that contains more words but less information than the Twitter post, seems to be worse than any of the other options.
- JoshuaJB 8y agoNote that this does not effect all MIPS-based systems. The standard has included hardware floating point for many years now, it just seems some OEMs have neglected to upgrade or cut it for cost savings.
- floatingatoll 8y agoGiven the OEMs cited, would it be a reasonable estimation to suggest that the _majority_ of MIPS-based systems are affected?
- monocasa 8y agoYeah, most consumer routers I've dealt with don't have a FPU. They're more likely to be dual core than have an FPU.
- snaky 8y agoConsumers care about speed and don't care about security, so it's reasonable choice by vendors.
- monocasa 8y agoConsumers don't really care about speed, they care about checkboxes being checked. I'd be surprised if dual core really did anything for getting packets to and from the gateway interface any quicker. If anything I bet it makes it go slower with a naive implementation.
- saagarjha 8y agoConsumers care about security if they’re hacked.
- snaky 8y agoThey aren't hacked yet when they make decision about buying the router, and anyway they cannot differentiate based on security promises marketed to them by vendors.
- jstarks 8y agoThe paper was laborious to read. The short of it seems to be that Linux used to perform floating point emulation on MIPS by writing instructions to run to the usermode stack. The stack therefore had to be executable. This is known to be a bad idea. A couple of years ago, this code was moved from the stack to a new segment, but this segment is still writable and executable, and the address is fixed. This is known to be a bad idea. And of course the stacks are still executable because the commonly-used compilers haven’t been updated to request non-executable stacks. The paper does not propose a solution.
- amluto 8y agoThe “obvious” solution is to map that page RX and have the kernel write to it anyway because the kernel has magic kernel powers.
- blattimwind 8y agoOr map it twice. Once RX for usermode, once W at a random address for the kernel to write to. Some JITs use the same tactic.
- amluto 8y agoSome of the more extreme SELinux and similar policies don't like this either.
- tinus_hn 8y agoThe permissions are managed by the processor or the mmu. The kernel has magical powers to modify the permissions but can’t just ignore them.
- therealmarv 8y agoWhat are the best alternatives? I've read about some open source router alternatives (both hardware and software) in the past but forget the names. Also a very good HW with hardened open software could be great. Any information?
- ScottBurson 8y agoI use a fanless PC running OpenBSD. It's a bit of work to configure, but I think I can trust it.
- floil 8y agoFor myself, I switched everything over to Google WiFi's, precisely because they auto-update, and having worked previously on a security-focused team at Google, I trust them to have a competent security team and actually stay on top of the patches. I don't miss fussing with manually updating router firmware. Life is too short. On the other hand, my Nest thermostats were bricked after a software update this week, so maybe today I'm starting to see a crack in my "auto update is best" dogma...
- tatoalo 8y agoSame reason I've also switched to G-WiFi, lately I've been having issues with iOS devices disconnecting randomly and after a couple of seconds the connection would have been established again. I've tried playing around with DHCP but nothing changed, maybe my it's my ISP's router which is a pita to work with...(vodafone).
- TeMPOraL 8y ago> On the other hand, my Nest thermostats were bricked after a software update this week, so maybe today I'm starting to see a crack in my "auto update is best" dogma... It works best when the vendor can be trusted to only push security updates and occasional quality of life improvements. In general, automatic updates tend to be a vector for bloat, user-hostile features (e.g. spyware), and user-hostile business practices (e.g. remote bricking).
- 8y ago
- stefan_ 8y agoI mean, TP-Link could enable all of these basic security features and be lauded in the paper, then you look 5 minutes and find a "system(<web interface input>)" level bug in the firmware.
- ausjke 8y agoASLR, stack protector etc are all enabled in recent openwrt as far as I know, not sure about DEP though
- deleted 8y ago[deleted]
- jhcl 8y agoI am not familiar with the services all those routers provide to their companies but I am not bringing one online without first slapping OpenWRT on it. Well tested and to my knowledge reliable. Functional for everything I need it for.
- jlgaddis 8y agoI have a small embedded device (that runs OpenBSD) that serves as the router here at home. It works wonderfully for me and serves my needs well but it definitely wouldn't be a good choice for 99% of "home router administrators". Likewise, OpenWRT (and similar open-source router firmware) is a big step up in quality than probably pretty much anything any router manufacturer ships. Here's the thing... <rant> You and I -- and, I'd wager, the overwhelming majority of HN readers -- are easily capable of replacing our stock firmware, locking it down, keeping it up-to-date, and so on. Unfortunately, the average person (who likely just buys one of the cheapest routers they can find on the shelf at Walmart or Best Buy or similar) isn't. The average consumer simply doesn't understand that many of these devices they buy -- especially all of the new "Internet of Things" devices that have been popping up the last few years -- are completely insecure pieces of trash. Hell, many of them don't even care -- well, until it directly affects them personally, at least -- so long as "it works". They have no desire to learn a ton of stuff about computing, networking, or security -- they just want the ability to monitor what's going on in their house while they're away or whatever -- and they cannot understand why they should be required to (and I, personally, don't blame them). They don't know about the whole "convenience versus security" continuum or just how far away from the "security" side of that continuum that these devices they're buying to make life more convenient are. The average consumer (rightfully) expects that these devices that are available for them to purchase and install in their homes are (reasonably) "secure". They simply aren't aware of the sorry state of (in)security in the software industry. I think that within the next few years we'll begin to see (in the U.S., at least) some regulation with regard to security and software. I don't think any of us really WANT this to happen (it would be much better if the industry were "self-policing", of course) but it has become apparent that those who are producing these devices simply aren't going to devote the resources required to improve the security of their products until they are forced to. </rant> (Related: for the last seven years (until very recently) I worked for a small ISP. I was amazed at how very little many of the employees -- including the ones responsible for all of the networking gear! -- knew or even cared about security. With the exception of myself (and a recent college graduate who we hired as, basically, my "junior") nobody even thought about security unless or until "something happened" that required them to. Having experienced that, it became clear to me that the average person REALLY isn't gonna give a damn.)
- renox 8y agoNot surprised: I remember that MIPS has instructions to trap on integer overflow 'for free'(no need to pollute your icache with branch-on-overflow like other ISA) but compilers don't use these instructions :-( Conclusion: to a first approximation nobody care about security.