If this was a small startup, I can absolutely see those being hurdles. This is Microsoft on a product they've had for 20+ years that is a major part of their platform - those things should be mostly automated and well oiled machines.
A mature enterprise level company has no excuses for "QA is hard!" or "We can't validate patches!" for a product they sell. I don't expect them to get this out in ten minutes, but they should be able to manage a patch in 24 - 72 hours for a fairly critical and relatively easily solved security bug.
I would guess I averaged about 10 lines a month on my project that had been around for decades. Making even slight tweaks required dozens of meetings, design discussions, functional and performance testing, etc. etc. It took an eternity.
The bike shed won't get painted to a new color just because a the new middle manager asked for it.
“If this was a small startup I couldn’t see those being hurdles but at a behemoth like MS with an almost 2 decade old product I can.”
In a large enterprise the process isn't too hard, it's just complicated.
I was neither justifying or admonishing MS for this issue, I was just responding to a gross trivialization of the process that I found offensive.
Let's see. How many microsoft employees would it take to change a lightbulb? ;-)
https://blogs.msdn.microsoft.com/ericlippert/2003/10/28/how-...
Highlight:
> That initial five minutes of dev time translates into many person-weeks of work and enormous costs
This is just to add an interesting article on top of the sibling comment from the MS employee; nothing's easy in the engineering of a large product.
Valid counter-criticism of the "just a couple of lines of code" line generally, but four months is a long time since disclosure and that is a lot of morning coffees.
According to the article, Microsoft is dedicating resources to a new client which won't exhibit the flaw.
So I guess that means either they examined the flaw and determined it wasn't a high enough risk to warrant patching, or they don't care. Dealer's choice I guess.
Maybe the number of people using Skype these days is insignificant? I tried to use it about a year ago and noped the hell away after 5 minutes.
Yes that's all it takes. No code reviews, security review, integration testing, quality assurance testing, compatibility testing, or validation. None of the work on the installer or updater. No release notes or other communication to the community.
Just a couple lines of code. Easily done before morning coffee.