Page 1 of 4 1234 LastLast
Results 1 to 16 of 50

Thread: Microsoft hits back after Google publicises Windows bug

  1. #1
    HEXUS.admin
    Join Date
    Apr 2005
    Posts
    29,106
    Thanks
    0
    Thanked
    1,869 times in 642 posts

    Microsoft hits back after Google publicises Windows bug

    Google didn't want to wait until the bug fix was distributed today, Patch Tuesday.
    Read more.

  2. #2
    Member
    Join Date
    Jul 2013
    Posts
    129
    Thanks
    9
    Thanked
    3 times in 3 posts
    • sirtrouserpress's system
      • CPU:
      • I7-5600U
      • Memory:
      • 20GB DDR3
      • Storage:
      • 128GB PCI-e SSD
      • Graphics card(s):
      • NVIDIA GeForce 940M
      • Operating System:
      • Xubuntu/Windows 10

    Re: Microsoft hits back after Google publicises Windows bug

    As I see it, if Google didn't realise these bugs every once in a while, businesses like Microsoft would have no incentive to patch it quickly. So to many respects Google still is working on the side of Microsoft by reminding them to do their jobs...

  3. #3
    Senior Member
    Join Date
    Jun 2004
    Location
    Kingdom of Fife (Scotland)
    Posts
    4,991
    Thanks
    393
    Thanked
    220 times in 190 posts
    • crossy's system
      • Motherboard:
      • ASUS Sabertooth X99
      • CPU:
      • Intel 5830k / Noctua NH-D15
      • Memory:
      • 32GB Crucial Ballistix DDR4
      • Storage:
      • 500GB Samsung 850Pro NVMe, 1TB Samsung 850EVO SSD, 1TB Seagate SSHD, 2TB WD Green, 8TB Seagate
      • Graphics card(s):
      • Asus Strix GTX970OC
      • PSU:
      • Corsair AX750 (modular)
      • Case:
      • Coolermaster HAF932 (with wheels)
      • Operating System:
      • Windows 10 Pro 64bit, Ubuntu 16.04LTS
      • Monitor(s):
      • LG Flattron W2361V
      • Internet:
      • VirginMedia 200Mb

    Re: Microsoft hits back after Google publicises Windows bug

    In response to Google's lack of flexibility, Microsoft exec Chris Betz wrote in a blog on the company's site on Sunday "We asked Google to work with us to protect customers by withholding details until Tuesday, Jan. 13, when we will be releasing a fix. Although following through keeps to Google’s announced timeline for disclosure, the decision feels less like principles and more like a 'gotcha,' with customers the ones who may suffer as a result." Betz added "What's right for Google is not always right for customers. We urge Google to make protection of customers our collective primary goal."

    Opinion is split between whether Google was right to publicise the bug on principal, or it should have had some flexibility to help protect Windows users. The BBC has quotes from supporters on both sides of the argument but at the time of writing Google is yet to officially respond to the Microsoft TechNet blog post by Chris Betz.

    What do readers think about Google Project Zero and its disclosure of the unpatched bug in this case?
    If the above is an accurate summation of what occurred (and the BBC and other sites seem to be telling the same story) then I'm going to side with Microsoft in this case. Sure, I'm happy that Google's Project Zero folks are trying to keep developers "honest" wrt security. But to release details of the flaw when they'd been told that it was going to be patched in two days time seems vindictive.

    On the other hand I have no problem with the idea that Google turn around and says "sure, you're patching on the 13. Okay we'll release details on the 15th", as that would have been the sensible thing to do since it'd be giving Microsoft a chance to do the correct thing and patch the flaw.

    Career status: still enjoying my new career in DevOps, but it's keeping me busy...

  4. #4
    Registered User
    Join Date
    Sep 2014
    Posts
    2
    Thanks
    0
    Thanked
    0 times in 0 posts

    Re: Microsoft hits back after Google publicises Windows bug

    I think we are forgetting that Microsoft actually had two releases prior to this one, and they could maybe had urged a bit more to have it fixed with in the given time by google ?
    I'm surely standing with google on this one. two patch cycles is a lot, yea it takes time to make the fix, but should not take 50+ days.

  5. #5
    Senior Member
    Join Date
    Sep 2012
    Location
    North West, UK
    Posts
    508
    Thanks
    22
    Thanked
    34 times in 28 posts
    • big_hairy_rob's system
      • Motherboard:
      • ASUS Z170-A
      • CPU:
      • Intel I5 6600k
      • Memory:
      • 16GB DDR4 Corsair Vengence (3000mhz)
      • Storage:
      • Samsung 850 500GB, WD Blue 1TB
      • Graphics card(s):
      • MSI Radeon R9 275
      • PSU:
      • EVGA 550W (80 plus Gold)
      • Case:
      • Fractal Design S (Windowed)
      • Operating System:
      • Windows 10 64.
      • Monitor(s):
      • Iiyama ProLite E24B3HS 24", LG Flatron L1950SQ19"
      • Internet:
      • Plusnet (infinity)

    Re: Microsoft hits back after Google publicises Windows bug

    Microsoft knew the deadline of 90 days and if Tuesday was such an issue, why wasn’t it released on the Tuesday prior to the deadline. Sure it may look vindictive of Google, but what about any hypocrisy by allowing a giant company such as Microsoft to dictate when it can release its statements, while smaller companies would not be given that chance. By sticking to their guns Google at least remain honest to the terms that they set and as a result I side with them.

  6. #6
    Token 'murican GuidoLS's Avatar
    Join Date
    Apr 2013
    Location
    North Carolina
    Posts
    806
    Thanks
    54
    Thanked
    110 times in 78 posts
    • GuidoLS's system
      • Motherboard:
      • Asus P5Q Pro
      • CPU:
      • C2Q 9550 stock
      • Memory:
      • 8gb Corsair
      • Storage:
      • 2x1tb Hitachi 7200's, WD Velociraptor 320gb primary
      • Graphics card(s):
      • nVidia 9800GT
      • PSU:
      • Corsair 750w
      • Case:
      • Antec 900
      • Operating System:
      • Win10/Slackware Linux dual box
      • Monitor(s):
      • Viewsonic 24" 1920x1080
      • Internet:
      • AT&T U-Verse 12mb

    Re: Microsoft hits back after Google publicises Windows bug

    Meanwhile, Google is ignoring security flaws in Jelly Bean (Android 4.3)...

    http://blogs.wsj.com/digits/2015/01/12/google-not-fixing-some-old-android-bugs/

    Considering that Jelly Bean *still* powers roughly 2/3rds of all Android devices worldwide, you'd think they would take care of their business before calling out someone else - especially when they'd already been in contact with Microsoft, and had been given a repair date. So no, Google wasn't being honest, nor good guys. They were being hypocrites of the worst kind.
    Esse Quam Videri
    Out on the road today I saw a Black Flag Sticker on a Cadillac...


  7. #7
    Senior Member
    Join Date
    Dec 2013
    Posts
    2,960
    Thanks
    408
    Thanked
    370 times in 256 posts

    Re: Microsoft hits back after Google publicises Windows bug

    Didn't Google stop support of Jelly Bean (Android 4.3) back in July 2013 ?

  8. #8
    Registered+
    Join Date
    Jan 2009
    Posts
    50
    Thanks
    0
    Thanked
    5 times in 4 posts

    Re: Microsoft hits back after Google publicises Windows bug

    Quote Originally Posted by GuidoLS View Post
    Meanwhile, Google is ignoring security flaws in Jelly Bean (Android 4.3)...
    not forgetting this one, stopping me from using a nexus 4 phone to make/receive calls (no mic or speaker)...

    https://productforums.google.com/forum/#!topic/nexus/j74JlShhihc

  9. #9
    Senior Member
    Join Date
    Sep 2013
    Location
    Europe
    Posts
    573
    Thanks
    42
    Thanked
    13 times in 13 posts
    • DemonHighwayman's system
      • Motherboard:
      • MSI Z97I Gaming
      • CPU:
      • Intel i7 4790K
      • Memory:
      • 16Gb 2.4Ghz Kingston Beast
      • Storage:
      • 256 Gb Samsung 850 Pro (Main), 4TB Toshiba X300 (games), 2TB External TV/Films HDD
      • Graphics card(s):
      • KFA2 RTX 2070 EXOC
      • PSU:
      • Coolermaster Real Power M700
      • Case:
      • Bitfenix Prodigy
      • Operating System:
      • Windows 10
      • Monitor(s):
      • Asus PB278Q
      • Internet:
      • Yes most of the time

    Re: Microsoft hits back after Google publicises Windows bug

    I think Google should have been a bit more flexible maybe granting up to a week extra before going public, however MS did have plenty of time to get the bug fixed. Anyway i'd say to anyone who is affected to hold off a week anyway before they update, google around to see if the new patch causes any problems, which every update they did last year did !

  10. #10
    Senior Member
    Join Date
    Aug 2006
    Posts
    1,399
    Thanks
    8
    Thanked
    68 times in 60 posts

    Re: Microsoft hits back after Google publicises Windows bug

    Well I'm in the Microsoft camp on this one... the only people who this actually benefits from Google releasing the info are the people that are out to use the security flaw. From what I read it has quite a large system wide effect so the testing etc likely took longer than say fixing a simple bug.

    Yes they had 90 days to deal with the issue but we had Christmas and New Years in that period so allowing a couple of days wouldn't have hurt anyone, except Google who wouldn't have been able to get 'one over' on Microsoft.

    I've been growing more and more anti google of late due to decisions they keep making to try and 'force' us to use their services and this just seems to fall in that sort of approach.

    As to Android support from Google, there's support and then there's fixing security issues on arguably their most popular os/version etc..... it's fine waiting for a security update and all but you don't exactly get many of them on Android, hell it's even worse if you're using a skinned version, like a majority of android users (Samsung).

  11. #11
    Account closed at user request
    Join Date
    Aug 2003
    Location
    Elephant watch camp
    Posts
    2,150
    Thanks
    56
    Thanked
    115 times in 103 posts
    • wasabi's system
      • Motherboard:
      • MSI B85M-G43
      • CPU:
      • i3-4130
      • Memory:
      • 8 gig DDR3 Crucial Rendition 1333 - cheap!
      • Storage:
      • 128 gig Agility 3, 240GB Corsair Force 3
      • Graphics card(s):
      • Zotac GTX 750Ti
      • PSU:
      • Silver Power SP-S460FL
      • Case:
      • Lian Li T60 testbanch
      • Operating System:
      • Win7 64bit
      • Monitor(s):
      • First F301GD Live
      • Internet:
      • Virgin cable 100 meg

    Re: Microsoft hits back after Google publicises Windows bug

    Quote Originally Posted by GuidoLS View Post
    Meanwhile, Google is ignoring security flaws in Jelly Bean (Android 4.3)...

    http://blogs.wsj.com/digits/2015/01/12/google-not-fixing-some-old-android-bugs/

    Considering that Jelly Bean *still* powers roughly 2/3rds of all Android devices worldwide, you'd think they would take care of their business before calling out someone else - especially when they'd already been in contact with Microsoft, and had been given a repair date. So no, Google wasn't being honest, nor good guys. They were being hypocrites of the worst kind.

    Surely it is up to the phone manufacturers to update to KitKat? Google's own Nexus devices are, to the best of my knowledge, all up-to-date.

  12. #12
    Senior Member
    Join Date
    May 2008
    Location
    London town
    Posts
    279
    Thanks
    7
    Thanked
    16 times in 12 posts

    Re: Microsoft hits back after Google publicises Windows bug

    Quote Originally Posted by wasabi View Post
    Google's own Nexus devices are, to the best of my knowledge, all up-to-date.
    Nope, My Nexus 7 LTE is still sat on 4.4.4.

  13. #13
    Senior Member
    Join Date
    Aug 2006
    Posts
    1,399
    Thanks
    8
    Thanked
    68 times in 60 posts

    Re: Microsoft hits back after Google publicises Windows bug

    Quote Originally Posted by wasabi View Post
    Surely it is up to the phone manufacturers to update to KitKat? Google's own Nexus devices are, to the best of my knowledge, all up-to-date.
    Which you could argue is a design flaw of Android, unlike Windows and iOS who both have built in update features which work with ALL devices that use it (yes I know the limited phones they support)

    Quote Originally Posted by gagaga View Post
    Nope, My Nexus 7 LTE is still sat on 4.4.4.
    so my's non LTE 2012 nexus 7, I've not had any update notification come through... even though it's supposed to have been. Not the first time I've had to 'force' an update, the last one required me formatting the device back to stock to get the update.

  14. #14
    Senior Member
    Join Date
    Jun 2004
    Location
    Kingdom of Fife (Scotland)
    Posts
    4,991
    Thanks
    393
    Thanked
    220 times in 190 posts
    • crossy's system
      • Motherboard:
      • ASUS Sabertooth X99
      • CPU:
      • Intel 5830k / Noctua NH-D15
      • Memory:
      • 32GB Crucial Ballistix DDR4
      • Storage:
      • 500GB Samsung 850Pro NVMe, 1TB Samsung 850EVO SSD, 1TB Seagate SSHD, 2TB WD Green, 8TB Seagate
      • Graphics card(s):
      • Asus Strix GTX970OC
      • PSU:
      • Corsair AX750 (modular)
      • Case:
      • Coolermaster HAF932 (with wheels)
      • Operating System:
      • Windows 10 Pro 64bit, Ubuntu 16.04LTS
      • Monitor(s):
      • LG Flattron W2361V
      • Internet:
      • VirginMedia 200Mb

    Re: Microsoft hits back after Google publicises Windows bug

    Quote Originally Posted by Corky34 View Post
    Didn't Google stop support of Jelly Bean (Android 4.3) back in July 2013 ?
    My problem with them is that while it's fine for them to stop support, the only official answer is "buy a new device and consign the old one to landfill" - how very environmentally friendly of them.
    Quote Originally Posted by wasabi View Post
    Surely it is up to the phone manufacturers to update to KitKat? Google's own Nexus devices are, to the best of my knowledge, all up-to-date.
    That first bit is Google's line - which personally is a pretty flimsy excuse. I cannot see why Google couldn't "persuade" it's OEM's to unbundle their UI's (and other assorted bloatware) therefore making a heck of a lot easier for OS updates to be done. Or why not just allow folks with old devices (like those millions of peoples who have Galaxy S3's for example) to download and flash raw (Nexus style) Android? Then at least you'd be able to do something about security flaws other than adding another device to landfill. After all, there's a lot of developers on XDA-Devs that appear to be able to do this!

    Yes, I'd definitely prefer that Google got their house in order!

    Career status: still enjoying my new career in DevOps, but it's keeping me busy...

  15. #15
    Senior Member
    Join Date
    Oct 2013
    Location
    Newcastle Upon Tyne
    Posts
    926
    Thanks
    54
    Thanked
    105 times in 72 posts
    • Jowsey's system
      • Motherboard:
      • Asrock H81M-ITX
      • CPU:
      • Intel Xeon E3-1230V3
      • Memory:
      • 8GB Corsair XMS3
      • Storage:
      • 256GB Crucial MX100 & 2TB Seagate Barracuda
      • Graphics card(s):
      • Asus GTX 770 DCUII 2GB
      • PSU:
      • EVGA SuperNova GS 550 watt
      • Case:
      • Phanteks Evolv ITX
      • Operating System:
      • Windows 7 64 bit
      • Internet:
      • Virgin Media 100Mb

    Re: Microsoft hits back after Google publicises Windows bug

    Quote Originally Posted by wasabi View Post
    Surely it is up to the phone manufacturers to update to KitKat? Google's own Nexus devices are, to the best of my knowledge, all up-to-date.
    I'm with you.

    Google have made available several updates since 4.3. It's weird that some people with Nexus devices haven't received the update yet.

    I'm going to rock the boat here a bit as I kind of understand why Google might have done this.

    90 Days is a lot of time. It's 3 months. Quarter of a year. If people like Google aren't going to keep putting pressure on M$ to ensure there products are secure then someone will use these vulnerabilities, probably for a more sinister means.

    M$ are talking rubbish when they say Google has endangered customers. M$ told Google it's fixed and they are just waiting to push it out. It feels like M$ is in a bad mood as Google didn't keep to it's pointless deadline and instead keep to it's own.

  16. #16
    Token 'murican GuidoLS's Avatar
    Join Date
    Apr 2013
    Location
    North Carolina
    Posts
    806
    Thanks
    54
    Thanked
    110 times in 78 posts
    • GuidoLS's system
      • Motherboard:
      • Asus P5Q Pro
      • CPU:
      • C2Q 9550 stock
      • Memory:
      • 8gb Corsair
      • Storage:
      • 2x1tb Hitachi 7200's, WD Velociraptor 320gb primary
      • Graphics card(s):
      • nVidia 9800GT
      • PSU:
      • Corsair 750w
      • Case:
      • Antec 900
      • Operating System:
      • Win10/Slackware Linux dual box
      • Monitor(s):
      • Viewsonic 24" 1920x1080
      • Internet:
      • AT&T U-Verse 12mb

    Re: Microsoft hits back after Google publicises Windows bug

    Quote Originally Posted by Corky34 View Post
    Didn't Google stop support of Jelly Bean (Android 4.3) back in July 2013 ?
    4.3 was announced on 24 July 2013. 4.1 was announced in June of 2012. KitKat (4.4) was a Halloween gift in 2013. 5.0 (aka Lollipop) was announced in October of 2014, and by all accounts, doesn't even tick off a full percentage point of Android users.

    So no, it's not likely they stopped support when they announced the product And while it may be some form of demented fun to stand in queue for days on end every year to buy a new phone, 18 months for a major release of an OS is not a long span of time, even in today's gotta have the newest now society.
    Esse Quam Videri
    Out on the road today I saw a Black Flag Sticker on a Cadillac...


Page 1 of 4 1234 LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •