News for hackers. Stuff that matters.
Re:Google discloses another Windows security issue after dea... by yuhong on Thursday January 15, 2015 @07:24PM (#8896429)
Doubling the deadline to 180 days is probably reasonable IMO.
Re:Google discloses another Windows security issue after dea... by comboy on Thursday January 15, 2015 @07:58PM (#8896601)
Half a year? I wouldn't assume these guys at Google are the only ones discovering these vulnerabilities. Longer period won't improve Windows security. All it can do is keep better image of MS.
Re:Google discloses another Windows security issue after dea... by markcerqueira on Thursday January 15, 2015 @07:52PM (#8896568)
Might be, but I'm sure if it's important they would allocate resources to getting it fixed ASAP.

I doubt the fix for this and testing takes 90 days, or even 45 days.

Re:Google discloses another Windows security issue after dea... by rinon on Thursday January 15, 2015 @07:56PM (#8896584)
This apparently _does_ take that long, but should absolutely not.
Re:Google discloses another Windows security issue after dea... by higherpurpose on Thursday January 15, 2015 @08:06PM (#8896646)
Either Google is sending Microsoft bug reports like rapid-fire, and Microsoft has already fixed dozens of them that we haven't found out about - or for some strange reason, Microsoft didn't fix the only two bugs Google reported in the last 90 day period.

If that's the case, then either Microsoft forgot about them, or they carefully orchestrated a PR scandal against Google (wouldn't be the first time - like the time they built an unauthorized Youtube app that Google specifically told them not to build, and then notified the whole media about it, putting words in the reporters' mouths).

Re:Google discloses another Windows security issue after dea... by teraflop on Thursday January 15, 2015 @08:24PM (#8896719)
Well, Google has been sending Microsoft (and other vendors) lots of other bug reports: https://code.google.com/p/google-security-research/issues/li...

What I find interesting is that there are at least a couple of cases in which bugs were marked as being subject to the 90-day disclosure deadline, but not made publicly visible until days or weeks after the deadline had passed.

https://code.google.com/p/google-security-research/issues/de...

https://code.google.com/p/google-security-research/issues/de...

Re:Google discloses another Windows security issue after dea... by Amezarak on Friday January 16, 2015 @11:12AM (#8899749)
There are other bugs not reported by Google that Microsoft has to investigate and resolve as well. I doubt Google is the primary channel of security bug reports.
Re:Google discloses another Windows security issue after dea... by markcerqueira on Thursday January 15, 2015 @08:00PM (#8896613)
Right. If they extended it to 180 days, it would take them 200 days to fix it. 365 days ~> 400 days.
Re:Google discloses another Windows security issue after dea... by fname on Thursday January 15, 2015 @08:05PM (#8896641)
From the comments in the article

Microsoft informed us that a fix was planned for the January patches but has to be pulled due to compatibility issues. Therefore the fix is now expected in the February patches.

So, they met the deadline and fixed the vulnerability, but due to compatibility issues had to pull it before being released through Windows Update.

Re:Google discloses another Windows security issue after dea... by modeless on Thursday January 15, 2015 @08:27PM (#8896730)
... so they didn't meet the deadline. The deadline is for a released fix, not a theoretical fix that nobody can install in reality. They could, and should, speed up their process. But they won't, unless they get pressure from outside.
Re:Google discloses another Windows security issue after dea... by wideroots on Thursday January 15, 2015 @10:23PM (#8897092)
...yea it's easy to say when most people here should know how hard it is to ship any complicated system on multiple platforms. Actually, just making an app work for all major versions of Android could be a nightmare. And...what do you mean "they won't speed up their process"? Microsoft has released zero-day security bug fixes less than 90 days so many times before.
Re:Google discloses another Windows security issue after dea... by modeless on Thursday January 15, 2015 @10:34PM (#8897118)
I didn't say it was easy. I said Microsoft could do it, and that's true. Microsoft can do hard things, if it's a priority for them. Apparently they've judged that the damage isn't worth prioritizing these fixes higher.
Re:Google discloses another Windows security issue after dea... by Dylan16807 on Thursday January 15, 2015 @10:34PM (#8897120)
'making a program work' can easily be half your development time, or even more if you don't put on a lot of polish.

But this is bugfixing, not creating new programs. It shouldn't take this long.

Re:Google discloses another Windows security issue after dea... by amaks on Friday January 16, 2015 @02:03AM (#8897571)
Whatever time frame Google would come up with Microsoft would still find a reason to delay past it and publicly cry out loud.
Re:Google discloses another Windows security issue after dea... by lkbm on Friday January 16, 2015 @11:27AM (#8899841)
My understanding was that Microsoft had a specified timeline. Do you have reason to believe it's derived from Google's timeline?

If Microsoft says "100 days", saying "okay" instead of " no, 90" gives a timeline 100 days, not 101.

Re:Google discloses another Windows security issue after dea... by majc2 on Friday January 16, 2015 @02:30AM (#8897631)
This is conjecture and frankly nonsense. If the time frame was 5 years, would MS really find a reason to delay and to publicly cry out loud? No. The only org being unreasonable is big G.
Re:Google discloses another Windows security issue after dea... by higherpurpose on Thursday January 15, 2015 @08:09PM (#8896657)
Other companies fix such bugs in days.
Re:Google discloses another Windows security issue after dea... by uniformlyrandom on Thursday January 15, 2015 @08:12PM (#8896669)
Other companies do not develop enterprise operating systems.
Re:Google discloses another Windows security issue after dea... by wglb on Thursday January 15, 2015 @11:41PM (#8897296)
For one, IBM does, and has for some time. Others in the thread note that Red Hat and others do. Apple does iOs, which runs on far more devices than anything else mentiond in this thread.
Re:Google discloses another Windows security issue after dea... by travem on Friday January 16, 2015 @12:17AM (#8897362)
The total number of iPhones is not really relevant to the discussion, the number of iPhone models is. Testing a fix on an enumerable number of iPhone models in the wild (lets say iPhone 4, 4s, 5, 5c, 5s, 6, 6+) is nowhere near the complexity of testing Windows against the variety of devices that it would need to be validated against.
Re:Google discloses another Windows security issue after dea... by pgeorgi on Friday January 16, 2015 @04:30AM (#8897935)
Few of these issues are in driver level code, so the variety of devices doesn't play into that.

The most recent one is somewhere in the User Profile Service, which is about as far away from the hardware as possible. Shellshock didn't need testing on every possible hardware combination it runs on either, did it?

Re:Google discloses another Windows security issue after dea... by pan69 on Thursday January 15, 2015 @08:54PM (#8896825)
You mean like Redhat?
Re:Google discloses another Windows security issue after dea... by Karunamon on Thursday January 15, 2015 @09:06PM (#8896865)
Or Novell SuSe? Being "enterprisey" isn't an excuse for weak security.
Re:Google discloses another Windows security issue after dea... by Igglyboo on Thursday January 15, 2015 @10:14PM (#8897070)
RedHat runs on no where near as many devices as Windows does.
Re:Google discloses another Windows security issue after dea... by danieldk on Friday January 16, 2015 @02:22AM (#8897611)
Red Hat and CentOS run on many servers, which arguably have the highest economic impact when they are exploited (or when a 'fix' leads to problems).
Re:Google discloses another Windows security issue after dea... by pan69 on Thursday January 15, 2015 @11:26PM (#8897255)
Since Redhat is a distribution of Linux, how many Android installs are there?
Re:Google discloses another Windows security issue after dea... by tedunangst on Friday January 16, 2015 @12:25AM (#8897384)
? Nobody is running redhat on their android phone.
Re:Google discloses another Windows security issue after dea... by pan69 on Friday January 16, 2015 @04:56AM (#8898001)
That's correct. They run Linux, like Redhat.
Re:Google discloses another Windows security issue after dea... by Igglyboo on Friday January 16, 2015 @09:47AM (#8899163)
How is that a fair comparison?

RedHat is POSIX compliant so why don't you just lump in every POSIX compliant device ever made? /s

Re:Google discloses another Windows security issue after dea... by oldmanjay on Friday January 16, 2015 @11:07AM (#8899719)
Do you honestly feel like that is anything but disingenuous?
Re:Google discloses another Windows security issue after dea... by beedogs on Thursday January 15, 2015 @08:20PM (#8896703)
Yep, Microsoft's the only one.
Re:Google discloses another Windows security issue after dea... by amaks on Friday January 16, 2015 @02:06AM (#8897582)
What is it, 1999? Welcome to the real world, Neo
Re:Google discloses another Windows security issue after dea... by SolarNet on Thursday January 15, 2015 @08:21PM (#8896708)
How is that a reasonable excuse? If they have so much money their operating system should be fixed faster, not slower, than other operating systems.
Re:Google discloses another Windows security issue after dea... by dragonwriter on Friday January 16, 2015 @12:47PM (#8900343)
More resources should make the number of fixes possible per year greater, but it may not substantially reduce the time from notice to fix any single issue (and may, because of organizational overhead involved, sometimes increase the time for particular fixes over an organization with fewer total resources.)

Maintaining code is not a trivially parallelizable function.

Re:Google discloses another Windows security issue after dea... by SolarNet on Friday January 16, 2015 @08:07PM (#8902862)
> Maintaining code is not a trivially parallelizable function.

Yes, I know this, thank you.

But we are talking about billions of dollars vs. millions of dollars (for Linux / BSD). We are talking multiple orders of magnitude(!) more money. I realize there isn't a Silver Bullet, but the fact that what we have heard coming out of Microsoft about they're management practices year after year is ABYSMAL, it is not an excuse. Especially when people who are working for free, with no/little organizational support, can beat them at releasing security fixes.

> because of organizational overhead involved

So maybe they should fix it? How is their incompetence at running an organization a valid excuse? If it was a problem they cared about they would be researching how developers and teams of developers perform best, how best to organize code, etc. Instead they used stacked teams for years on end. I have no sympathy.

If it's as serious problem maybe they should stop making new operating system features and devote more resources to fixing, cleaning up, depreciating, etc. the ones they already have?

They are making business decisions, and their ineptitude at security is a result of them. There are no excuses of "they are the only one's doing X" for "they are bad at doing Y when they do X" when they are promising Y!

Re:Google discloses another Windows security issue after dea... by nkozyra on Thursday January 15, 2015 @10:19PM (#8897079)
More money (or resources) = faster solutions is a pretty common fallacy.

Often the size, scope and wealth of resources induces an increasingly slower response to such things.

Re:Google discloses another Windows security issue after dea... by Dylan16807 on Thursday January 15, 2015 @10:40PM (#8897133)
How is it a fallacy? Because management is incompetent? If your budget goes from 1M to 10M even a child could show you how to spend 1M and throw the rest into a big fire or something. Maybe run two agile teams at 1M each.
Re:Google discloses another Windows security issue after dea... by Philadelphia on Friday January 16, 2015 @12:44PM (#8900322)
Do people not read The Mythical Man Month anymore?
Re:Google discloses another Windows security issue after dea... by SolarNet on Friday January 16, 2015 @08:33PM (#8902929)
Yea, but that doesn't mean you still don't get some additional speed out of hiring more developers, especially when correctly organized, with sane management policies, and good software development practices.

The point is that Microsoft has the money to hire 100x more developers than the other guys, they should at least be well organized enough to deploy a part of that man power effectively.

Lets put it this way, there are 7 companies out there (at least) maintaining various different distributions of UNIX that can patch quickly, why can't Microsoft patch their 7 operating systems as quickly? From my view what you are saying is that because Microsoft is a monolithic company with 7 code bases it is somehow harder than 7 companies with 1 code base each? How does that track? Especially when Microsoft has a 100x more money than each of those other companies.

I'm not saying there is such a thing as a man-month. I'm saying there are ways to organize production, teams, and software so that people can provide more work than in poorly managed environments.

Re:Google discloses another Windows security issue after dea... by anon1385 on Thursday January 15, 2015 @10:55PM (#8897180)
I honestly can't tell if you are attempting parody or being serious.
Re:Google discloses another Windows security issue after dea... by Dylan16807 on Friday January 16, 2015 @12:14AM (#8897354)
I'm perfectly serious. Perhaps I misread the comment I am replying to.

Flat out 'more money to fix the problem' should never make things slower. Worst case you can ignore the money.

Even if it's too late to add people for project X, you should be able to use the money for something to improve productivity on project X+3.

If I'm wrong about something please explain.

Re:Google discloses another Windows security issue after dea... by anon1385 on Friday January 16, 2015 @03:46AM (#8897789)
Well if you were being serious it sounds like you really need to read this book https://en.wikipedia.org/wiki/Mythical_man_month
Re:Google discloses another Windows security issue after dea... by Dylan16807 on Friday January 16, 2015 @03:57AM (#8897822)
I am aware of that book. I considered referencing it in my earlier comments.

I don't know how I can my my point more clear.

If a manager shoves in more workers and slows things down, they are failing at their job.

They are worse than useless.

Because someone useless would take the extra budget, not hire anyone, and not slow down the work. Perhaps they would waste it in vegas.

I am saying nothing that contradicts that book. Just two simple points:

1. More resources only slow down a project when they are misused. They are never inherently bad.

2. It's not even hard to speed up work on security bugs, because each bugfix is a different project and can have its own dedicated team.

Please actually point out something I said that was wrong, instead of making vague references.

Re:Google discloses another Windows security issue after dea... by nkozyra on Friday January 16, 2015 @09:44AM (#8899148)
My point wasn't that more money itself induces potential slowness, but added infrastructure & scope that surround it (not necessarily even in the same department) often can.

Ignoring more money is pretty unlikely to be an option as a whole, and inefficiencies generally cascade down to some extent.

Re:Google discloses another Windows security issue after dea... by Dylan16807 on Friday January 16, 2015 @12:56PM (#8900399)
Other departments matter in some ways, but bugfixing can be self-contained and mostly avoid slowdowns.

But even more important is that these outside slowdown effects are pretty minor. If this was software development then you might have no recourse and you'd be somewhat slower overall. But this is handling many many independent projects. You can hire more teams without having man-month problems, and then handle bugs efficiently.

>Ignoring more money is pretty unlikely to be an option as a whole, and inefficiencies generally cascade down to some extent.

Again, I blame management. A nice sturdy cardboard box as a manager is impervious to social effects from other departments, and it can soak up extra cash too.

I expect anyone being paid to manage to do a better job than a box. Not to go along with the flow uncritically.