Ubiquiti all but confirms breach response iniquity
krebsonsecurity.com
krebsonsecurity.com
I personally don't believe this. IMO, this is a company who is looking for a fall guy, and _most likely_ it's going to be somebody who raised a stink about all the security problems during their time there.
Form your own opinion, I'm just a guy who worked at Ubiquiti for a year, raising all kinds of hell about the security, architectural, and operational problems that I saw while I was there.
But what do I know...
That's a pretty common ploy. Been there, done that. Early in my career when I was naive enough to try to whistleblow on things over my head.
What I meant was something different. The breach, as I understand it, was quite critical. Ubiquiti in this case could take the standard corporate spiel of "it has hallmarks of a nation state attack, there was nothing we could do" bullshit disclaimer - but given the nature of this breach, every customer of theirs would now be wondering if $Enemy has put malware in their infra, and whether it isn't a good idea to smash it all with a hammer and buy new one from someone else. So I suspect Ubiquiti is going the other way, blaming it on a single, inconsequential individual, that absolutely, positively didn't give access to anyone else, and thus nobody's infra was in any danger.
(Note: I have no inside knowledge, or even any deep knowledge, of this topic - I'm just a random Internet person speculating.)
Nation state is not a fancy infosec way of saying country
(Can it really be because "nation state" is more fancy?)
I can understand, though, why they don't say "state" -- maybe that'd sound as if a single state in the US had attacked
I think your point about confusion with constituent states is spot on though
I really wouldn't like to migrate away but I can't say all the info that's been coming back has been making me want to have them as a part of my network infrastructure.
I really just want to manage an OpenWRT based network with one central web interface and not have to deal with corporate/state entities deciding to push fun changes out in the management interfaces that power these systems.
[1] https://wiki.mikrotik.com/wiki/Manual:CAPsMAN
[2] https://wiki.mikrotik.com/wiki/Manual:Upgrading_RouterOS#Rou...
Most of the value proposition of the Unifi lineup is I can look at a single website that I host and see the WiFi clients connected to an access point, what switch feeds that access point internet (and whether its linked at gigabit or 100Mbps), uptime on all devices involved in the stack, whether the client has poor WiFi quality, trouble DHCPing, etc.
The single pane of glass to view everything when I am many miles from the networks I support is essential. Compared to when these sites were on PFSense before migrating, these networks have improved uptime, rapid remediation of issues, and changing VLANs, SSIDs and labeling each client on the network is a snap.
Edit: Borrowed /u/bpye's single pane of glass term
> The single pane of glass to view everything when I am many miles from the networks I support is essential
It's also why we're talking about this.
If they never forced people to create a cloud account - and instead allowed people to choose - this would be wildly different.
Anyone who is forced to get a UI.com account (eg: UniFi Dream Machine and UDM-Pro owners) should change their credentials and do a factory reset on their routers and Access Points ASAP.
This is a miserable user experience. If you do a reset and don’t know the SSH password on APs or cameras you get to spend a hellish few hours crawling though ceiling insulation, climbing ladders and physically resetting devices. It’s so shit. I’ve just done it, but not due to security concerns, but instead because of a UDM-P crapping out randomly.
With the UDM series, the integrated controller ensures you lose everything if you have to factory reset, site to site VPNs have to be manually configured, and numerous other minor annoyances crop up (like UI.com not always being able to connect to the controller).
And I like the fact that I can an overview of the state of my network; one of my wired links to an AP would degrade to 100 Mbps at times, and being able to see the link speeds easily was very helpful (it was a bad ethernet cable in the end).
Before I moved to Ubiquiti I had a spate of problems with my fiber broadband, which would stop working for a few minutes at random, resetting my RDP connections. I had a vendor-supplied Linksys (I think?) router, and trying to troubleshoot it was painful. If I ever have such problems again I'll have much better diagnostics.
That said, I won't buy any Ubiquiti gear that requires the cloud, and my faith in the company is eroding. But, like others, I would be at a loss what to replace my gear with at the moment. I just hope it'll function well enough until either Ubiquiti gets it act together (again?) or a viable competitor arises.
Checking the cable is like checking if the power is on, it is NEVER the cable - except in networking for some reason. Half the time it's the cable.
I suspect that's the most common cause of network cables 'going bad' in the home.
Didn't take us long to notice they had laid the cable like electricians, neatly following the contours of a few door frames with tight 90 degree bends.
Glad I learned that lesson early.
It uses OpenWRT, and you can access it remotely.
Crap wifi was a huge thing I dealt with. Unifi fixed that completely. The ability to run a relatively complex network (by home network standards) with multi access points is nice, but the ability to administer them without CLI interface is great. I loved my edge router but touched it with trepidation. It was rock solid except when I was sucking with it. Unifi suits/suited the enthusiastic amateur.
> I run a small network with one big router and several access points, and at least with Mikrotik's gear, it's pretty much fire and forget.
Unifi used to be too, with an interface that was a bit difficult to navigate (settings spread among about 20 tabs, but it was possible to get the job done without sshing to components).
Now it’s flakey. I just rebuilt my last week which was working fine but I couldn’t log in and the UDM-P screen said it required resetting. Dark times.
To answer this for me personally (and I suspect this is a pretty common answer): To use the best, and to explore technologies that I might suggest to business clients.
Business clients love central management interfaces.
As well, I’m honestly kind of done with managing fiddly “snowflake” devices, and central management interfaces usually come with the ability to standardize the config across devices.
I definitely don't "need" it. But it's veeeeeeeery convenient. Especially when it comes to security, being able to see which devices have updates and perform them all from one screen, is extremely convenient. I'm highly interested in paying for convenience at home.
Thankfully I don't use their cloud based management interface -- as far as I know this breach does not affect my local UniFi Controller. Hopefully this is a rude awakening and Ubiquiti goes back to their old consumer focused approach.
First problem is 5GHz is terrible at going through walls, I don’t believe it will even go through a single brick wall and maintain decent bandwidth. Even 2.4GHz is considerably slowed by 2 or 3 drywall/plywood obstructions.
Second problem is can the mobile device you’re using return that signal through all those walls to the access point. I have noticed an huge increase in quality and snappiness of FaceTime and other high up and down bandwidth activities once I added more access points so that connections are going through only 2 or 3 walls.
For another reference, I have a hotel that needed to upgrade its network to meet the brand standards for signal strength in all the rooms, and we had to end up installing 6 access points in the drop ceiling of each hallway 15 guest rooms in length (each guest room is ~15ft wide, so the corridor was ~225ft long). It resulted in the elimination of almost all guest complaints about the wireless network.
Make no mistake, it still "works" with just one, only slower.
Ah, the ones that have wire mesh underneath? That would do it.
I like UniFi in wall access points in the room I’m inside.
Not super complex but no single nighthawk is gonna do it and the unifi management interface does the job. I'm not cloudy though.
One important thing to think about when planning your WiFi deployment is if you have things that have poor connectivity, everything on that channel suffers. I can have several devices running at several hundred megabits of quality, but a single device being really slow bogs down the channel and suddenly everything else starts getting lots of jitter and overall poor network performance despite most devices having good signal quality. Also, your device may show it has good signal strength but it might be poor quality (bad SNR) so in reality its a poor link speed. Having things physically closer usually results in better average SNR, meaning higher speeds for everything on the channel.
Also, as others have mentioned 5GHz might make it through a wall without a lot of stuff in it, but its not going to penetrate very well through several walls. Having my AP's in the hallways means there's usually only one wall with minimal stuff in it between a device and the AP, so each device usually reports at least several hundred megabits of throughput possible.
I need new APs soon.
It wasn’t a problem until covid when multiple meeting or other streams just performed poorly on a marginal network. The Ubiquiti gear made it easier to run antennas for optimal signal.
The hot thing to do is to shit on them, but I’ll be sticking with it. They’ll emerge better from this crisis and if you think that any competitor in this price point is better, you’re delusional.
Works amazingly on heating and cooling bills, but it's a pretty solid wall to radio waves.
[0] https://www.ibhs.co.uk/foil-backed-mineral-wool-50mm-thick-x...
COVID must have been a massive boost to their bottom line.
I’m no market analyst, but the last year, even including the last week, has been very good to Ubiquiti.
https://www.nasdaq.com/market-activity/stocks/ui/advanced-ch...
I possibly could have done it with two if I ignored the outside areas but one definitely wasn’t enough even with careful placement.
Edit: obviously 2.4ghz penetrates further, but 4k streaming on multiple TVs doesn’t go well with the bandwidth (and interference) on 2,4
Its pretty simple, having each device individually managed is archaic, a pain in the ass and there is no technical reason why it has to be that way.
6 doesn't add very much over 5 in real world setups, very few devices even support 802.11ax yet, and the bleeding edge has never been Mikrotik's target segment.
6E gear is not really available anywhere yet, so it's really only an issue for people who just have to have the latest gear at all times. For the majority of people, 802.11ac/wifi 5 is what their hardware supports, so that's what they need.
The hAP AC² serves my home networking needs quite well, with an additional AP to better cover the whole apartment.
You can access your network from Tether app via cloud if you wish, too. When you enable Mesh, everything is controlled via the router. You don't need to manage anything on the extenders.
RE200 can work as an AP if you can get them a CAT5, or can provide wireless to Ethernet capability. I don't need home-wide VLANs and other exotic stuff (for a home network), but you can adjust QoS on the router in three levels and it has an embedded OpenVPN server if you fancy.
While not network related, you can temporarily or permanently turn off all LEDs on the devices so they don't create any light pollution, something I love to have.
All in all it's a great package, for my home network, at least.
That's very surprising to hear. The decades-old spanning tree protocol can prevent that. I in fact have a friend who has done the exact same thing (Google Wifi with wired backhaul) with no problems. It switches from 802.11s to STP with no problems.
The next thing I want to do is reflash my Unifi APs with OpenWRT [3] - the hardware is fine, but at that point I'll get all the support without the controller software.
My home environment is fairly basic so moving away isn't too hard - this would obviously be much harder for a small business...
[0] - https://francis.begyn.be/blog/nixos-home-router
[1] - http://www.willghatch.net/blog/2020/06/22/nixos-raspberry-pi...
My understanding is that this doesn't work anymore because Ubiquiti started signing firmware. Your link also goes to a blank page.
[0] - https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=fb...
I like this idea too, but would prefer that the router was physically separated and before any hardware that was in the network.
Is this a pointless concern?
They want to brush this under the rug as fast as they can, and that means using the opportunity to pin it on somebody that's been "problematic".
The culture at Ubiquiti collapsed in my last year there. The company was unrecognizable because everyone was quitting so fast.
If there's a cyber security firm that's been hired to provide analysis they're going to be combing through egress traffic to find anything suspicious. But, egress traffic is difficult and expensive to analyse.
Worse yet, the attackers could easily just sit there and not use their attack methods for a little while and start up their compromises in weeks or months. You couldn't be certain nothing's still there till you ripped the AWS resources out and replaced them.
everyone believes it
Nobody blames the NSA in these circumstances, ever.
Would you be able to point to unofficial compatible operating systems for Ubiquiti devices? I want to remove Ubiquiti software from the devices I bought and paid for.
They might as well come out and say they have well-developed evidence that the perpetrator has an IQ over 50.
>Form your own opinion, I'm just a guy who worked at Ubiquiti for a year, raising all kinds of hell about the security, architectural, and operational problems that I saw while I was there.
You are a lawn man/woman.
Security problems: I have to show my badge EACH TIME I go to the bathroom
Architectural problems: these bricks are the WRONG COLOR!
Operational problems: The painters used the WRONG COLOR OF OFF WHITE!
Again, I know this isn't what you ment, but I enjoyed transposing a well written critique of their software from (presumably) a knowledgeable software guy into a lawn person in a jumpsuit.
Thank you, amd have a good day.
Looking at the firewall logs it seems the devices try to ping (ICMP type 8) a bunch of AWS IPs every few hours. The controller tries to connect 80/443 on different AWS IPs a lot more often, even without me navigating the web interface. Other than that, no ill effects. Device firmware update notifications are gone, just says "up to date" now.
Interestingly, I still see the ad for their "dream machine" on the dashboard, as it seems to be baked into the controller. It's also trying to load external resources from "net-fe-static-assets.network-controller.svc.ui.com" while navigating the new web interface. The "classic" interface still seems to be truly self-contained. Using the latest controller version as of today (6.1.71-15061-1).
Condensed firewall logs for reference below. Not that it matters much, but why not.
Unifi controller VM:
zgrep unifidrop /var/log/syslog\* | grep "SRC=$unificontroller" | awk '{print $12, $21}' | sort | uniq -c | sort -h
5 DST=13.224.246.17 DPT=443
5 DST=143.204.174.59 DPT=443
5 DST=143.204.174.83 DPT=443
5 DST=34.210.116.187 DPT=80
5 DST=34.211.38.191 DPT=80
5 DST=34.218.198.60 DPT=80
5 DST=99.84.5.14 DPT=80
5 DST=99.84.5.24 DPT=80
5 DST=99.84.5.51 DPT=80
5 DST=99.84.5.82 DPT=80
7 DST=13.224.246.67 DPT=443
7 DST=13.225.74.11 DPT=443
7 DST=13.227.220.19 DPT=443
7 DST=13.227.220.38 DPT=443
15 DST=54.201.165.155 DPT=443
25 DST=44.239.243.150 DPT=443
28 DST=44.238.226.202 DPT=443
28 DST=52.89.51.163 DPT=443
28 DST=54.218.175.125 DPT=443
Unifi devices (all ICMP 8): zgrep unifidrop /var/log/syslog\* | grep -v "SRC=$unificontroller" | awk '{print $12}' | sort | uniq -c | sort -h
2 DST=13.224.230.94
2 DST=143.204.9.24
4 DST=99.84.6.169
6 DST=52.84.94.172
6 DST=54.230.54.165
24 DST=52.222.138.169There was a falling out between teams while I was there because the cloud team wanted to collect stats from APs even when users disabled analytics in the UI. It was so bad that some of the developers and one of the leads quit because they didn't want to be a part of it.
Someone on Reddit started reverse engineering it https://www.reddit.com/r/Ubiquiti/comments/lwr4ud/update_ubi... The APs are reporting things like connected clients and client stats according to recent dumps. Do you have analytics disabled in the UI and this is still happening?
This hardware is far from cheap and consumers are literally paying for adware/spyware. I really hope Ubiquiti stock takes a nosedive over the next year.
Compared to your average all-in-one home router, however, these are also markedly less shitty.
Don't get me wrong, I see why you would spend money on Ubiquiti gear; in fact, I run a similar setup. But for your average non-technical user, it's going to be a harder sell. It's the same reason you (probably) don't run a several thousand euro enterprise WiFi at home.
And yes, Ubiquiti most definitely isn't for non-technicals (Except for the AmpliFi stuff). It's more prosumer grade stuff. More features than the "gaming wifi" crap but still easier to configure than official Cisco stuff.
Unless, of course, you find spyware shitty... Which one would think most reasonable people do.
There was no company wide communication, and all communication channels were made private, and if you sent an email to more than a couple people you were directly rebuked by the CEO. Nobody felt like they were trusted, and the norm was for most engineers to have absolutely zero idea of what was happening in the company outside of their direct project.
Teams were constantly at odds and pitted against each other, and the CEO never resolved any conflicts between teams or employees. The company (at least the software side) was treated like Thunderdome. Some team leads and office managers took care of their people, but most people were just beaten down. I don't think I'd ever seen a less motivated, more dejected group of software developers than I did during my time there.
IMO, this kind of bullshit clown show starts from the top. And as long as the top doesn't want to fix it, it won't get fixed. And since software almost invariable ends up reflecting the structure of the organization that produced it, you get this kind of security shit show.
I hope this is the last one and they get their act together. But realistically I can't believe that'll happen.
I couldn't understand why the ex-Amazon cloud lead was also in charge of Slack. When he made all channels private and put a Slackbot in every channel to monitor conversations, I knew it was all over. I'm worried his Slackbot logs are part of the leak. Guy had his hands in everything :(
Same guy who took over GitHub and forced everyone into his self hosted source control because he couldn't trust Github. That decision didn't pay off.
He did.... what? That sounds like straight out of a Dilbert comic.
He was "in charge" because he convinced Robert that he was the right guy for the job by finding a security flaw that let him log into Robert's personal UniFi Protect setup at his home. At that point Robert basically gave him carte blanche, but also started directing him to lock everything down. More than a bit of paranoia there, in my opinion.
In the Krebs article the whistleblower calls out forging SSO logins as one of the things that was compromised. If the attacker is really an ex-employee like Ubiquiti says, then it's scary that the SSO signing keys aren't even being rotated after the account forgery stunt.
> Adam says the attacker(s) had access to privileged credentials that were previously stored in the LastPass account of a Ubiquiti IT employee, and gained root administrator access to all Ubiquiti AWS accounts, including all S3 data buckets, all application logs, all databases, all user database credentials, and secrets required to forge single sign-on (SSO) cookies.
sounds smart to me. I wouldn't trust github either.
From the outside it seems like accepting fault and product returns would smooth waters. Acknowledge faults on their own forums and Reddit subs and also provide times lines for fixes (then stick to them and update threads!)
The hardware is mostly good. The weird bugs and company management are turning a strong community of users against Ubiquiti.
After Brandon left, Unifi went to shit. There hasn't been one significant feature or major function added to Unifi since then. Routing hasn't move at all in 7 years. Well, in a recent beta you can now have multiple WAN IP addresses. Whooppee. Switching hasn't gained anything - layer 3 is utter missing. QoS? Good luck.
Unifi is fine for networks with simple needs, good for prosumer use or small businesses - but if you start to scale requirements it falls over pretty quick.
It was very promising when routing/switching was added to Unifi - but it's never been fully realized :(
The good thing about them being a public company is there is some accountability from outside the company. Looks like they're already being investigated for fraud for downplaying the breach and their stock price took a big hit. Hopefully this all leads to the CEO being replaced and things turning around.
Sad situation. I knew a lot of good people there who cared about making good products during the UniFi glory days. Everything collapsed fast. I knew we were in trouble when the CEO's early employee friends were disappearing and their offices were being closed without warning.
I still see no realistic alternative for the "distributed decent wifi at a reasonably SMB scale" wireless product though. Miraki I guess is as close as it gets, but then you are locked in 100% cloud and it's certainly not remotely the same price point.
I am relegating Unify to manage my APs and (some) switches for ease of use - while I enjoy CLI fun, it gets old doing routine stuff the for the 100th time.
Hopefully another company really steps up in this space, because I can't imagine having to go back to the dark days of individually managed APs and all that.
No, that is too late. You get even sooner an even greater insight into leaders of a company based on the things they build. Does a hardware company try to force its users to move things to a proprietary cloud for no clear benefit? You know it's a company run by ar*eholes. Nothing more to know.
At someone who runs a UniFi network in my home with just 4 pieces of hardware (gateway, wired switch, and 2 PoE WAPs) I'm really curious if there are solid alternatives for a managed home network. UniFi really hit a sweet spot of price/performance that made it a somewhat pricey; but, not totally unreasonable option for the home.
Any suggestions from the HN crowd?
For me it's one of the few options available because my ISP forces me to use a transitional IPv6 technology called "MAP-E," which the UniFi products don't support. I switched ISPs after purchasing my equipment and ended up with $700 of dead weight.
"Section 7. Audit.Synology will have the right to audit your compliance with the terms of this EULA. You agree to grant Synology a right to access to your facilities, equipment, books, records and documents and to otherwise reasonably cooperate with Synology in order to facilitate any such audit by Synology or its agent authorized by Synology."
https://www.synology.com/en-us/company/legal/terms_EULA
I can't verify the claims about "Peoples' Republic of China PRC" being allowed to enter a non-Chinese citizen's home (US citizen) to protect IP. Might be applicable to Taiwan or Chinese citizens.
I am not a lawyer so I cant determine whether this EULA is enforceable in the US or EU. Regardless of enforceability, I would be hesitant to buy Synology products as well. Who knows what backdoors they have implemented in order to satisfy the Chinese government.
As far as I know that clause was created years ago when people were using key generators to make keys for surveillance station licenses. I don’t know of anyone who has ever actually been audited.
The lack of mounting options and Poe power are obviously a downside for a lot of implementations but overall they appear to be solid.
Their switches and APs are still really good. For alternatives, it depends on your goals. How many configuration options do you need? Is cloud management bad? Any more.
For consumer: Google, Eero, Orbi and some of the others are good. If you want more control, you need to venture into the SMB and Enterprise space.
Unifi, Engenius, Aruba Instant On, Tp-link Omada, Mikrotik, Ruckus and maybe some others. It really depends on your desired feature set.
Not sure how much I’d trust their products unless they’ve really done a 180 in terms of security in the last year or two.
I'm running openwrt on a rpi4-2gb (usb ethernet dongle for WAN, onboard ethernet for LAN) and and a TP-LINK EAP245 access point and have been extremely happy. For reference, my connection to my ISP is 940 down / 840 up, and the pi4 handles SQM/QoS on this line without breaking a sweat
I do plan to flash openwrt on to the eap245 as soon as the 5ghz drivers become usable, I like the hardware and the stock firmware isn't bad, but just not nearly as good as openwrt. there's a port of openwrt to the eap right now but 5ghz speed is limited to 2.4ghz speed for some reason at the moment.
More shiny products that increase bottom line is great but many IT officials rely on UniFi as well, I wonder how they’re responding to enterprise customers.
I just hope this incident will at least get them to put some emphasis on security again as well.
it pains me to say this because I was there for the UniFi glory days: The old Ubiquiti is dead and gone. Almost everyone I know quit.
I hope they can land on their feet and return to the glory days but I don't have much hope. The company got toxic fast at the end
Because the platform integration and ease of administration, no one else has and it’s great for simple networks.
We always thought MikroTik was one of the biggest competitors for low cost equipment. Our main advantage was the UBNT community and having famous supporters like Troy Hunt which MikroTik didn't have. The community fell apart after the redesign killed it and I don't think people like Troy Hunt will endorse Ubiquiti now so it should be interesting to watch what comes next
Freudian slip?
If they could, it seems like it would incentivize more caution about what data is collected, and more investment in the security of that data.
I also imagine an insurance industry, where the insurers then have expectations about what kinds of security must be in place to get reasonable premiums.
At a former company, we had a nasty case of BEC with a vendor that ultimately cost us well over six figures - over 90% of the loss was recouped by filing a claim with our insurance.
> Ubiquiti’s IoT gear includes things like WiFi routers
I understood IoT to mean wifi toasters, TVs and other home appliances. Since when was a router an IoT device? Are we going to call all nework devices IoT now. This strikes me as taking rather too much journalistic license.
In fact wtf is a WiFi Router. I use Unifi to deploy Wireless Acess Points on a LAN with centralized control. It is possible to do this without them having internet access at all, but it makes it rather harder to update everything. This is miles away from IoT.
Describing Ubiquity as a IoT company is like calling Cisco, Juniper, Mikrotik and Aruba IoT companies. This sounds like an attempt to feed the narrative that the IoT is going to eat us alive.
Let us focus instead on what Ubiquity actually did wrong, isn't that bad enough?
Wi-Fi router I would take to mean one of those consumer all-in-one boxes, which is what the UDM fits the description of.
I agree that this distinction is unnecessary. When we consider who wrote the article and who it's for, we should expect a bit more granularity than foggy acronyms.
[1]: https://arstechnica.com/gadgets/2021/03/buffer-overruns-lice...
I just wish I had completely deleted my Ubiquiti account when I sold my WAP.
In fact I'm buying two new R710s to replace my very old UAC AP Pros. Was going to get the new AP 6 LR but after UIs current woes (and them dropping support for my APs way too early) I'm done with them.
Though, After using Ruckus in Corp/Enterprise they've sold me on how capable their APs are, it's real deal high density stuff.
PF is created and primarily maintained by OpenBSD
OpenBSD’s base system (without extra packages) includes PF and has a focus on security.
PF in freebsd is several major versions old.
nftables (like iptables before it) is rule based and not bucket based. So high numbers of rules will not affect pf’s performance like it does with nftables.
But, for home users, probably not noticeable. Though I prefer the syntax of PF personally.
[0]: https://upload.wikimedia.org/wikipedia/commons/3/37/Netfilte...
[1]: http://mailing.openbsd.misc.narkive.com/jtIB9W3w/pf-packet-f...
What does this even mean? Do you have any documentation to explain?
>So high numbers of rules will not affect pf’s performance like it does with nftables.
This is wrong. From OpenBSD documentation:
"More lines being evaluated for each packet will result in slower performance."
[0]https://www.openbsd.org/faq/pf/perf.html
It's not 2001 any more. Nftables and Linux have left the BSDs in the dust.
I posted the architectural diagrams of both in another comment on this thread yesterday, I think you missed that.
That is how it works in nftables.
>but I can see how it could be confusing if you’re used to iptables and only think in those terms.
Considering you're misunderstanding some basics about nftables and iptables here, I think you need to look in the mirror.
>I posted the architectural diagrams of both in another comment on this thread yesterday, I think you missed that.
I saw, and it only reenforced the fact that that's how nftables works. Hilariously enough, the OpenBSD webpage crashed and wouldn't load, giving various 500 and 42X errors.
Without those ties to their infrastructure, this breach would not be as severe. It would just cause an attacker to see what I've bought from them, nothing else.
I'm glad I can still use the unifi controller in docker without any ties to UI.com however their later stuff like Unifi protect, access, talk etc no longer works with that.
I guess it's for the usual reasons. Telemetry / product improvement, and also more marketing data. Data is the new gold :)
Beyond stupid.
So even if you run a local controller, I see two very serious vectors:
1. The "Ubiquiti account signin" functionality - you probably had it off, but I'd like a confirmation that it doesn't keep a backdoor open anyway.
2. Having a malicious firmware update put on the servers. If it took months for someone to find the vulnerability, who knows how long the servers could push a compromised controller/firmware builds for the hardware.
For example, I run the UniFi controller on my FreeNAS server. There are no forced updates to it. It doesn’t update unless I update it. The firmware on my APs doesn’t update unless I update them from my controller.
The firmware could be compromised at the source so your FreeNAS doesn't help at all when you download and apply a compromised firmware update.
Unless you're not updating your APs and keeping them vulnerable in that way :)
In my case, no, they cannot push anything to my devices. Obviously, I could pull down compromised firmware. But that's always a risk with software that I don't personally verify, which is like 99.9% of software.
As a side note: obviously this security incident doesn't give me a whole lot of confidence in how they run their systems, but at no point has it been alleged that Ubquiti's firmware updates have been tampered with.
Just because not everyone installs security patches within a few months after they come out (it says the breach had been ongoing for two months) doesn't mean that therefore it doesn't apply to everyone. In the strict sense, indeed not everyone will have been compromised, but it totally applies to you in the sense that through business as usual (assuming that includes installing security updates), you can be compromised.
I have stuck with controller 5.13.32 rather than moving to 6.x just yet. It's an LTS version and I'm still waiting for the whinging to stop on the forums. I also watch the AP firmware and that has had some interesting times over the last few months. I've confirmed dodgy AP versions on my sites and backrevved and held accordingly.
I treat the whole thing the same way I do any other system. I come out in spots when people mention clouds and IT in the same sentence, so I have not knowingly enabled any cloudy integrations from my controller to UBNT. Specifically, I have not enabled "Remote Access".
Is it a case of you probably want to rebuild machines that have default usernames/passwords? Or is it more whatever can be seen in the Ubiquiti UI might be been accessed by third parties?
I mean, regardless, most probably, the answer to this is yes.
It is very, very easy to run vanilla Linux (or even OpenBSD) on their hardware. I do exactly this:
https://news.ycombinator.com/item?id=26645062
Octeons (not Octeon-TX) are amazing processors. Ubiquiti makes killer hardware. I hear their software is junk but wouldn't really know since I always erase it immediately after unboxing.
It's a big honking MIPS chip with firehose connections to the ethernet PHYs. Precisely the kind of device you want for a router.
What are the thruput measurements on OpenWRT when compared to ER-.. stock firmware, with hw accel or with DPI..?
I have an ER-4 to be able to use the entire wan connection, but on stock firmware I must disable DPI to enable hw acceleration (otherwise the thruput floors). I don't use DPI atm, so no big loss.
Can you utilize the hw accel in openWRT too?
Are we talking DPI at 1Gbps symmetric?
I have been in the position of implementing a client on a API I do not control. The owners of the servers (colleagues but in a different country) do not seem to know what logs are.
We get random failures from the server. I can pin down to the second when they occur (not closer because of network lag). I suspect that the server is failing under load, but the way I would find out is to... Read the logs.
My foreign colleagues do not respond to me, ghost me entirely, when I ask them to inspect the logs.
Perhaps it is a Windows/Azure thing?
Logs cost money to both collect and store. Not everyone is cheerfully burning through VC capital. Some people have budgets.
Speaking of log collection, simply dumping the logs into a central repository is the same as taking the garbage to the landfill. Collecting trash just results in a big collection of trash.
Extracting useful information from a huge pile of logs is non-trivial. You'd have to know at least one query language, probably several if you work on big enterprise systems. You'd have to know a bunch of esoteric things like how to convert the long decimal strings to a number so that you can interpret as any one of a dozen timestamp formats as an actual datetime in UTC, and then convert that to local timestamp so that you can tell when something actually happened. And so on.
All of this is merely a prerequisite for finding a specific instance of what you know is there.
You know what you'll never find in logs? Things you didn't know to look for! That's unfortunately about 90-99% of what you actually need to know, making logs typically about 1-10% as useful as you'd like.
Did I mention they cost money? Have you seen how many arms and legs Splunk charges these days? Why would you pay that much for something that is less than a tenth as useful as it could be?
The fundamental problem is that discipline doesn't scale. You can't expect a hundred thousand IT operations guys to all do everything all of the time, in spite of the non-technical finance guy holding on to the purse strings like he's gripping a life preserver after going overboard in a raging storm.
PS: I turned logging on extensively for a recent Azure project. Some logs cost more than the service they were monitoring. I mean sure, I could turn off the unnecessary logs, but how do I know ahead of time which ones will be necessary or not? I don't have a time machine! I can't go back and turn off the logs I won't need... later.
PPS: Have you noticed all logging companies charge by the gigabyte? What incentive do you imagine they have for improving the efficiency of the log transfer and storage formats?
If the would just look at logs they could answer so many questions that are costing a lot of money.
I am used to a Unix world, with logs as text files. They take up very little room, and it is easy to through out old ones (keeping logs for ever is foolish for a lot of reasons).
I am staggered that "I turned logging on extensively for a recent Azure project. Some logs cost more than the service they were monitoring." There is no way that this can be true unless there is some very very bad craziness going on. A real mindfuck
Even a hours worth of logs would of by now saved at least a week of developer time for the people I work with (my time, they pay for).
"Logs are typically off by default in most Enterprise software" That is probably true, I have no reason to doubt you and it fits with the other things I have witnessed, but there is a better way.
System Center Operations Manager and all derived products such as the various Azure Monitor and Azure Logs offerings have craziness going on.
For example, a typical metric is stored with a 300:1 write amplification because the database schema they use repeats the fully qualified machine name, counter name, and counter instance name per measurement. This prevents the collection of a useful set of metrics at a useful frequency.
Logs are similarly generated using suuuuuuper verbose JSON, capturing everything except the critical fields you actually wanted, and then stored uncompressed record-by-record, keeping the full field names for each and every row.
What incentive do you think they have to improve on the efficiency of the wire format or the storage format if they charge by the gigabyte?
If it is too much for production, turn it on for development servers.
My foreign friends seem to know not what that means
Are there good alternatives other than DIYs like PfSense/BSD?
At this point it wouldn't shock me if they announced subscription required for firmware updates and at that point screw it - might as well go Meraki or Ruckus and get actual support as well as a lot better performance.
(Yes, Apple exists.)
I don't see your point about Apple, unless you're being sarcastic for comedic effect. Apple release software with security flaws too. In fact a zero-click security vulnerability present in the Apple email client was posted on this very page only three days ago[1].
[1] https://www.cyberscoop.com/ios-zero-day-zerodium-high-supply...
Looking into Loki, Graphite, etc. But I’m a bit at a loss where to begin.
At least Apple seems to care about privacy and security, even if it is a self-serving marketing scheme.
Having APs that could be hardwired would be a requirement for me. The less wifi the better.
With the world of work at home exploding there seems to be a big missing link here.
I'm sitting with a big list of q's that I'm not sure I have a decent amount of time to answer. Does switching to pfsense/openwrt/something open source work with mesh? With ease of set up? Do enterprise brands offer anything worthwhile here? Do I have to regress to letting machines connect to unsecured networks?
I was going to press buy on the setup for some ubiquiti products till a couple of days ago :-(
I have sites that firmware hasn't been updated in years and doesn't need to. It always amuses me in one thread people bitch about MS, Windows 10 and forced updates then in threads like this I read people fessing to having auto updates enabled voluntarily. Ugh.
As for alternatives, Cisco's small business line is looking pretty reasonable. You can find used gear on ebay easily, you can upgrade firmware without a subscription or even needing an account (yes, I'm still talking about Cisco!) and while their management console is a bit weak, it's maturing. I think it will mature faster than UBNT who was strong out the gate but delivered nothing new or significant for almost 7 years now in routing, switching has never delivered layer 3 - especially useful for larger switches. APs seem to take longer to get bugs resolved in their firmware - but like I said if you only upgrade when you really need to that won't even effect you.
Clearly the market exists for what they’re offering. I am surprised at the serious lack of alternatives.
The APs are cloud managed only, but, personally, I trust HPE not to make a complete clown show of things the way UBNT has. But that's absolutely going to be a deal-breaker for a lot of people (especially with the way UBNT's now poisoned the well to a degree).
The big hole in that lineup is a gateway device. They just don't have anything comparable to the UDM (Pro). I'd be surprised if they don't eventually introduce something, though, given how the rest of the lineup seems pointed directly at the niche Ubiquiti is currently occupying.
That is unwise on the long-term, though. The technology is there so you don't have to trust anyone, so why do you choose to trust them when they're not offering cloudfree solutions?
Ubiquiti has a history of poor software releases that break things and now of trying to gloss over a serious security breach. I'm less worried about HPE in that regard.
The fact that doing anything, for example assigning a VLAN to a switch port, requires you to first setup a mongodb server on your machine before you can install the controller software tipped me off to the quality of what we had bought. The device also gets like 80°C while idle.
This controller software is now on isolated hardware, we trust the thing about as much as an old Android phone, and that was just from our impression as security people without knowing of any breach.
I see it as a good thing that other friends of $friend will be spared that recommendation after this news.
Unifi stuff is quite cheap for what you get for a simple reason: Each one does not need to run a webserver and all that stuff. This means that the pretty stuff has to run elsewhere. For a single site you can use a phone app and for multi site setups and MSPs you have the controllers.
The controller can be run on a Windows PC with a next next install or a Linux box with pretty minimal setup requirements.
It sounds like you might want to go the app route otherwise if you are an IT company (I own a 20 person one - so also small) then find the one screen doc with around 10 copy and paste instructions once you have say a small Debian or Ubuntu minimal installed. You could also run up a Win10 VM and install the Windows distro quite easily.
It doesn't have to be network equipment in the traditional sense: any old linux server will do, it's just that it needs to have a couple dozen network ports. Traffic can be limited to a gigabit per second between all the ports combined (no need for multi-gigabit backplanes or switch fabrics or what the correct term for that is). I'd almost buy a big USB hub and connect USB–Ethernet adapters, but that feels more hacky than core infrastructure is supposed to be.
Ended up swapping in an Archer C7 on OpenWRT with a LTE modem to ensure business continuity for the client while working with Meraki's abysmal support to get their router to work correctly.
This sounds like a 8 port poe switch. They get hot. However they also don’t seem to mind it.
It's not PoE and more than 8 ports.
But is about time Apple come back to Wireless and Router business.
Their lack of Wifi 6 across the range, and the security problems drive me to look at alternatives. Found the Netgear WAX610. Very happy with them.
Auttoiko?
The Reddit sub seems like they are actively trying to suppress discussion of this issue. There's some allegations of censorship on the sub, but I'm not seeing it... which might actually just be confirmation that they are censoring. I don't know.
Are there any particular examples of suppression or links to the allegations of censorship? The sub did recently begin allowing equipment picture posts again by popular demand. [2] I suppose an uncharitable interpretation is that that move was appeasement to distract from the breach issue.
[1] https://www.reddit.com/r/Ubiquiti/comments/mgm4o7/whistleblo...
[2] https://www.reddit.com/r/Ubiquiti/comments/mi0679/rule_chang...
Edit: Formatting