Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.

No it wasn't. Literally the first sentence I quoted says otherwise. Here, let me quote it again:

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.
[doublepost=1509570533][/doublepost]
You messed up. We understand. Google can patch all they want, Samsung is not google. Your quote is about Samsung.

I quoted two things, the first of which clearly references Google, and the second of which most likely refers to a Google issue.
 
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.

The Pixel had a better go at it. That's all.

OK, I'll ask one final time:

  1. if Google isn't affected, why did Google, according to the article, rush to release a patch?
  2. 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?
But please, keep not responding to that.
[doublepost=1509570871][/doublepost]
Are you sure it's the same thing? This doesn't mention WPA2 exploit

Yeah, no, these exploits clearly have not been fixed in 11.1, as the article states that the tests were run in 11.1:

And just to confirm – yes, we updated our iPhone targets to iOS 11.1 prior to the contest.
 
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.
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.

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.
 
OK, I'll ask one final time:

  1. if Google isn't affected, why did Google, according to the article, rush to release a patch? Better question: why didn't Apple patch?
  2. 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.
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.
 
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.
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.o_O There couldn't have been issues with Sammy's fork? Their optimizations? It had to be an issue with Google? You're basing this on...

I think you mean to say you saw nothing in that post to suggest that Google's code WAS affected. Exploits pay. As far as has been reported, there were no exploits on Google. Trying to conflate Samsung's exploit with an exploit against Google is just plain dishonest and really not worth much discussion.
[doublepost=1509571595][/doublepost]
OK, I'll ask one final time:

  1. if Google isn't affected, why did Google, according to the article, rush to release a patch?
  2. 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?
But please, keep not responding to that.
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.
 
Last edited:
They still need to connect to their wifi network. I dont see that happening on a stolen iphone 7.
 
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.o_O

I didn't make that leap at all; I asked.

There couldn't have been issues with Sammy's fork? It had to be an issue with Google? You're basing this on...

There had, indeed, to be an issue on Google's end, because, for the umpteenth time, Google issued a patch.

Trying to conflate Samsung's exploit with an exploit against Google is just plain dishonest and really not worth much discussion.

The only reason I conflated Samsung and Google is that Google was not separately tested. Instead, various Android-based devices were, among them one from Samsung. Given that, as you acknowledge, Samsung's browser is based on code by Google, and that Google issued a patch, I posited the possibility (if not strong likelihood) that this Samsung flaw is in fact, in part, on Google's end.

I mean, either that, or was being "plain dishonest". ¯\_(ツ)_/¯
 
Tests like these prove a basic fundamental truth about software, which is that there will always be bugs/exploits.

And this is why Android is an utter joke compared to iOS. Google can patch bugs all they want and post the updated code to AOSP, but if the OEM never downloads the code and issues an update then it’s meaningless.

If a tree falls in the forest.....
 
  • Like
Reactions: bmot and spinnyd
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 am guessing you don’t care about your digital footprint? The various network credentials you have stored on the phone? Your banking info stored in iCloud.

There is a lot more info you need to guard that can be damaging to you than access to digital payments.
 
What are “master of pwn points”? Are they like Chucky cheese tokens and once you get enough you can redeem them for prizes?
 
  • Like
Reactions: spinnyd
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.

I have two phones. One for work which needs to be locked and one for personal which if I could, I would own a Moto Razr and disconnect from a lot of the mobile distractions. I do have social networking accounts though I deleted them from my phone to be more responsible with my time. I only check them on the weekends or during breaks at work. My point was more to me not needing the 4 or 5 digits pass codes and fingerprint feature. I've gone years without it but lately it seems that everyone now has "vital" information on their phone that the neighbor is going to steel. I get Wi-Fi hacks and what not but I am referring the daily tasks on my phone. Every single time I get a notification I have to unlock the phone. You can't set the lock time outside of immediately in settings anymore.
[doublepost=1509573431][/doublepost]
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.

Uh, no it's not the equivalent. A person looking through my phone for digital assets such as a picture or a contact versus letting a person in my house for physical assets across a much broader spectrum are entirely different. Wi-Fi standards, digital currency, etc. I get it. But aside from your credit card info please tell me what your common everyday thief is going to steel from your phone that is of value? Your text messages, your music, take a selfie and post it to Facebook?

And as mentioned in another reply, "I have two phones. One for work which needs to be locked and one for personal which if I could, I would own a Moto Razr and disconnect form a lot of the mobile distractions. I do have social networking accounts though I deleted them from my phone to be more responsible with my time. I only check them on the weekends or during breaks at work. My point was more to me not needing the 4 or 5 digits pass codes and fingerprint feature. We've all gone years without it but lately it seems that everyone now has this vital information on their phone that the neighbor is going to steel. I get Wi-Fi hacks and what not but I am referring the daily tasks on my phone."
 
  • Like
Reactions: DoctaThompson
Great... so if I updated from iOS 10 to 11.1 it would benefit me zero. I'll stay on 10 then.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.