Against whom Ubiquiti has apparently just filed a lawsuit.
As a customer, this is the email that I got and didn't catch at the time. "Sooo, just FYI, there's been an attack against our systems with DB. Maybe consider changing your password?" Hugs and puppies, Ubiquiti.
Yeah, the fact that credentials were not invalidated and immediately reset means that this section is complete bullshit.
It's an example of "Ubiquiti and other companies disregard(ing) their customers’ online security" because that's exactly what they did. That's not clickbait.
That's funny, "we found a backdoor in our systems" in the filing is in no way the tone that your email struck, @Ubiquiti. What's the deal with that?
Yeah, sorry. As one of those quaint things called "a paying customer," I assure you that the risk factor here is not your competition figuring out the secret to making space heaters reboot.
Uh.... you *did* downplay the severity here. Whether it was an insider or an outsider isn't really the relevant part of the story, so much as "you failed to secure the data that I had entrusted to you."
Oh come on @ubiquiti. Even Krebs's story and the claims therein didn't shine as much light on your failings as your own lawsuit filing is doing. My god...
Welp @briankrebs is getting pride of place in my RSS reader for the next decade based upon this.
And at this point we've only seen the suit. Krebs hasn't filed a response yet!
Ubiquiti seems awfully convinced that "it wasn't an outside attacker, we just suck at detecting insider threats" is a far stronger position than it is here in reality.
I don't care who pushed you or what you were carrying; everyone saw you eat shit down the stairs.
The meat of the accusation is that the inside attacker was @briankrebs's source. I really fail to see the problem if that's true; that guy kinda seems like one of the more competent people running the store over at @Ubiquiti right about now.
Think to all of the books you've read, the movies you've seen.
When someone sues a journalist, how often are they presented as "the good guys?"
It appears @ubiquiti is represented by @clarelockellp, who proudly boasts about... suing journalists. Genius PR move, folks.
I eagerly await being added to the lawsuit because I have enough Twitter followers to look like media if you squint hard enough, and I too have said things about you on the internet that are likely to cause you some grief, @ubiquiti.
Be sure you get the rest of the kids saying mean things about you on the playground too, you poor delicate $18B publicly traded company.
"Let me put it this way,” begins someone a bit more up to speed on my shenanigans, with the unmistakable tone of someone teeing up a long drive down the fairway of hopelessness.
“He made an insulting video about the founder of the world's largest law firm (Oracle / ‘Kirkland Ellison’).
Then he got the @nytimes to print that 'nobody likes said founder.'
And *THEN* he got that company to *PAY HIM FOR ADVICE*.”
I mean, there’s a few reasons that my @LastWeekinAWS newsletter (to which you should subscribe!) has 30k subscribers, and one of them is because it’s fairly rare to find cloud-related news roundups that are entertainingly insulting to giant companies.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
I'm at the AWS Summit in NYC, where I believe that nicknames are for friends--and Gennifer Artificial Intelligence is no friend of mine.
Good morning.
Thirsty much?
A game / challenge at the AWS Startups booth: how long can an AWS employee go without mentioning GenAI? Someone just made it all the way to one minute, ten seconds!
Okay. Let's do Networking Specialty. Practice question 1:
Correct answer is B.
"Wrong!" says the answer key, "it's B because network load balancers don't support client IP preservation."
Except that they do. They absolutely do. They have for the past year. I'm just a boy, standing in front of an AWS Cert team, asking them to do their damn jobs.
Today's cloud marketing story is called "The Tale of Hot Rebecca," and is a truthful recounting of dinner last night.
Strap in; it's a fun ride.
Back in my early 20s, I had a number of friends / acquaintances in my (primarily Jewish) social circle named "Rebecca." It was kind of a problem.
("Can't we spray for them?"
"…not since the 1940s.")
So every Rebecca got an adjective, much like the seven dwarves. One of them asked me once what her adjective was, and I responded in a fit of unadulterated honesty, "you're Hot Rebecca" because honestly? Damn.
Made it to the #GoogleCloudNext keynote seating finally. Let's see how this goes now that the world is starting to wake up to a "much of the AI hype is unwarranted" reality.
Boeing: "HOW ARE THEY DOING IT?!"
Airbus: "We bought a torque wrench?"
Boeing: "No, how are you being a featured customer testimonial at #GoogleCloudNext?"
Airbus: "Oh, that? We made a strategic decision to not be walking poster children for corporate negligence."
And now, some DevOps / SRE / Sysadmin / Ops / ENOUGH already tips I learned from early in my career--brought to us by our friends at Chex™ Mix. All of these are great ideas that you should implement immediately...
DNS is notoriously unreliable, so use configuration management to sync all of the servers' /etc/hosts files. Boom, no more single point of failure.
Future-proofing is an early optimization, so don't do it. Every network should be a /24 because that's how developers think. I mean come on, what are the odds you'll ever have more than 253 hosts in a network?
And the Amazon earnings are out for Q4. A miss on @awscloud revenue by $20 million because analysts didn't expect one of you to turn off a single Managed NAT Gateway.
Let's explore deeper into their press release.
For 2023, AWS sold $90.8 billion of services, most of which were oversized EC2 instances because you all refuse to believe Compute Optimizer when it tells you there are savings to be had if you're just a smidgen more reasonable.
Word frequency in the earnings release:
Customer: 87
Employee: 11
Generative: 16
Cloud: 24
Serverless: 3
DynamoDB: 2
Union: 0