Man the things these people can do are simply amazing. Their understanding of the internal system processes from nothing more than an external view is literally incredible.
I think Austin is stating Samsung isn't Google. Samsung's internet browser has nothing to do with Google. You're entire quote was about Samsung, not Google.
[doublepost=1509570533][/doublepost]There was quite a bit of action prior to the contest, as Apple, Google, and Huawei all released last-minute patches in the middle of the night.
You messed up. We understand. Google can patch all they want, Samsung is not google. Your quote is about Samsung.
Look, it's okay. You don't have to backtrack. You made a mistake.No it wasn't. Literally the first sentence I quoted says otherwise. Here, let me quote it again:
[doublepost=1509570533][/doublepost]
I quoted two things, the first of which clearly references Google, and the second of which most likely refers to a Google issue.
Look, it's okay. You don't have to backtrack. You made a mistake.
Samsung got hacked, Apple got hacked. You're replying to a report about Google being unhackable with a post about Samsung. If it makes you feel better, all mobile OSs can be hacked.
I'm agreeing with you, but your reasoning is just bad.Your mental gymnastics are adorable.
Are you sure it's the same thing? This doesn't mention WPA2 exploitWhat an irrelavant and pointless comment.
On a more relevant note. This exploit has been fixed in the new update.
Inappropriate and unnecessary.Would these security researches tell Tim cook that getting rid of touch ID was retarded?
I'm agreeing with you, but your reasoning is just bad.
The Pixel had a better go at it. That's all.
Are you sure it's the same thing? This doesn't mention WPA2 exploit
And just to confirm – yes, we updated our iPhone targets to iOS 11.1 prior to the contest.
Apple's iPhone 7, running iOS 11.1, the latest version of the iOS 11 operating system, was successfully breached twice by Tencent Keen Security Lab.
On a more relevant note. This exploit has been fixed in the new update.
You presumably have a job which might rely on digital communication. You also might use your phone to communicate with other people in your life. While security is not important to you, some of the people you talk to might appreciate a basic passcode so not literally everyone can look through your phone. This is the equivalent of leaving your front door open because "meh I don't have valuables anyway". If you can't be bothered to enter a 4 or 6 digit code or literally place your finger for a split microsecond, that's concerning.All this while I'm trying to turn off passcode and fingerprint unlock features on my phone as they are tiresome to me. I appreciate all of the security features and respect for privacy. But in reality, by not using Apple Pay or digital payments I have nothing to hide on my phone. Which is also why a $1,000 iPhone with a camera to take selfies has no appeal to me.
No there isn't.Is there an iOS 11.1.1 update out already?
All this while I'm trying to turn off passcode and fingerprint unlock features on my phone as they are tiresome to me. I appreciate all of the security features and respect for privacy. But in reality, by not using Apple Pay or digital payments I have nothing to hide on my phone. Which is also why a $1,000 iPhone with a camera to take selfies has no appeal to me.
I don't know why this is so difficult for you to understand. There's nothing wrong with your device and all these devices can be hacked.OK, I'll ask one final time:
- if Google isn't affected, why did Google, according to the article, rush to release a patch? Better question: why didn't Apple patch?
- are you asserting that Samsung's browser: a) has holes of its own that were never in Google's code in the first place, b) has holes that have since long been fixed upstream, or c) may in fact quite likely have holes that are also found on Google's end? Samsung's browser likely opens security holes in the OS through supported features.
It isn't SoApple is wrong.Are you sure it's the same thing? This doesn't mention WPA2 exploit
Your post takes a disingenuous turn towards FUD. You can't seriously posit a messed up - I don't know what to call it, but it definitely ain't chili cuz chili don't have beans in it. Your "guess" is full of beans. You didn't even try to make a logical leap. You just jumped from it's based on Chromium (it is) therefore the bugs in Sammy's browser stem from issues with Google.I see nothing in that post to suggest that Google's code wasn't affected, and enough to suggest that it was, in fact, affected, namely the assertion that Google "released a last-minute patch in the middle of the night".
While it's possible that Samsung's browser, which surely is forked from Google's Chromium and/or heavily uses Google's Blink, uses outdated components that have long since been fixed upstream, or has issues that never existed upstream in the first place, clearly there were bugs on Google's end.
So in essence you're asking @AustinIllini to prove your supposition? That's pretty rich. How about you provide evidence that even comes close to corroboration. You threw out the claim.OK, I'll ask one final time:
But please, keep not responding to that.
- if Google isn't affected, why did Google, according to the article, rush to release a patch?
- are you asserting that Samsung's browser: a) has holes of its own that were never in Google's code in the first place, b) has holes that have since long been fixed upstream, or c) may in fact quite likely have holes that are also found on Google's end?
Your post takes a disingenuous turn towards FUD. You can't seriously posit a messed up - I don't know what to call it, but it definitely ain't chili cuz don't have beans in it. Your "guess" is full of beans. You didn't even try to make a logical leap. You just jumped from it's based on Chromium (it is) therefore the bugs in Sammy's browser stem from issues with Google.![]()
There couldn't have been issues with Sammy's fork? It had to be an issue with Google? You're basing this on...
Trying to conflate Samsung's exploit with an exploit against Google is just plain dishonest and really not worth much discussion.
All this while I'm trying to turn off passcode and fingerprint unlock features on my phone as they are tiresome to me. I appreciate all of the security features and respect for privacy. But in reality, by not using Apple Pay or digital payments I have nothing to hide on my phone. Which is also why a $1,000 iPhone with a camera to take selfies has no appeal to me.
Exactly. If it’s that easy then why is the government so hell bent on getting back doors in these platforms?
You don't have any e-mail on your phone? No contacts? No calendar appointments?
No social networking accounts?
Even if you don't feel that's private information, your contacts might be quite angry by the nonchalant way you're exposing their address information.
You presumably have a job which might rely on digital communication. You also might use your phone to communicate with other people in your life. While security is not important to you, some of the people you talk to might appreciate a basic passcode so not literally everyone can look through your phone. This is the equivalent of leaving your front door open because "meh I don't have valuables anyway". If you can't be bothered to enter a 4 or 6 digit code or literally place your finger for a split microsecond, that's concerning.