Slashdot Mirror


'Irresponsible' Google Refused Fortnite's Request To Delay Vulnerability Disclosure To Score Cheap PR Points, Says Epic's Chief (bbc.com)

The leader of the firm behind the hit game Fortnite has accused Google of being "irresponsible" in the way it revealed a flaw affecting the Android version of the title. BBC, with additional input from Slashdot staff: On Friday, Google made public that hackers could hijack the game's installation software to load malware. The installer is needed because Epic Games has bypassed Google's app store to avoid giving it a cut of sales. Epic's chief executive said Google should have delayed sharing the news. "Android is an open platform. We released software for it. When Google identified a security flaw, we worked around the clock (literally) to fix it and release an update. The only irresponsible thing here is Google's rapid public release of technical details," he said. "We asked Google to hold the disclosure until the update was more widely installed," tweeted Tim Sweeney. "They refused, creating an unnecessary risk for Android users in order to score cheap PR points."

142 of 230 comments (clear)

  1. They're miffed by Hylandr · · Score: 5, Insightful

    Google isn't playing nice. Don't get a cut of the profit? Well screw your security alerts.

    --
    ~ People that think they are better than anyone else for any reason are the cause of all the strife in the world.
    1. Re:They're miffed by 93+Escort+Wagon · · Score: 4, Insightful

      People should've already been aware that Google isn't above playing politics with software vulnerabilities.

      We've also seen it go the other way - where Google held onto vulnerability announcements regarding its own software far longer than the 90 days (or whatever it specifically is) Project Zero generally says is how long they're willing to wait.

      --
      #DeleteChrome
    2. Re:They're miffed by Narcocide · · Score: 1

      The real question is whether they've previously sued anyone else for irresponsible disclosure like this.

    3. Re:They're miffed by magarity · · Score: 5, Insightful

      There's 2 sides to this:
      1. Google wants to get a cut
      but
      2. Users really, really, really, don't need yet another gaping security hole AKA "installer" on their devices.

    4. Re:They're miffed by spire3661 · · Score: 2, Insightful

      Users really really need to get software from places other than google.

      --
      Good-bye
    5. Re:They're miffed by Aighearach · · Score: 1

      Most of my android software comes from F-droid, and that's been true for years!

    6. Re:They're miffed by Zmobie · · Score: 1

      I should amend, I feel Google is going against the spirit of their policies (with their extension on disclosure) even though they didn't technically violate the letter of it. If you disagree, then to each their own.

    7. Re:They're miffed by Xylantiel · · Score: 1

      I'm not sure which side you're coming down on.... once the patch is out it is much easier to reverse engineer the vulnerability, so the ethical thing for google to do is disclose it shortly after that time so people know that they need to update. All the ethics problems here seem to be on Epic's side. Google's app store charges may be too high, but that doesn't really compare to Epic's willingness to have their customers get malware just so they make more money.

    8. Re:They're miffed by Anonymous Coward · · Score: 1, Insightful

      Then really really put the effort into doing it right. Security is not easy - nor cheap.

      That Epic had users installing this is fucking terrifyng.

    9. Re:They're miffed by farble1670 · · Score: 1

      it may be worse because Google is taking a MASSIVE cut of revenue for doing next to nothing anymore with Google Play

      The whole reason Epic is able to make billions of dollars on Fortnite Android is because of development done by Google. Are you saying the billions and billions of dollars they spent building the Android ecosystem over the last decade is "next to nothing"?

    10. Re:They're miffed by viperidaenz · · Score: 1

      You mean what Microsoft is now doing again with Edge?

    11. Re:They're miffed by viperidaenz · · Score: 1

      Epic didn't want a security hole publicly announced while they were running their Android rollout campaign, making people think twice about the security warning they accept when side-loading apps on their phone.

      Especially since they were already told doing things this way would put the security of their users at risk.

    12. Re:They're miffed by Zmobie · · Score: 1

      Initial development is beside the point. They've made that investment back with tons of return so many times it is ridiculous. I'm perfectly fine with them taking some cut as everyone should be paid for their work, but 30% is excessive imho especially when they are just abusing a market monopoly. It might be different if they were continuing to invest that much into the infrastructure continuously, but as I said they barely do anything with the Play Store anymore. They also are monetizing in a lot of other ways despite what they want everyone to believe...

    13. Re:They're miffed by farble1670 · · Score: 1

      Pro tip: Qualifiers like "anymore" may change the meaning of the sentence.

      If you develop a product, you get to make money on it up until (?), then you have to start giving it away for free. That's how it works.

      And anyway, as far as Google Play, once you write the code and get those servers running, you just walk away from that shit and take a vacation. That's the Big Secret those Silicon Valley fat cats aren't telling us.

    14. Re:They're miffed by scdeimos · · Score: 1

      @TimSweeneyEpic is just acting like a spoilt child. Epic has published the Fortnite installer patch and Google has acted according to their publicy posted Responsible Disclosure policy, https://www.google.com/about/a...

    15. Re:They're miffed by Zmobie · · Score: 1

      Difference is there is now a viable market alternative and it shows in their market share. Microsoft has barely 10% share factoring in Edge and IE.

    16. Re:They're miffed by Zmobie · · Score: 1

      Seriously man, you're actually like they are still pouring billions into it and getting shit returns for that. Not only that, don't think I ever said they had to give it away for free... I write software for a living, I know what the markets look like and that would be a pretty stupid position for me to take. You're taking a basic argument and way extending it to an extreme that was never even implied. This has gone beyond continuing to make a good living for their initial work. This has drifted well into the gouging realm.

    17. Re:They're miffed by farble1670 · · Score: 1

      Initial development is beside the point.

      Since when? What other business operates like that? Do you think Honda starts selling their cars at cost when they've made enough profit for the year? How much is enough? Will you decide?

      They've made that investment back with tons of return so many times it is ridiculous.

      Can you provide revenues and expenditures for the Google Play division? Or do you just have a feeling about it?

      but 30% is excessive imho

      How much do you understand about what goes into Android? Development of the OS itself. Build all of the Google apps. The backend services. Working with hundreds of OEMs to support Android on their devices. Bug fixing. R&D. Server farms. Linux kernel work. Thousands of employees. All of the same for all the services Google apps depend on: messaging, gmail, calendar, maps, music, video, youtube etc. etc. etc. All with public facing APIs for developers.

      I don't claim to know either, but I'm a software engineer with some experience and the scale of that is almost beyond comprehension.

      Google is a rich company, but what % of that comes from Google Play? My guess is almost nothing relatively.

      They also are monetizing in a lot of other ways despite what they want everyone to believe...

      That's mysterious. Sounds like you know about something terrible, just terrible thing that none of us n00bs understands. Let me guess. I AM THE PRODUCT?

    18. Re: They're miffed by Zmobie · · Score: 1

      Again, you're exaggerating my point way beyond what I said. I never said it has to be at cost or free. That would be absurdly idealistic and run counter to basic economic principles. Stop with this, you know it isn't even close to my point.

      https://www.statista.com/stati...
      https://www.statista.com/stati...

      20 billion on play alone in 2017. Didn't see their revenue total but Q2 2018 was 30 so 120 is a safe assumption. Meaning it accounted for 1/6 of their revenue... They aren't dumping even half that into the distribution piece or even likely most of the support structure by now. There's your numbers. I'd say 16% is a bit bigger than "relatively nothing."

      Now, considering I am a software engineer and work on enterprise level systems and architecture, yea I have a pretty good idea of what goes into Android development. Don't get on a high horse with that like I'm some pleb that doesn't know what I'm talking about. I've deployed large scale systems with everything you're mentioning for fortune 500 companies though mostly not consumer facing.

      The last part is just you being asinine. I'm clearly referring to the largely known fact that Google collects and sells information and not even acting like somehow you don't know. Google does in fact want people to believe otherwise, I was merely making an aside.

    19. Re:They're miffed by farble1670 · · Score: 1

      Seriously man, you're actually like they are still pouring billions into it and getting shit returns for that.

      Yes, Google is still pouring billions into what makes Android. Search. Google maps. Gmail. Hangouts. OS development. Security research. Visual design. Development APIs. Chrome browser. Linux kernel development. Assistant. Voice recognition. Play music. Youtube. Enumerable developer APIs. And so on.

      Developers don't write apps for Android because of the store. The store is just a browser for apps. They write apps for Android because Google builds a rich ecosystem that has attracted millions of users, millions of users that will potentially pay for their apps and watch the ads in their apps. They've attracted thousands of OEMs to build many unique hardware permutations.

      No, that stuff isn't "done."

    20. Re: They're miffed by Zmobie · · Score: 1

      You ignored the second half of that statement which changes the meaning a lot. They are not trying shit returns on that, and that's the point. Bottom line it is a monopoly and you can choose to believe they won't abuse that but I don't and believe they definitely are.

    21. Re: They're miffed by Zmobie · · Score: 1

      Getting* phone typing is apparently hard for me...

    22. Re:They're miffed by rtb61 · · Score: 1

      Look software coders get away with all sorts of crap, the worst warranties in the history of the word warranty for a start. It's called criminal negligence, https://en.wikipedia.org/wiki/.... This being the purposeful withholding from the public of faults in software which can be criminally exploited, to gain illegal access to the computing device. This not once but upon a repeated basis and in fact instituted illegally upon a cartel basis, all agree to keep secret security faults in each others software to protect their profit margins. "To constitute a crime, there must be an actus reus (Latin for "guilty act") accompanied by the mens rea (see concurrence). Negligence shows the least level of culpability, intention being the most serious, and recklessness being of intermediate seriousness, overlapping with gross negligence." So keeping software bugs secret from the public who should be made aware is technically a criminal act. Only one person needs to be hacked by a known and kept secret bug and those who kept it secret are guilty of a criminal act, that of criminal negligence.

      Those little keep it secret deals are actually conspiracy with criminal intent to act in a criminally negligent fashion. By law, upon discovery, those faults should be immediately reported to the applicable authorities, they are the only ones allowed to decide whether or not it be kept secret, your little cushy deals, actually against the law.

      --
      Chaos - everything, everywhere, everywhen
    23. Re:They're miffed by Gimric · · Score: 1

      Except the people who get hacked and their android customers, not Epic.

  2. So what's the full story by alvinrod · · Score: 2

    I'd at least like to hear Google's side of this first.

    Would hate to unpack the pitchfork for nothing and all that.

    1. Re:So what's the full story by thaylin · · Score: 5, Informative

      Google followed its own guidelines. Their guidelines are that they will release the details when the first of 2 things happens, either 90 days has expired OR a general availability patch has been released. The second happened, but Epic wanted google to violate its own guidelines for them.

      --
      When you cant win, ad hominem.
    2. Re:So what's the full story by Anonymous Coward · · Score: 1

      I'd at least like to hear Google's side of this first.

      Follow the second link in TFS, which will get you to the Slashdot article from August 24th, and has a link to the Google issue tracker.

      Basically Google found out that Epic's installer was vulnerable to other people taking it over and using it to install pretty much anything.

      This sounds like a company pushed out an update to bypass the app store, and in the process introduced a giant security hole.

      Sounds like Google was more concerned with user security than giving a damn about Epic's PR.

    3. Re:So what's the full story by u19925 · · Score: 1, Informative

      I'd at least like to hear Google's side of this first.

      You heard google already. They told what they had to when they announced the security issue. Only then Epic has reacted. In this instance, Google is outright greedy and wants to kill anybody who wants to distribute software outside of Google Play store. So much for the open Android platform. Manufacturers cannot fork Android otherwise none of the phones can be connected to Play Store. They must install dozens of privacy invading Google apps in default settings otherwise no Play Store. Android are simply Google peeking devices. At least with FB, they get what you explicitly provide. Apple virtually does not use anything you provide and collects far little data. Google implicitly collects all data that you may not be aware of and sells them to the highest bidders even if they know that purchaser is using it illegally (one of the largest corporate fines ever was paid by Google to settle illegal drug ads).

    4. Re:So what's the full story by u19925 · · Score: 1

      Google does not provide level of details that id did for Epic flaw immediately after the patch is made generally available.

    5. Re:So what's the full story by SantiagoMcRib · · Score: 5, Insightful

      This is well stated. And for those that think that it's vindictive on Google's part, well... you're not wrong, but it's the consequence of releasing outside the ecosystem that would automatically deploy the update to the install base.

      I think a lot of people are failing to realize that the 30% cut isn't just to make Google money, but also to fund the infrastructure to host and deploy apps according to their own best practices.

    6. Re:So what's the full story by Albanach · · Score: 5, Insightful

      Let's think about what Epic were asking for. They'd prefer users not be notified of a critical vulnerability for three months and instead just wait to see how many upgrade naturally.

      Google on the other hand have a published policy that they will notify of security events after 90 days if un-patched or after a patch is widely available, exactly what happened here.

      While Google does have a strong financial incentive to stop other companies from operating outside the play store, they also have an incentive for Android not to be viewed as a less secure mobile operating system. It seems to me that, if you want to encourage security patches to be applied, you would want to let users know that their existing install has a critical vulnerability. Why Epic would prefer silence can be inferred, but it's not to the benefit of their customers.

    7. Re:So what's the full story by Cochonou · · Score: 1

      It is certainly reasonable for server-side software in which a security team ensures that the current installation is not vulnerable to exploits, and performs the required patching/updating operations.
      For commercial software aimed at general users, the benefits of (very) prompt disclosure are more questionable:
      - Regardless of the disclosure status, these users will most likely never hear about it.
      - Even if they hear about it, in the specific case of games such as Fortnite, a significant proportion of the users will not care about the vulnerability as long as they can play.
      - Updates will be pushed through the app store/update manager/etc, with no user interaction.

    8. Re:So what's the full story by thaylin · · Score: 1

      Actually before they released the patch they ensured that darn near everyone had the patch, even Epic stated that:

      "Sweeney concedes that "Google did privately communicate something to the effect that they're monitoring Fortnite installations on all Android devices(!) and felt that there weren't many unpatched installs remaining"."

      Also pretty much every disclosure I have seen has had technical details.

      --
      When you cant win, ad hominem.
    9. Re:So what's the full story by Xylantiel · · Score: 4, Insightful

      It doesn't help that if Epic's launcher had been distributed through the play store, I think having it update would be less of a problem. And this is one of the major security advantages of distributing through the play store. So you can view the entire decision of Epic to not distribute through the Google store as sacrificing user security for more money. I don't even want to know how many scam download sites there are. It is a lot harder to tell the difference on a phone than on a desktop. If this is any indication of how seriously Epic takes their customers' security, one better assume it's pretty much a field day of vulnerabilities.

      I happen to agree that the Google play store is kindof onerous, but what Epic has done is a worse solution from the user standpoint and failed in a completely predictable way in this case. There are other possible solutions, but the handset vendors are too used to having Google do a lot of things for them to push the issue, or too hostile to each other to work together. ...or maybe it actually all comes back to DRM such that an actual open and fair platform is untenable from the start.

    10. Re:So what's the full story by Zmobie · · Score: 1

      Some money is appropriate, but 30% is pretty damn excessive. Factor in the taxes and most of the companies are lucky to get half of what they are charging and a bunch of that I'm sure is overhead.

    11. Re:So what's the full story by RhettLivingston · · Score: 1

      Exactly. I'd like to add that in this case, it doesn't seem like they should have followed the rules.

      Epic's game and installer is a non-essential add-on. Removing a downloaded exploit is a fine and normal solution to cleaning the device. The users should have been notified immediately to implement the obvious solution.

    12. Re:So what's the full story by Zmobie · · Score: 1

      In finding the vulnerability, yes they were concerned. Given how popular the game is though, the disclosure should have been delayed and Google knows it. If they had worked with Epic they probably could have waited until at least a 75% patch rate (which is reasonable) was attained before making the disclosure. Especially given how new this thing is right now. Because of Google's practices on Android, it is more complex for users to patch Epic's installer and Google knows that too, but doesn't care. It looks as it they thought, "we can spin the narrative that if they used our distribution platform they would have had plenty of time," and play innocent that this was policy (regardless of the fact that it is also normal practice to extend the disclosure time for extenuating circumstance, like this).

      Meanwhile, if they HAD waited a little bit longer and the saturation was high enough the vulnerability would be nearly useless by that point (and lets be real, the 75% I mentioned wouldn't have taken all that much longer to wait out, they wouldn't have even hit the 90 day policy...), because by the time someone could exploit it their success rate wouldn't be good enough to make it worth their while. The only reason they have the 7 day after patch policy is normally that is enough time to reach the patch rates that make the vulnerability useless.

    13. Re:So what's the full story by Jerry+Atrick · · Score: 1

      You're assuming Epic gave Google that information, that the information was correct and Epic a believable source.

      Google make bad judgements but are serious about bugs they didn't deliberately intend. Epic are more often just clueless and slow to acknowledge bugs.

      It's hard to take Epic's bleating seriously.

    14. Re:So what's the full story by Aighearach · · Score: 1

      If Epic didn't give Google the information, then Google doesn't have it and can't act based on it!

    15. Re:So what's the full story by viperidaenz · · Score: 1

      If their software was distributed via Google Play, the patch would have been installed automatically for the majority of users after a few days. By default phones are set to auto-update apps when they're on WiFi and charging. Google Play itself always auto-updates. Epic is saying after a week hardly anyone has updated their installer.

    16. Re:So what's the full story by viperidaenz · · Score: 1

      They don't pay tax on the 30% Google took.
      They also don't need to run any of their own infrastructure, pay for bandwidth or pay a payment processor, which for very small transactions like in-app purchases, will charge a lot higher than the "normal" 2.5%.
      They also don't need to worry about the security implementation of the payment system in their app. Or the security of the installation manager software, which apparently did Epic not worry about, they completely disregarded any attempt at security.

    17. Re:So what's the full story by viperidaenz · · Score: 1

      Of because Google knows about all app installations, because users agreed to let Play Protect scan all installed apps.

      Google probably have a better idea than Epic. As the users actually need to run the software for it to notify Epic that it's installed and what version it is. Google already has that software running on virtually every Android phone.

    18. Re:So what's the full story by Zmobie · · Score: 1

      That is a fair point if true, but it seems self-defeating for Epic to say anything if that were the case. Perhaps it can then be thrown in the pointless corporate pissing match, but I stand by Google does have ulterior motives.

    19. Re:So what's the full story by Zmobie · · Score: 1

      The 30% is part of the overhead.

      Wait, so then you're saying as a consumer you're perfectly fine with having to pay an additional 30% markup because of Google's mainstream distribution monopoly? I guess to each his own, but that seems pretty damn excessive to me still.

      I also think the cut they are taking is excessive regardless of it being a game or being popular. They are entitled to some type of servicing fee (I don't expect an OS to be given away for free), but they are not redeveloping the app store every month/year. The damn thing has been largely unchanged for some time now. Yes some of it is to fund Android development and again that is fine, but this is not their only revenue stream. I really can't blame Epic for not wanting to hand over that much money to them. And as I said in another post, no Google did not violate the letter of their policy, but I do feel they violated the spirit depending on what the patch rates were (someone else pointed out they may have been at a decent level, we don't know the real numbers though).

      The rest of it, I will 100% give you they assumed the risk creating their own installer and publishing outside the standard distribution channels (I'm just not arguing with their reasoning for doing so). They did fuck up and deserve some PR hit for doing it. Unfortunately what has become clear to me through all of these posts and the volume of people landing on different sides of this, were honestly speculating a lot without more information. Large part of it comes down to which side we're willing to give the benefit of the doubt as to being less dishonest (not going to use honest, neither company is actually honest). I personally have become a bit jaded with Google so I tend to put less faith in them...

    20. Re:So what's the full story by Shikaku · · Score: 1

      https://support.google.com/goo...

      You are correct, by default they do.

    21. Re:So what's the full story by stooo · · Score: 1

      >> Epic wanted google to violate its own guidelines for them.
      You don't violate a guideline. it's a "Guide" "Line", not a rule.

      If the update took more than 7 days to apply, the update mechanism is flawed and needs change fast.

      --
      aaaaaaa
  3. Google was right here by Anonymous Coward · · Score: 1, Insightful

    If an application is allowing malware to be sideloaded, the users have damn well a right to know about it.

  4. Re: Irresponsible Epic released vulnerable code. by Anonymous Coward · · Score: 1

    Google is not the distributor. In fact they are aggressively acting out because they are not the distributor.

  5. Hmmmm by Anonymous Coward · · Score: 1, Interesting

    I guess what Google is really saying here is if you find any zero-days in Android, publish them right away. Never mind this silly 'responsible disclosure' that companies like Google make noises about supporting.

    1. Re:Hmmmm by squiggleslash · · Score: 1

      No, they're saying that if a patch is published for a vulnerability, people should be told that the vulnerability exists and that there's a patch for it.

      --
      You are not alone. This is not normal. None of this is normal.
    2. Re:Hmmmm by viperidaenz · · Score: 1

      They're saying wait until that patches are being deployed before publishing. Like what they did in this case.

  6. Hard to care about either party... by Austerity+Empowers · · Score: 2

    It's not clear what level of ownership Google should be expected to take on this. It seems to me that they technically did more than I'd feel obligated to in their shoes. Epic appears to have been responsible for the bug, Google appears to have found it for them. Honestly I think they already went the extra mile right there.

    Of course if Epic used the app store, then I'd expect a more appropriate arrangement of identification, fix and announcement.

    1. Re:Hard to care about either party... by drinkypoo · · Score: 1, Interesting

      It's not clear what level of ownership Google should be expected to take on this. It seems to me that they technically did more than I'd feel obligated to in their shoes.

      That is in fact the nature of Epic's objection. Google did more than they were obligated to do, and the thing they did put users at risk, it did not protect them.

      Epic appears to have been responsible for the bug, Google appears to have found it for them. Honestly I think they already went the extra mile right there.

      And that's where they should have stopped. If Epic were not addressing the bug, then full and immediate disclosure would have been warranted, but that was not the situation.

      Of course if Epic used the app store, then I'd expect a more appropriate arrangement of identification, fix and announcement.

      Nice bug you've got there. Shame if someone announced it unnecessarily while you were fixing it. Guess you should have paid the protection money, eh?

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:Hard to care about either party... by barc0001 · · Score: 2

      If Epic used the app store, the vulnerability never would have existed. It's because they're sidestepping the security there that the problem came to be.

    3. Re:Hard to care about either party... by thaylin · · Score: 2

      That is in fact the nature of Epic's objection. Google did more than they were obligated to do, and the thing they did put users at risk, it did not protect them.

      I disagree. In order to install the app they had to disable several security mechanisms, and probably not turn them back on. They told epic about the flaw and waited for them to fix it, once it was fixed and released a patch it is best for all people to know they need to immediately patch, since there are no guarantees their loader auto patches.

      and that's where they should have stopped. If Epic were not addressing the bug, then full and immediate disclosure would have been warranted, but that was not the situation.

      incorrect. Google has an obligation to continue, unless you think flaws should not be disclosed unless they fail to fix them?

      Nice bug you've got there. Shame if someone announced it unnecessarily while you were fixing it. Guess you should have paid the protection money, eh?.

      Again they did not disclose it during the fix, they disclosed it after a patch had been released. They followed their own guidelines.

      --
      When you cant win, ad hominem.
    4. Re:Hard to care about either party... by drinkypoo · · Score: 1

      Again they did not disclose it during the fix, they disclosed it after a patch had been released. They followed their own guidelines.

      It's pathetic to see people justify abuse under the law, but it's even more pathetic to see people justify abuse under corporate policy.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    5. Re:Hard to care about either party... by thaylin · · Score: 1

      So you are saying Google should have put users in danger by holding on to the discloser, for what reason?

      --
      When you cant win, ad hominem.
    6. Re:Hard to care about either party... by Anonymous Coward · · Score: 2, Informative

      Nice bug you've got there. Shame if someone announced it unnecessarily while you were fixing it. Guess you should have paid the protection money, eh?

      The fix was already made available. As per Google's guidelines, they either announce the issue 90 days after reporting it, or a week after the fix is made broadly available. From the article, the fix was made available on Aug 17, and Google announced the flaw Aug 24 (a week after it was made available).

      Now, whether a week is enough time or not is another question... Epic wanted the full 90 days, Google said nope. How much time would be sufficient? Will everyone who downloaded it update, without knowing there's a major security flaw in their installed version? From the article, the installer is only updated when it or the game is run. So if a user downloads it and tries it once, then doesn't look at it again and also doesn't uninstall it, they are now vulnerable.

    7. Re:Hard to care about either party... by StormReaver · · Score: 1

      I find it hard to care about either party when two evil companies are battling it out for the evil crown that only hurts the two evil companies.

      They both suck, just in different ways.

    8. Re:Hard to care about either party... by spire3661 · · Score: 2

      So you honestly think that getting software from only on place is the best possible future? Android NEEDS to get programs from places other than google. Why are you cheering this crap on. The faster we break people's complete dependance on Google Play, the better off we will all be.

      --
      Good-bye
    9. Re:Hard to care about either party... by bluefoxlucid · · Score: 1

      It's pathetic to see people justify abuse under the law, but it's even more pathetic to see people justify abuse under corporate policy.

      It looks more like you said they shouldn't have published a vulnerability before the patch was ready, and GP pointed out Google published the vulnerability after the patch was already released and being installed by users for a week.

      Most of us get the advisory that a patch fixes a critical vulnerability the second the patch is released. It's right there in the release notes, right up front.

      Google did more than they were obligated: they kept quiet a week longer than required to let Epic make the announcement and let users catch up. They only had an obligation to go 90 days without a patch or one second after the patch was released.

    10. Re:Hard to care about either party... by Anonymous Coward · · Score: 1

      And you just said that only Google Apps are available in Google's App Store.... Go fuck yourself. Hell, even Microsoft, Apple, Dell and IBM have their apps in the Google App Store.

    11. Re:Hard to care about either party... by barc0001 · · Score: 1

      > So you honestly think that getting software from only on place is the best possible future?

      So you honestly think an army of millions of 12 year olds can properly vet and secure their Android device? Like it or not, Android, IOS and similar mobile OSs operate on a walled-garden approach to the average user. Half of the reason we have massive malware problems on Windows is due to anyone and anything installing any application any time without proper vetting. Your Grandma gets a scary popup? She does what it says and bang! she's now mining crypto for some Russian. At least Android out of the box has a fairly decent defense against the the most basic vector of infection, and now Epic is telling people to disable that deliberately.

      > Android NEEDS to get programs from places other than google.

      Why? Serious question. You knew what you were buying into when you got a smartphone, and that was a curated ecosystem. Even this curated ecosystem is way more open than what came before smartphones, remember the days of running an "app" on an old Nokia or Motorola? How about PalmOS or Symbian apps?

      So to your question - for a PHONE? Yes, it's best that the average person on the street gets their software from a centralized location where there is at least some quality control and attempts to head off malware. At the end of the day, the main reason you have a PHONE is to call people and communicate with them, and it already does all of that out of the box.

      To be perfectly honest, I would like to see it restricted even more. In my ideal world if you want to install an .APK on your Android phone, you would have to physically load it from a PC over a USB cable. That would eliminate much of the risk IMO. That way everyone who wants to use non-Play store software can still do so, but a clueless end user can't easily be tricked into sideloading something malicious.

    12. Re:Hard to care about either party... by Anonymous Coward · · Score: 1

      The only abuse here is being done by Epic for using their own flawed distribution mechanism and expecting Google to bend over backwards to change their long-standing policies regarding exploit notification.

    13. Re:Hard to care about either party... by Aighearach · · Score: 1

      When you think you're going the "extra mile" for somebody else, but you're not actually part of their team, and they tell you to stop... That means you weren't helping.

    14. Re: Hard to care about either party... by thaylin · · Score: 5, Insightful

      AFTER it has been patched so uses can patch? That is not how it works dude. If they announced the bug BEFORE a patch was made available then sure, but after a patch is released it is more irresponsible to NOT release the details because people wont know they need to patch, but exploiters will know there was a patch and can seek it out.

      --
      When you cant win, ad hominem.
    15. Re:Hard to care about either party... by tlhIngan · · Score: 1

      How about PalmOS or Symbian apps?

      Actually, PalmOS and Symbian apps were open - there was no app store or anything. You downloaded the files and installed them on your phone.

      Of course, it meant that every app had to implement some sort of demoware thing, and not everyone took a credit card so paying for your software was a PITA (especially if you were outside the US). And you often had the trouble of upgrades so you had to hunt down your registration codes again.

      Yes, things are better now since everyone's pretty much has the ability to accept credit cards - either by opening a real merchant account, or by using something like Paypal. And that didn't stop some rather interesting DRM schemes from being implemented.

      One of the most dangerous ones was a PalmOS app called Liberty that was a game boy emulator. If pirated it would destroy your data. Due to a bug, it inadvertently was a bit too aggressive and destroyed not only the data, but the device itself (erasing critical flash memory blocks). There was a fixed version after a couple of hours of getting discovered, but the author spent a few bucks having to replace devices.

    16. Re: Hard to care about either party... by barc0001 · · Score: 1

      > My generation did it in the 80/90/00s and we had no problem.

      I'm part of "that generation" as well, and I can recall massive problems that started back then which we still live with today. Except back in the olden days the vector was a floppy disk. These days it's wireless and OTA. Back then you fed a stupid prompt a cookie, these days your gran's phone gets locked out while it mines crypto or has its file system encrypted and held for ransom.

      Walled garden ecosystems exist for a reason and that reason is the average user has proven time and again to be anywhere from mostly to completely incompetent at handling security threats.

    17. Re:Hard to care about either party... by barc0001 · · Score: 1

      > Actually, PalmOS and Symbian apps were open - there was no app store or anything. You downloaded the files and installed them on your phone.

      I remember well, and the thing about it was you had to use your PC to download them and then go to the trouble of purposely uploading them to your device. Which, as I mentioned I think is a great idea and is exactly how sideload .apk files should have to work because that would dramatically reduce the chances of someone tricking the average user into running something unintended.

    18. Re: Hard to care about either party... by astrofurter · · Score: 1

      "pathetic"

      I think the preferred term is "little Eichmanns".

  7. It ceratinly makes sense. by nimbius · · Score: 4, Insightful

    Google has nothing to lose by delaying disclosure of an exploit that isnt even in its ecosystem...
    however...google has everything to lose if the idea of operating outside its walled garden catches on.

    --
    Good people go to bed earlier.
    1. Re:It ceratinly makes sense. by colonslash · · Score: 1

      > Google has nothing to lose by delaying disclosure of an exploit that isnt even in its ecosystem...
      They do have something to lose, the security of and confidence in Android. Disclosing this bug lets users know about it so they can make sure the vulnerability is closed (like by updating the installer).

    2. Re:It ceratinly makes sense. by celeb8 · · Score: 1

      Google has plenty to lose when people add exploitable installers to "its ecosystem", to use your term. "Their ecosystem" (to use your term) has a reputation already for being lax security-wise, and mostly for just this sort of issue, the fact that they don't wall off their garden as strenuously as some others (evidence for this: side-loading still exists). They also would obviously prefer that people use their methods for install, since they get money and are able to police the security better. So, three separate motives, but unless you're distorting things for the purpose of rhetoric all three point to Google being open and honest and letting their users know of a vulnerability. Sunshine isn't a bad thing unless you're trying to hide something.

    3. Re:It ceratinly makes sense. by Dagmar+d'Surreal · · Score: 1

      Exactly how is something meant to run on Android NOT "in its ecosystem"?

  8. Google is not to blame here. by thaylin · · Score: 5, Informative

    Google followed its own guidelines. Their guidelines are that they will release the details when the first of 2 things happens, either 90 days has expired OR a general availability patch has been released. The second happened, but Epic wanted google to violate its own guidelines for them.

    The problems is in bypassing the play store they did open themselves up some and now they want google to change, not them.

    --
    When you cant win, ad hominem.
    1. Re:Google is not to blame here. by thaylin · · Score: 1

      No they are not. They released the patch to the general public patch. Google waited 7 days more and released the vulnerability.

      --
      When you cant win, ad hominem.
    2. Re:Google is not to blame here. by thaylin · · Score: 2

      What abuse? The patch was released in a matter of a day or so..

      What happens if a hacker finds the vulnerability and targets the users who dont know they need to patch? Well Epic and Google would have put those people in jeopardy by holding it. This way people know they need to patch.

      --
      When you cant win, ad hominem.
    3. Re:Google is not to blame here. by Luthair · · Score: 2

      The guidelines are reasonable, once a patched version is available interested attackers can compare binaries and discover the vulnerability. All hiding the disclosure does is give these attackers more time to exploit the vulnerability by making it less likely users will know to upgrade.

    4. Re:Google is not to blame here. by bluefoxlucid · · Score: 1

      That actually sounds like a good strategy: let them have rope enough to hang themselves, then blame Epic for the sudden rush of malware-laden Android phones after their sideload software gets everything hacked to hell. Frighten the world into running as far away as possible from anything you haven't blessed.

    5. Re:Google is not to blame here. by amicusNYCL · · Score: 1

      Why does Google have any role in this at all? Their role is to develop Android and run their own store. Why are they policing independent developers not using the Google store? Isn't it only Epic's responsibility to communicate with their own customers?

      --
      "Our two-party system is like a bowl of shit looking at itself in a mirror." - Lewis Black
  9. Lock vulnerable app, can update, can not run by perpenso · · Score: 2

    "We asked Google to hold the disclosure until the update was more widely installed," tweeted Tim Sweeney. "They refused, creating an unnecessary risk for Android users in order to score cheap PR points."

    Allowing the unpatched game to continue running also unnecessarily risks Android users. Doesn't google have the ability to delete an app in Android? If so perhaps they should have deleted the unpatched game versions?

    Looking forward maybe google should have the ability to lock out a vulnerable version of an app. Don't delete it, just prevent it from running, only allow it to be updated to a newer version.

    1. Re:Lock vulnerable app, can update, can not run by EndlessNameless · · Score: 1

      Google can do that for Play apps. This whole pissing match started because Epic decided NOT to publish Fortnite on the Play Store.

      --

      ---
      According to the latest ruleset, this post should be modded as Vorpal Flamebait +5.
    2. Re:Lock vulnerable app, can update, can not run by Dagmar+d'Surreal · · Score: 1
      "They refused, creating an unnecessary risk for Android users in order to score cheap PR points."

      ...amazing how that can be obverted to say "Tim Sweeney refused to prioritize publishing the update and an apology because it would cost Epic PR points".

      ...although seriously, I'm not carping on you about that. You're totally right that Google could have simply dropped a signature for Epic's installer into their vulnerability monitor and instantly yanked it off every Android device if they'd wanted to, but Epic would have really thrown a tantrum about that.

    3. Re:Lock vulnerable app, can update, can not run by perpenso · · Score: 1

      True, I'm just making the point that if we are to judge actions by Epic's "creating an unnecessary risk for Android users" criteria then there may be appropriate actions Epic is not considering.

    4. Re:Lock vulnerable app, can update, can not run by perpenso · · Score: 1

      You want google to be able to lock side-loaded apps? You realize the whole point of the article was the app was not installed via the play store right?

      With respect to malware or a serious infection vector for malware, why not? Play or non-Play is irrelevant. Its little different than anti-virus software quarantining or deleting detected malware.

    5. Re:Lock vulnerable app, can update, can not run by perpenso · · Score: 1

      If google started deleting or blocking the apps that I choose to sideload onto my android, I would ditch them ASAP and join the class action lawsuit which would surely follow.

      If they were doing so only in cases of genuine malware, you would lose. And the terms of service could easily be updated to permit this if not already allowed to further weaken your actions.

  10. Re: Irresponsible Epic released vulnerable code. by barc0001 · · Score: 1, Insightful

    Google doesn't distribute Android? When did that happen?

    Regardless, anyone with two brain cells to rub together could see this shitshow (and more in future) coming the second Epic announced that in order to install their software you'd have to allow uncertified install packs on Android. Many many people do not have the technical acumen to understand the full ramifications of that, and will probably forget to flip the switch when they're done, so a whole host of malware providers are even as we speak licking their chops waiting to take advantage of the holes in the devices Epic has just convinced their users to open.

    Does Google charge too much on the Play Store? Probably. But it's their store and they can set any price they think the market will bear, just like anyone else. That's the deal for using Android. Epic is being very irresponsible.

  11. Re: Irresponsible Epic released vulnerable code. by Megol · · Score: 1

    I think you are a bit confused if you think this bug was in Android...

  12. Re:Google petty AF by Big+Boss · · Score: 1

    Google's policy seems reasonable. There's a fixed version, so disclose the info.

    Not only is it a shitty installer, the whole idea of an installer app on Android is shitty. Just have people download the APK and use the built in package installer. If it's about download size, use the same trick most big games do and have the app load data files on first launch into its own protected data directory. All of that is built in and is quite safe and audited.

    Not that Google never does anything shitty, but this one is on Epic.

  13. Re: Irresponsible Epic released vulnerable code. by tbuddy · · Score: 2

    They did the same thing they do with other bugs. Give them 90 days to fix it and disclose 7 days after it is patched, whichever comes first. It's hard to say they are being unfair or aggressive since it is the exact same time window they have for anything else. It's not google's responsibility to hold on to the release beyond 7 days because Epic asks them for more time to ensure everything is long since patched.

  14. Re:Irresponsible Epic released vulnerable code. by The+Faywood+Assassin · · Score: 1

    This is correct. If they don't want Google to shit on their parade, maybe they should have plugged the security holes.

    --

    "I'm a humble person really,

    I'm actually much greater than I think I am"

  15. Re:Google petty AF by drinkypoo · · Score: 1

    Not only is it a shitty installer, the whole idea of an installer app on Android is shitty. Just have people download the APK and use the built in package installer.

    That's not a fully working solution because it leaves out people who get confused during the download process. If you download an APK then it appears in your downloads list and as a notification. If you clear that notification and your downloads list then there is no way whatsoever to install that APK without installing additional software, like a file manager, unless you download it again. Many people are probably not even aware of the downloads list, and if someone has a lot of notifications they might not be able to figure out how to install the APK they just downloaded. This is Google's fault; they should have included a file manager with their OS, but they didn't.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  16. Re: Irresponsible Epic released vulnerable code. by drinkypoo · · Score: 1

    It's not google's responsibility to hold on to the release beyond 7 days because Epic asks them for more time to ensure everything is long since patched.

    It's not Google's responsibility to announce the vulnerability, either. They choose to do so, nobody is forcing them.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  17. Re: Irresponsible Epic released vulnerable code. by Anonymous Coward · · Score: 1

    vulnerabilities need to be announced as soon as they reasonably can, otherwise everyone is running on unpatched systems and being silently exploited, or not so silently once some ransomware gets on there.

  18. Reverse Engineer by Luthair · · Score: 4, Insightful

    The moment a patch is released attackers have the opportunity to reverse engineer the patch to find the vulnerability regardless of whether there is a subsequent disclosure or not. By this vulnerability being widely circulated in the press its more likely users will upgrade or uninstall than hoping users launch fortnite in the next 90-days. I imagine the real issue Epic has here is that they do not want the bad press leading to users who downloaded Fortnite to try uninstalling.

    1. Re:Reverse Engineer by thaylin · · Score: 1

      You would think most slashdot readers would understand this, apparently not.

      --
      When you cant win, ad hominem.
    2. Re:Reverse Engineer by Tough+Love · · Score: 1

      Most Slashdot readers also understand that if upstream requests that disclosure be delayed because mitigation procedures are in process, then it is normal to respect such a request.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    3. Re:Reverse Engineer by locopuyo · · Score: 1

      I don't think you even understand it. The vulnerability is that if you connect to a compromised wifi connection and attempt to manually update the app (there is no automatic update) they can spoof the update with their own malicious update.

      If someone uninstalls then searches the web to re-download it using compromised wifi they could be taken to a fake site serving malware. So if someone is naive enough to trust a malicious wifi connection they're even more at risk with this exploit being made public. This doesn't really help anyone, it's just a PR attack by Google.

    4. Re:Reverse Engineer by thaylin · · Score: 1

      Except there were no mitigating procedures in process, and google had already identified that nearly all downloads had patched.

      --
      When you cant win, ad hominem.
    5. Re:Reverse Engineer by Tough+Love · · Score: 1

      Rubbish, a patched downloader was being distributed, this is a mitigation procedure. Weasel word "nearly" does not save your argument.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    6. Re:Reverse Engineer by thaylin · · Score: 1

      My god you really went around the neighborhood to try and attack google.

      the exploit was vulnerable to any APP with WRITE_EXTERNAL_STORAGE permission. Any app with the name com.epicgames.fortnite could have been downloaded an installed via that. It did not have to come from a hijacked access point. It was mostly a glorified permissions issue.

      Again, no PR attack, just them following their procedures and being responsible.

      --
      When you cant win, ad hominem.
    7. Re:Reverse Engineer by thaylin · · Score: 1

      The patch downloader had ALREADY been distributed, not *being*. and that is not what is meant by "mitigating procedures" I dont know of a reporting company in the world who would say, "well you released a patch, no need to release the details", they all do, all that holding it does is lead to more exploits by people who figure the issue out.

      --
      When you cant win, ad hominem.
    8. Re:Reverse Engineer by Tough+Love · · Score: 1

      The patch downloader had ALREADY been distributed, not *being*

      Where did anybody say that the patched downloader had been completely distributed. Oh right, you made that up. You do understand that the more Google apologists spin this pout with their lame deflections, the longer is stays in view and the worse it looks for Google. don't you? Of course you do. Carry on.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    9. Re:Reverse Engineer by Luthair · · Score: 1

      What mitigation procedure was that, hoping users launch Fortnite at some point? The active player base of fortnite assuredly launches the game more than once a week, disclosing the vulnerability protects the people who have it on their phone and never launch it as they don't have, and may never have the patch installed otherwise.

    10. Re:Reverse Engineer by thaylin · · Score: 1

      Actually from a security standpoint it makes them look good. I am anot a Google apologist, but I am also not a google hater. just because you dont understand how security works does not mean I have to be just as ignorant.

      --
      When you cant win, ad hominem.
  19. You're confusing facts vs wishes by raymorris · · Score: 1

    Gp stated correctly that this serious vulnerability would not have existed had Epic not insisted that users disable security protections. That's a fact. Not a wish, not a "best possible future", but a simple fact.

    Kinda like the fact that all your money you've been paying into Social Security is gone. It's been spent. It's not sitting there waiting for you to get it when you're older. Wishing things were different doesn't change the facts.

  20. Re: Irresponsible Epic released vulnerable code. by barc0001 · · Score: 1

    I don't think this bug was in Android. I said that Google distributes Android. Totally separate pieces of information. I then added my opinion that Epic is for their own enrichment opening up additional security holes in a very irresponsible fashion.

  21. Re: Irresponsible Epic released vulnerable code. by Zmobie · · Score: 1

    I see two major problems with your argument. First, Android is supposed to be open source/marketed as being the open platform, but the practices of Google are really counter to this. Normally I don't care to get into the pissing matching between companies (frankly I don't care if the companies kill each other usually), but these particular pissing matches are actually harming consumers. Then, Google is intentionally distributing Android with some built in dark patterns to scare users into only being comfortable with using Google Play where they get a large cut of profits for very little work. I mean they didn't even put that much work into Google Play to start. I don't mind them taking some profit as that is how the Android Platform is monetized and allows it to be freely distributed, but they literally take more money than these companies are taxed. Something is pretty wrong with that picture.

    On top of that, they have taken great pains to prevent other stores from taking much hold or allowing for simplified individual distribution to the Android platform in any way. Imagine the uproar if Microsoft did this with Windows. Epic did take a risk for this business decision and definitely fucked up with the execution, but Google is doing some real shady shit now and straight up trying to punish them. This is some fucking mob tactics to keep anyone else from doing the same and them losing the stranglehold on their distribution monopoly. This behavior is NOT good for consumers at all and honestly, pretty unfair to businesses and developers too.

  22. Spite by Tough+Love · · Score: 1

    Google jumped at the chance to punish out of spite, because Epic chose to operate its own store. This is how it looks.

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  23. Re: Irresponsible Epic released vulnerable code. by barc0001 · · Score: 1

    The problem with your arguments are you're applying expectations of open-ness for PC OSs to the mobile phone market. You complain that:

    > On top of that, they have taken great pains to prevent other stores from taking much hold or allowing for simplified individual distribution to the Android platform in any way. Imagine the uproar if Microsoft did this with Windows.

    We're not talking about Windows, Android's main competitor is Apple's IOS. How's Android look compared to that? How are those IOS competitors to the App Store there doing? Exactly.

    > First, Android is supposed to be open source/marketed as being the open platform,

    And it is. To MANUFACTURERS. It's a packaged OS that anyone who wants to build a device around can do so. Your disconnect is you are conflating how Android is considered an open platform to how Linux is on the X86 space.

    > Epic did take a risk for this business decision and definitely fucked up with the execution, but Google is doing some real shady shit now and straight up trying to punish them.

    And I disagree. Google put a mechanism in for experienced users to be able to load an untrusted .apk file with the expectation that only people who understood the ramifications of doing so - i.e. so called "power users" - would use it. And now Epic's told everyone and their grandma to allow untrusted .apks to be installed on their phones. Epic is the party saying "Google wanted a cut of our cash flow so we're just gonna tell everyone to toss out a basic security feature of Android so we can make some more money!"

  24. Re:Google petty AF by Orphis · · Score: 1

    There are file managers with recent Android.
    Maybe older ones as well, it probably depends on the phone maker too (my Galaxy S4 had one bundled from Samsung for example).

    Admittedly, the issue with large APKs is that you need double the space. First to download and then to install the files. That's why so many games are using installers (though usually done downloading private files in the main game, not as a separate app).

  25. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  26. We need standards for this by MobyDisk · · Score: 1

    Everybody has their own rules and guidelines around responsible disclosure. We need an organization like like the IEEE or ACM or CERT to make standard practices for this. This is important because there is always a question of liability. I'd like to know that if I followed the IEEE rules for responsible disclosure that I can be reasonably sure that someone can't sue me.

  27. Re:Google is butthurt by Tough+Love · · Score: 1

    epic is make billions off this game and they don't get any

    Not true. A popular game makes the Android platform more popular, sells more handsets, and enlarge Google's walled garden of services from which it derives advertising income.

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  28. Re: Irresponsible Epic released vulnerable code. by Zmobie · · Score: 1

    The problem with your arguments are you're applying expectations of open-ness for PC OSs to the mobile phone market.

    While true, why should they be applied different? Phones are just mini computers and in many cases people use them as their main computer anyway. The only reason the markets are treated differently in that regard is the companies behind the major developments engineered the market that way. It was a much more organic process with PCs originally and they were not able to force-feed consumers their own ideas with as much success (Plus as much as I dislike Torvalds, Linux gave a big middle finger to closed platform usage in the early days).

    We're not talking about Windows, Android's main competitor is Apple's IOS. How's Android look compared to that? How are those IOS competitors to the App Store there doing? Exactly.

    Apple is just as guilty if not more. The argument that "It isn't as bad as they other guy" is still weak. Using a more extreme example would be, "I'm not so bad, I only beat that guy into a state or paralysis/coma, while that guy beat another to death!" Neither one is right, just less wrong...

    And it is. To MANUFACTURERS. It's a packaged OS that anyone who wants to build a device around can do so. Your disconnect is you are conflating how Android is considered an open platform to how Linux is on the X86 space.

    When they came up with it originally they tried to compare it in much the same way as the Windows/Linux relationship, but they became very dissatisfied with the fragmentation of the market. While the Android One development has helped Android beat Apple they also used that initiative to solidify some monopolies within the platform. Google Play is the lynch pin to that monopoly. Companies can't even branch Android effectively and reach a decent market because of Google's policies with it and their is no real alternative market.

    And I disagree. Google put a mechanism in for experienced users to be able to load an untrusted .apk file with the expectation that only people who understood the ramifications of doing so - i.e. so called "power users" - would use it. And now Epic's told everyone and their grandma to allow untrusted .apks to be installed on their phones. Epic is the party saying "Google wanted a cut of our cash flow so we're just gonna tell everyone to toss out a basic security feature of Android so we can make some more money!"

    I'll give you that Epic did take a big risk in using that to accomplish this, but why exactly should Google have such a monopoly on the distribution of software to the phones? Same with Apple. It creates a serious pay to play scenario that isn't really different than the spirit of net neutrality. Google is trying to force people to access the consumers through them for a hefty fee. It is a "security feature" but it is also a digital bouncer for Google. Why can't they provide a more secure way for independent market places or developers to distribute apps? Simple, profit. They stand to make nothing and even lose their monopoly if they did that. If they really cared about users as much as they claim this would already be standard just like software security certificates and dll signing.

  29. There are no right sides here. by Dagmar+d'Surreal · · Score: 1

    It's very simple, and it's not what this headline says.

    Epic decided to forgo the Play Store for releasing Fortnite.

    Google said "Okay, but this sort of thing can make our platform less secure. Be careful out there."

    Epic releasesd an installer for Fortnite that could install Fortnite without the Play Store.

    Google looks at it, and sees that it can be used to install more than just Fortnite, because it contains some stupidCode that can be used to install all sorts of malicious things because someone at Epic was very careless.

    Google tells Epic about this lame bit of coding, and tells them they've got seven days to fix it because it would be really, really bad if this were exploited by someone who wanted a whole lotta phones on their DDoS botnet (for example).

    Epic says "We believe we have 90 days to fix it" and releases a new installer without the stupidCode in it.

    Seven days goes by, Google releases details of the stupidCode so that other people can learn from and not make this same foolish mistake.

    Epic throws a tantrum.

    The TL;DR is that this wouldn't have been a problem if someone at Epic hadn't decided to just throw an installer out there without looking at it carefully first, and Google probably should have given them 30 days instead of 7, but probably gave them only seven days because it lets them reinforce their point that poorly-written third-party installers are bad. Epic gave them reason to do that when they started talking to the press and basically whining about the Play Store cut as if Google did nothing to deserve any money (because it's so obviously both easy and free to build and maintain a giant marketplace with some semblance of standards), and Google appears to have noticed that if they ignore the tall tales "web reporters" spin, they eventually wind up having to explain complex concepts to state Senators and that tends to be very expensive.

  30. Re:Google is butthurt by Tough+Love · · Score: 1

    Reading comprehension issues? OP wrote "don't get any". Now you are arguing a fallback. Suit yourself, Google still looks like shit over this and you know it.

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  31. Pay/Non-play, a choice not a technical issue by perpenso · · Score: 1

    Google can do that for Play apps. This whole pissing match started because Epic decided NOT to publish Fortnite on the Play Store.

    If they can remove a Play app then they can remove a non-Play app. They may not do so currently but that is a choice not a technical issue.

  32. Re:Google petty AF by volodymyrbiryuk · · Score: 1

    Don't clear the notifications then. It's not that difficult. Epic could have made an instruction how to install an APK. Doesn't Android have a built-in file manager anyway?

    --
    sudo rm -r -f --no-preserve-root /
  33. Re:Google is butthurt by thaylin · · Score: 1

    if by "looks like shit" you mean looks responsible, you are correct.

    --
    When you cant win, ad hominem.
  34. childish of google by SuperDre · · Score: 1

    That's really childish of google, especially as Google is only using the 7 day deadline when it's due to a security risk if it's already being actively misused, but it isn't. Normally they have 90 days (or sooner if they notice it being actively being misused).
    So why did they release it with the 7 day deadline? well we all know why...

    1. Re:childish of google by thaylin · · Score: 2

      Actually the policy says 7 days after a patch has been released, not if being misused, that is their policy.

      --
      When you cant win, ad hominem.
  35. Re:Google is butthurt by Tough+Love · · Score: 1

    So your new fallback argument is "shit is not shit". Nice.

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  36. Literally by cigawoot · · Score: 1

    > we worked around the clock (literally) to fix it

    So they put a clock in the middle of the room and arranged their desks around it?

  37. Re: Irresponsible Epic released vulnerable code. by viperidaenz · · Score: 1

    Fucked up like an amature.

    And their reason for doing this is because they want to handle the in-app purchases themselves to make more profit.
    So they can't write a secure installer and we're expecting them to securely handle peoples credit card information?

  38. Re: Irresponsible Epic released vulnerable code. by viperidaenz · · Score: 1

    Google don't take all of the 30% for themselves. You can get Visa et all will be getting a decent cut of that.

  39. Re: Irresponsible Epic released vulnerable code. by viperidaenz · · Score: 1

    Don't forget Epic also continued to say ".... and on top of that, we're telling them to install an app with a massive security hole in it"

  40. Re: Irresponsible Epic released vulnerable code. by farble1670 · · Score: 2

    It's not Google's responsibility to announce the vulnerability, either. They choose to do so, nobody is forcing them.

    It's only their responsibility if you assume they have an interest in protecting the security of their users.

    Are you for bug disclosures or against them? There is / was a serious security issue w/ the Epic installer. Bug disclosures are a Good Thing. We are all better off for them. Attributing malice to the action doesn't change that fact.

    Unless you are looking for a reason to bash Google. If so, disregard the above.

  41. Re: Irresponsible Epic released vulnerable code. by barc0001 · · Score: 1

    >> We're not talking about Windows, Android's main competitor is Apple's IOS. How's Android look compared to that? How are those IOS competitors to the App Store there doing? Exactly.

    > Apple is just as guilty if not more. The argument that "It isn't as bad as they other guy" is still weak. Using a more extreme example would be, "I'm not so bad, I only beat that guy into a state or paralysis/coma, while that guy beat another to death!" Neither one is right, just less wrong...

    I think that's a bit of hyperbole. The default position on apps from phones always was "work with what the manufacturer makes available for purchase on the store or hack your phone. Period". Apple stepped in and let people develop (for a fee) free apps in addition to paid ones, but the single point of distribution was and is the App Store. Android was the very first OS that even gave you the option to sideload .apk files without having to screw with a PC like PalmOS on the Treo. You're angry that it wasn't as open as the PC world. That wasn't ever in the cards.

    > I'll give you that Epic did take a big risk in using that to accomplish this, but why exactly should Google have such a monopoly on the distribution of software to the phones?

    Because they make the software that runs the phones? If you don't like it, go get a different phone, or write your own software for the phone. Or if you don't want to do that, go get a Tizen or Plasma Mobile compatible phone, overwrite the stock Android with that and have at it. I mean sure, Tizen's riddled with security holes and Plasma only works on a couple of Android devices but baby steps.

    > Why can't they provide a more secure way for independent market places or developers to distribute apps? Simple, profit. They stand to make nothing and even lose their monopoly if they did that.

    You're right. They stand to make nothing. And they risk introducing instability. So why on God's Green Earth would they? Do you do extra work for free that might cause you more problems in your day job? I don't. Why would they?

  42. Re: Irresponsible Epic released vulnerable code. by Zmobie · · Score: 1

    I think that's a bit of hyperbole. The default position on apps from phones always was "work with what the manufacturer makes available for purchase on the store or hack your phone. Period". Apple stepped in and let people develop (for a fee) free apps in addition to paid ones, but the single point of distribution was and is the App Store. Android was the very first OS that even gave you the option to sideload .apk files without having to screw with a PC like PalmOS on the Treo. You're angry that it wasn't as open as the PC world. That wasn't ever in the cards.

    Again though, my point is why? The only reason that is not in the cards is simply because they artificially made it that way.

    Because they make the software that runs the phones? If you don't like it, go get a different phone, or write your own software for the phone. Or if you don't want to do that, go get a Tizen or Plasma Mobile compatible phone, overwrite the stock Android with that and have at it. I mean sure, Tizen's riddled with security holes and Plasma only works on a couple of Android devices but baby steps.

    Up front I buy that they have some rights to that somewhat due to investment and such, but even though you don't want to accept the comparison to the PC market (for some reason) we already went through this with Microsoft and it was ruled they should not/do not have unilateral authority over something like this. There is an inherent risk when a company puts out more than a product and they are actually creating an ecosystem and/or market. Once they venture into those realms they don't get to dictate to the consumer and businesses within that marketplace everything about that market. If they did we would have a pure oligarchy develop in every country that attempted to create a capitalist system.

    You're right. They stand to make nothing. And they risk introducing instability. So why on God's Green Earth would they? Do you do extra work for free that might cause you more problems in your day job? I don't. Why would they?

    Instabliity? No. This stuff is not any more unstable than what is going to run on a normal PC. These things are not magic and Google Engineers are not wizards. They are mini PCs with a different Operating System and built on the same principles as everything else. That is just business talk bullshit that no engineer in their right mind is going to accept and honestly neither should the consumers.

    Beyond that, as far as making a better side-loading mechanisms, I refer you to my previous point that when they created a marketplace they gave up some of the unilateral authority. Even if they were allowed that, they shouldn't be/have been acting like it is this huge open and free platform. They know it was misleading to people, but thought no one would notice or care on the consumers side if they were only taking advantage of the developers and businesses. To their credit sadly, they are right and most people don't care or notice. The backwards part is the consumers are either literally paying for it in higher costs for the software or indirectly paying for it due to lower quality work.

    Bottom line, I have absolutely no issue with them making money for what they do. Everyone has that right and that is how the system works, but they are outright gouging and taking advantage of a monopoly that they intentionally created.

  43. Google has never done this to Amazon. by emil · · Score: 1

    Lots of people install the Amazon App Store and pay for games through that source.

    It does appear that Google wanted to make an example of Epic specifically, in the hopes that more app developers will be cautious to follow.

  44. Re:Google is butthurt by Anonymous Coward · · Score: 1

    epic is make billions off this game and they don't get any

    Not true. A popular game makes the Android platform more popular, sells more handsets, and enlarge Google's walled garden of services from which it derives advertising income.

    Why does it make the Android platform more popular? That popular game is already available on all other platforms.

    And you really think they aren't butthurt about not being able to take a 30% cut of the profits of one of the world's most popular and profitable games on their platform? Really? Come on.

  45. Re: Irresponsible Epic released vulnerable code. by barc0001 · · Score: 1

    > You're angry that it wasn't as open as the PC world. That wasn't ever in the cards.

    > Again though, my point is why? The only reason that is not in the cards is simply because they artificially made it that way.

    Because a phone is not a computer. It's a phone. And it's subject to some incredibly strict regulations that computers are not subject to surrounding many things, including the availability of the device to call and stay in contact with emergency services, for example. Google, Apple, and others have to abide by these rules, and part of that is mitigating risk of malware rendering the phones unable to contact those services. Can you imagine the shit show that would entail if half the Android phones in the US couldn't call 911 due to a malware infection? Or worse, half the android phones called 911 ALL AT ONCE due to a malware infection?

    That is one reason they have to do their damndest to maintain a level of security over their devices and that means playing gatekeeper as much as possible. And at the end of the day it's their ass on the line. If the phone gets hacked people are going to blame Google, not Epic.

  46. Re: Irresponsible Epic released vulnerable code. by Zmobie · · Score: 1

    That's a cop out though. Google assumed their own risk by getting into the market and turning the phones into a computer just like Epic assumed risk buy using their own installer. And if Epic created the vulnerability you damn right they are going to be held responsible for that. Microsoft isn't held accountable for Adobe putting garbage software on their platform.

    This is a platform. They are computers with telephony functions. I really don't understand why you want to give them a pass based on some idea that they are some how different, but you're clearly not going to agree with me nor I with you. You're entitled to your own opinion but we're rehashing now and not really contributing to a productive discussion at this point.

  47. Re:Google is butthurt by Tough+Love · · Score: 1

    you really think they aren't butthurt about not being able to take a 30% cut of the profits of one of the world's most popular and profitable games on their platform?

    Nice strawman, I did not say any such thing.

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  48. Re:Google is butthurt by Tough+Love · · Score: 1

    so why do they take 30% of profit from the apps on the play store then? they should be doing that for free for the reasons you just stated.

    Great point, and one not missed by antitrust regulators, particularly in Europe and Asia. Apple needs to worry about this too, and Apple shareholders for that matter.

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  49. Re: Google is butthurt by Tough+Love · · Score: 1

    If more developers start skipping the Google Play store, Google could lose control of Android (the control it imposes via the store and Google services) and Android *actually* becomes free open-source. They clearly don't want that.

    Obviously not, but in the long run it is inevitable and most probably, Larry and Sergey already understand this. They will continue to rake in the 30% gravy while they can, but they will not make the mistake of trying to defend that windfall margin to the point that it brings in the regulators or the forks.

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  50. Re: Irresponsible Epic released vulnerable code. by easyTree · · Score: 1

    +1 interesting

  51. Epic done fucked up by mykro76 · · Score: 1

    Whoops Tim. Only a few weeks ago you told Forbes:

    Avoiding the 30% “store tax” is a part of Epic’s motivation. It’s a high cost in a world where game developers’ 70% must cover all the cost of developing, operating, and supporting their games. And it’s disproportionate to the cost of the services these stores perform, such as payment processing, download bandwidth, and customer service. We’re intimately familiar with these costs from our experience operating Fortnite as a direct-to-customer service on PC and Mac.

    You forgot about some other services performed by the Play Store. Automated analysis of your code for security issues. Automated roll-out of your updates to users. And in some cases - for very serious bugs - even forcing your updates onto users.

    And now you're crying foul because you got greedy, forced your users to bypass Android's security mechanisms and now you don't have a way to get a fix to them within seven days. LOL.

  52. Re: Irresponsible Epic released vulnerable code. by barc0001 · · Score: 1

    > That's a cop out though. Google assumed their own risk by getting into the market

    > This is a platform. They are computers with telephony functions.

    You have that backwards. They are a telephone run by a computer. It's not a cop out, it's a very real risk they have to mitigate. As I pointed out, Android is the only environment that even goes this far to be "user friendly" toward unvetted apps. If you're looking for an open platform, go look somewhere else because you'll never find it on a phone. You're correct, we're seeing this from different perspectives and won't be meeting in the middle.

  53. Re: Google is butthurt by Zero__Kelvin · · Score: 1

    F-Droid has been around for quite some time. You can use it so they haven't stopped you at all. Most consumers don't want to be bothered; they want and like the Play centralized repository. Sure Google takes a cut, but they provide added value and the insinuation to the contrary is disingenuous. Finally it is the OS not the apps that are open source so you are conflating two separate issues.

    --
    Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
  54. Re: Irresponsible Epic released vulnerable code. by Megol · · Score: 1

    Google doesn't distribute Android? When did that happen?

    When the distribution wasn't referring to Android but the code that was buggy - which Epic designed and wasn't distributed by Google. If that's not confusion it's a changing of goalposts strategy trying to hide the problem this article claim exists: that of Google being irresponsible opening up for Android users to be targeted.

    The rest of your comment is largely irrelevant and claiming that Epic is irresponsible is something I'd expect of a Google investor or fanboy(do they still exist?) - so exactly what is your relation to Google?