How IKEA Patched Shellshock
jones_supa writes: Magnus Glantz, IT manager at IKEA, revealed that the Swedish furniture retailer has more than 3,500 Red Hat Enterprise Linux servers. With Shellshock, every single one of those servers needed to be patched to limit the risk of exploitation. So how did IKEA patch all those servers? Glantz showed a simple one-line Linux command and then jokingly walked away from the podium stating "That's it, thanks for coming." On a more serious note, he said that it took approximately two and half hours to upgrade their infrastructure to defend against Shellshock. The key was having a consistent approach to system management, which begins with a well-defined Standard Operating Environment (SOE). Additionally, Glantz has defined a lifecycle management plan that describes the lifecycle of how Linux will be used at Ikea for the next seven years.
I imagine it was sudo rm -rf /, but I could be way off.
Let's save ourselves from unnecessary clickbait.
They were only able to do it because they already had an affordable, high quality krampfor on hand. The whole thing would have fallen apart if not for that.
I'm trying to teach myself to set people on fire with my mind... Is it hot in here?
I was there. It was said in a very joking manner. From the moment he started he showed his sense of humour.
In fact, his whole presentation was funny, amusing and had some good information.
The idea that he showed a one line command to patch wasn't the biggest shock of the talk. (Sorry, I don't recall the command.) It was the fact that he patches the 3,500 servers ONCE A MONTH. Straight into production. This caused some questions and discussion.
FTFA, "One of the potential challenges of constantly updating servers is the risk that applications break when new server operating system software is loaded. Glantz, however, isn't worried and noted that RHEL offers the promise of Application Binary Interface (ABI) compatibility across updates." The rest of his reasoning, and another amusing moment, is described at the end of the article.
Vip
./patch
but the interesting bit was the getting to that, yeah.
The moment would have been perfect if he'd just dropped the mic.
You are welcome on my lawn.
From the article the grandparent obviously did not read "Glantz showed a simple one-line Linux command and then jokingly walked away from the podium stating "That's it, thanks for coming," as the audience erupted into boisterous applause.". So in fact top notch people skills.
Chaos - everything, everywhere, everywhen
if its anything like my general Ikea experience, im sure the security ops team was handed a cardboard box labelled "Schelli schocc" with a 7 page manual full of bloated looking stick figures and a tiny hex wrench. they were then left to figure it out over a long night of busted knuckles and impromptu invented curse words. by dawn, either the prod environement passed a nessus scan or theyd built a bed...or both.
Good people go to bed earlier.
So he is using some sort of configuration management. I modified and tested a puppet manifest and then deployed to to our production puppet server. Over the next 30 minutes I had updated over 1000 machines.
I like Apple propaganda. It's much better than that awful Windoze propaganda.
By making the customers do most of it themselves.
Table-ized A.I.
Man holding hammer demonstrates ease of driving a nail into wood. Thousands holding screwdrivers are amazed.
was is "chsh -s dash www_data"?
I like Apple propaganda. And hypnotoad.
If tugboats were bigger, they could be the boats that tugboats tug.
So, what you are saying is I haven't bothered to read anything, or look at anything, but here is my completely irrelevant opinion?
Man, this place used to be something...
It was in Perl:
./update-all-3500-servers-at-once.pl
one line.
Slashdot, fix the reply notifications... You won't get away with it...
the article did not say what it was , but anyone with redhat experience already KNOWS this ...
as root do
" yum update "
two words , that is it
"I don't pitch OpenSUSE Linux to my friends, i let Microsoft do it for me
Why use a onelinerand what is in that oneliner? /usr/local/bin/IKEA-Update` is also a onliner.
I would use a script or a program to run it. Thta can be run as a 'oneliner'.
`sh
It is also not importand what is in that oneliner. Is it the standard update, or does it contain their own command with 360 different programs in it, subroutines and numerous other points of failure.
Don't fight for your country, if your country does not fight for you.
Professionals look and dress like professionals. If you insist on wearing grubby t-shirts and faded jeans at work don't be surprised if you're always kept out of the loop, never ever considered for promotion and ultimately the first to be let go when downsizing.
OMG, IKEA uses RH enterprise support for managing their servers... Slash *used* to be news for nerds. I have used scripts, after that RunDeck and now Ansible + Debian. And they do not need a subscription and better yet, are *distribution agnostic*.
Well, I sure as hell wouldn't run that on all my production systems without a wee bit of testing first...
Oh arse
# find /placewithtaxes -iregex ".*\(money\|geld\|argent\).*" -exec mv '{}' /offshore \;
Confucius say, "Find worm in apple - bad. Find half a worm - worse."
Sad but true. If you want to get taken seriously you need to put your custom on.
Oh, but there is of course. We upgraded our 3k servers easily because we have a RH enterprise account. ;) The only interesting bit was we have all the procedure documented, but then they contradicted himselves and say the man goes full comando and updates everything live without testing. Apart from that, it is drivel.
the man goes full comando and updates everything live without testing.
That's an assumption on your part. Sure, it may be implied, but isn't confirmed. I've seen places large enough that their OS provider would test on their behalf. So he can claim "no testing" and the answer is it was tested. Well tested. I've seen it done before.
Learn to love Alaska
If the heyday of Y2K remediation, I helped set up a push of a SOE to 275,000 distributed PCs in a weekend. It went off without a hitch. Management was happy, but the cries of thousands of employees who lost all their personal files and documents were ignored.
If you are willing to be heavy handed and brutal, you can accomplish miracles. Surely there is no news in that.
Any chance for a link to the video?
Free Pie! The Pie is Also Evil!
You have obviously never worked with your average big corp windows admin.
No sir I dont like it.
https://www.youtube.com/watch?...
-- Red Hat security in a post-Shellshock world - 2015 Red Hat Summit
With 3500 servers, its probably worth setting up your own package archive. Then the command to patch all the servers would most likely be pushing your tested and approved package to your local archive to be pulled by all the production servers on their next poll for updates.
yes, nothing like running thousands of machine without support from the OS devs. lot's of fun...
"The key was having a consistent approach to system management, which begins with a well-defined Standard Operating Environment (SOE). Additionally, Glantz has defined a lifecycle management plan that describes the lifecycle of how Linux will be used at Ikea for the next seven years."
And why I regard DevOps as a disaster in the making. While "DevOps" isn't bad for small companies, like ones I've worked for, where you 'wear many hats' or a rapidly moving R and D environment it is very dangerous in a real production environment. Of course clueless management will use "DevOps" as a cost cutting measure and then after the disaster fire everyone and outsource everything, often with even worse results, for what is essentially bad management.
But hey, they were Agile, Nimble, flexible, idiot sourced, and buzz word compliant.
putting the 'B' in LGBTQ+
I would've "bothered", but the talk isn't available online, apparently. So by your logic, nobody should comment anything here. Or /. shouldn't link to articles that are essentially just teasers.
Go to satellite, click on errata, set it to update. If you have it set up for communications Ikea would probably have been done in a half hour at the most. Otherwise, when they check in. Up to 4 hours later.
What's the big deal?
That article in the link is one of the worst I have ever read. No details are given about how they patched their systems. I'm assuming (like others) that they used "yum" to install the update. But no details are given about exactly what they did or how they handled it. Don't waste your time with the link.