WHO EVER THOUGHT THIS MIGHT HAPPENhttps://www.androidcentral.com/epic-games-first-fortnite-installer-allowed-hackers-download-install-silently …
-
Show this thread
-
-
Replying to @syvergy @JamesPinnell and
Did you see Tim's response? He said that he feels Google chose to release details of the exploit publicly as a direct attack on Epic's approach to android distribution. Like, duh, of course google are going to publicly decry your dangerously high profile attack on their system.
2 replies 2 retweets 14 likes -
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.
14 replies 1 retweet 29 likes -
Replying to @TimSweeneyEpic @manfightdragon and
We asked Google to hold the disclosure until the update was more widely installed. They refused, creating an unnecessary risk for Android users in order to score cheap PR points.
26 replies 5 retweets 41 likes -
I saw your words on the linked article, and I agree that that is likely 100% why they chose to go public so fast. I'm just not surprised they did. It's a shame that your software had an issue, and it's a shame that Google were able to run with that.
1 reply 0 retweets 4 likes -
Replying to @manfightdragon @TimSweeneyEpic and
Just try to acknowledge that it was actually your software that put users at risk, not Google.
1 reply 0 retweets 23 likes -
Yes, Epic is responsible for security flaw and, as I communicated to the
@AndroidCentral folks, we’re grateful that Google did the in-depth security analysis of Fortnite and reported the flaw to us.2 replies 0 retweets 8 likes -
Replying to @TimSweeneyEpic @JamesPinnell and
Did Google ever give you a reason for ignoring the standard 90 wait? I can't imagine whatever they had to say would look good for them.
1 reply 0 retweets 1 like
Sadly no. See the full thread here, which Google made public: https://issuetracker.google.com/issues/112630336 …
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.