Over 25k Linksys routers vulnerable to sensitive information disclosure flaw
badpackets.net
badpackets.net
Sadly the only good home NAS solutions are build it your own (time, hassle) or pay for something more expensive from Synology.
This suggests a GUI is coming, not sure how it will be supported. I'd hope they'd make it possible to wrap that up as a Cockpit plugin. Cockpit is very cool, and is standard with Fedora Server.
https://www.samba.org/samba/GUI/ https://github.com/cockpit-project/cockpit/issues/3534
How is this even voted to the top?
Edit: Looks like I hit a nerve. God forbid anyone buy hardware for a purpose it was actually designed for.
Linksys produces and advertises a "best of the best" router with inbuilt alternative NAS feature that not only is so poorly maintained that it's insecure but also unusable by modern OS.
Some people find that appalling because they want a basic NAS without breaking the bank and more "stuff" lying around, expecting a high end router to cheaply fill that gap.
Some other people will find it appalling because it shows how little Linksys actually cares about the product and security as a whole.
They are all hot garbage and should not be used.
However, a router acting as a file server just sounds plain wrong.
Also, there are small, quiet[er] NAS devices around. A bit of searching found me this: https://nascompares.com/top-5-silent-and-low-noise-nas-of-th...
How so? What's stopping a NAS maker providing shitty support and/or firmware? I actually used to own a Netgear ReadyNAS Duo and I got rid of it mostly because of how loud it was and Netgear stopped releasing updates, which meant that things like Timemachine backup stopped working. And it was super slow for transfer speeds compared to what the drives could do.
For comparison sake, that Linksys router I have is super duper quick - it can actually do 100MB/s reads and writes on the connected drives which is very impressive(I thought) - this Samba issue is the only thing separating it from being great at it. And then I could install OpenWRT and then just install the newest version of Samba - it's just that I'm a bit lazy to do that.
Repeat offenders should be held accountable, standards should be enforced (like running point releases of OpenWRT, providing vendor skins as a package, thus the vendor doesn't have to deal with software updates).
Have you seen the state of salaries in the firmware dev industry?
That pretty much explains why firmware security is such a mess. You pay peanuts you get peanuts.
Only TI ever really went all in with a fully open stack that had support mainlined, problem being by the time their chips had full support upstream they'd be lagging 1 to 2 years behind Qualcomm, Nvidia, Mediatek, Allwinner, Spreadtrum, etc while having a much higher cost per chip, most of said cost being the decently written and upstreamed drivers.
For longer lived architectures (eg: AMD/Intel CPUs) totally new device drivers aren't needed on launch day, in part due to older upstreamed drivers still mostly working with newer hardware.
None of the aforementioned vendors besides TI ever got into this virtuous cycle of having upstreamed drivers, thus they've trapped their devices on sketchy, unstable & insecure BSPs that hurt the reliability, performance and sometimes the market image of the final product (eg: when the device randomly crashes or gets exploited due to latent bugs).
I've had a Linksys WRT1900AC since its release (specifically on the promise of OpenWRT support)
The device has gradually gotten better and better with each OpenWRT release. These days I get a blistering 60MB/s file transfers over Wi-Fi to my laptop. Even with newer, "faster" specced devices on the market, I really can't see any compelling reason to upgrade
It shouldn't even be hard for Linksys (granted with their history I wouldn't trust them) or someone to provide that option. With a reduced feature set and etc maybe updates would be easier too.
Granted when it comes to home commercial routing products it looks like it is all about a bazillion new features (at least the way they look on the box / shopping sites) ... not less.
There's regular firmware updates and the feature set is quite standard.
Though their routers and access points are separate: Eg: Their smallest router: https://www.ui.com/unifi-routing/usg/
Their cheap WiFi AP: https://www.ui.com/unifi/unifi-ap-ac-pro/
To configure the network you use their controller software, can be deployed on a raspberry pi but I just run it ad hoc on my laptop when I need to change some configuration.
Users don't explicitely care because they don't know. It doesn't make much difference when viewing YouTube videos, but there's more to the Internet than cat videos.
CG-NAT is crippling because I want to receive incoming connections like anyone else who has a connection to the Internet should be able to. Router manufacturers can do better. The world does not have to consist solely of cloud-based middle-men who take full advantage of the fact that all your data has to pass through them, and that you have to trust them.
https://www.voip-info.org/stun
Both Linksys and CG-NAT need to be avoided.
Also it is very likely you are still vulnerable from other users on the same ISP attacking you.
Also, QUIT BREAKING THE INTERNET. CGNAT is complete crap that breaks the internet peer model. Even ISPs not using CGNAT are pushing complete crap on users. For example last week I had a user that VOIP stopped working. They received a new integrated cable modem router from their ISP. If you rebooted the unit VOIP worked about an hour, after that it would stop passing VOIP packets (ran tcpdump on the server and watched them stop). If we ran VOIP over another port it would work (but had different issues related to changing around 50 phones so we only used it for testing). There were no options to disable SIP_NAT, nor any other settings that would fix the problem. Since this ISP also provided their own phone service I found the whole debacle rather anti-competitive. They simply have no interest in contacting the modem vendor and having them fix the problem.
We ended up supplying our own modem and router in this case and the problem was resolved.
It's not security nor a service. And also breaks a lot of use cases like P2P VoIP/gaming etc.
I assume if the ISP gives you an IPv6 subnet, you'd disable it? Or if you can't do that, switch ISP?