News for hackers. Stuff that matters.
Re:Skype can't fix a nasty security bug without a massive co... by cptskippy on Tuesday February 13, 2018 @08:20AM (#16366887)
> A couple of lines to fix the bug, in theory

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.

Re:Skype can't fix a nasty security bug without a massive co... by vorpalhex on Tuesday February 13, 2018 @09:23AM (#16367290)
> No code reviews, security review, integration testing, quality assurance testing, compatibility testing, or validation.

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.

Re:Skype can't fix a nasty security bug without a massive co... by latencyloser on Tuesday February 13, 2018 @09:44AM (#16367448)
As a former Microsoft employee, my experience was that the longer a product was around, the harder it was to figure out who understood any part of it well enough to change something.

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.

Re:Skype can't fix a nasty security bug without a massive co... by patcheudor on Tuesday February 13, 2018 @10:02AM (#16367593)
Microsoft is still actively patching Skype. Here's an example of them patching what sounds like a similar DLL flaw just last year:

https://www.cvedetails.com/cve/CVE-2017-6517/

Re:Skype can't fix a nasty security bug without a massive co... by user5994461 on Tuesday February 13, 2018 @02:37PM (#16370013)
And don't forget that the product work as expected in most cases and many changes are not justified.

The bike shed won't get painted to a new color just because a the new middle manager asked for it.

Re:Skype can't fix a nasty security bug without a massive co... by BoorishBears on Tuesday February 13, 2018 @09:37AM (#16367386)
Ironically I would comment exactly what you did with, but the roles reversed:

“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.”

Re:Skype can't fix a nasty security bug without a massive co... by cptskippy on Tuesday February 13, 2018 @11:36AM (#16368407)
I feel like you've got those reversed. In small startup the bug fix would be deployed to production before it's committed to source control.

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.

Re:Skype can't fix a nasty security bug without a massive co... by pizza234 on Tuesday February 13, 2018 @10:33AM (#16367861)
> 24 - 72 hours for a fairly critical and relatively easily solved security bug

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.

Re:Skype can't fix a nasty security bug without a massive co... by Quarrelsome on Tuesday February 13, 2018 @09:36AM (#16367381)
I'm guessing if they fix this bug the simple way they break the entire product and the proper way is many months of work (entire eco-system restructure).
Re:Skype can't fix a nasty security bug without a massive co... by dspillett on Tuesday February 13, 2018 @08:55AM (#16367093)
> code reviews, security review, integration testing, quality assurance testing, compatibility testing,

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.

Re:Skype can't fix a nasty security bug without a massive co... by cptskippy on Tuesday February 13, 2018 @11:45AM (#16368508)
I wasn't defending Microsoft, just responding to the trivialization the op made.

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.

Re:Skype can't fix a nasty security bug without a massive co... by enzanki_ars on Tuesday February 13, 2018 @09:12AM (#16367205)
As others have already noted, yes, it’s a pain ship fixes in a company setting, and I fully understand that. On the oth r hand, 4 months for no fix is inexcusable.
Re:Skype can't fix a nasty security bug without a massive co... by sp332 on Tuesday February 13, 2018 @10:50AM (#16368014)
I think this is a response to the headline, which specifically mentions a "massive code rewrite".
Re:Skype can't fix a nasty security bug without a massive co... by mosselman on Tuesday February 13, 2018 @08:37AM (#16366982)
Luckily 'they don't care about security at all'. They just looked into it for fun when the report came in.
Re:Skype can't fix a nasty security bug without a massive co... by sodapopcan on Tuesday February 13, 2018 @11:12AM (#16368206)
"Can't you just..."
Re:Skype can't fix a nasty security bug without a massive co... by cptskippy on Tuesday February 13, 2018 @12:17PM (#16368795)
Like nails on a chalkboard.
Re:Skype can't fix a nasty security bug without a massive co... by corporatocracy on Tuesday February 13, 2018 @12:06PM (#16368719)
Bureaucracy is hard, but so is losing clients or getting sued by an enterprise customer for negligence in handling a known security hole in a timely fashion. Corporations can become extremely agile when there's money on the line.
Re:Skype can't fix a nasty security bug without a massive co... by orblivion on Tuesday February 13, 2018 @10:34AM (#16367871)
I enjoyed your retort, but I'll note that it being "just a couple lines of code" at least should imply that this is no harder than other security fixes, which somehow do make their way out faster than main releases.