Can't I manually take from my ios7 device those certificate and copy paste to my ios5/6 device ?
Did anyone research this ? Is this possible ?
Did anyone research this ? Is this possible ?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS 6 Users on Devices Able to Run iOS 7 Must Upgrade to Fix FaceTime
- Thread starter MacRumors
- Start date
- Sort by reaction score
Tried to FaceTime my mom today
I just found about this today and am a little late to the party.
I find the tribal "just upgrade the iOS to 7" responses very interesting. Why are people passionate about what other people do with their phone?
I love my iPhone, but this is the kind of thing a company does that is turning a corner. This is the kind of awful customer service that will push me, and my mom who I convinced to buy an iPhone, to defect. I choose Apple for a higher level of software and product. This kind of crap removes all incentive to pay a premium.
Sad day Apple. You don't make me upgrade my Mac to get a bug fix after one year - but I have to update my pocket computer Very disappointed.
I just found about this today and am a little late to the party.
I find the tribal "just upgrade the iOS to 7" responses very interesting. Why are people passionate about what other people do with their phone?
I love my iPhone, but this is the kind of thing a company does that is turning a corner. This is the kind of awful customer service that will push me, and my mom who I convinced to buy an iPhone, to defect. I choose Apple for a higher level of software and product. This kind of crap removes all incentive to pay a premium.
Sad day Apple. You don't make me upgrade my Mac to get a bug fix after one year - but I have to update my pocket computer Very disappointed.
It's hard to take anyone serious who interjects such a weird thought into an Apple discussion. I don't know whether to laugh because you must be an ignorant teenager or cry that there exist adults who have so little understanding of the world around them.
And I find the luddites on here very interesting. It's a bug, there is a free update available to fix it (and other serious security defects).
Nice jump to name calling, even before making any other relevant statements--the standard "go to for" weak or non-existent arguments. Especially so when you factor in that no one should really care what someone else might or might not want to have on their phone.
Yet another example of the collective being threatened by a non-conformist.
It would be nice to respect someone's desire to stay with a particular version of an operating system without taking it as a personal insult. It really is quite a puzzling response.
Ok, well, I'm not a teenager, and I'll wager I have taken more university level theological studies courses than the average university graduate.
Also, I didn't interject that, I was replying to the poster who did.
I'm sure you are of the opinion that many religions are inclusive by nature, but having done a large amount of undergraduate study and term papers on the subject, my opinion differs from yours.
In any case, way off topic and better discussed via PM if you would like to have your say on the matter.
It probably is possible in theory, but you'd be lying, and putting users you called with FaceTime at risk by providing a certificate that falsely reports that the security patch has been applied.
You'd basically be reporting a secure connection can be established when it in fact cannot be.
I don't want to be that person, but would it be ok to turn that question around to and ask how/why that doesn't matter?
I only ask because it seems pretty self evident that there is a real problem with wilfully broadcasting a secure connection that isn't?
From my understanding the certificate isn't the fix itself, it is just the "certification" that the security patch has been applied. Thus just forcing in a certificate that is accepted by the FaceTime check doesn't actually make the connection secure, it just tricks the software into thinking it is.
So what could happen because of that? I mean there's what it might sound/seem like, and then there's the reality, and I'm just trying to see what would be the actual reality of something like that as far as it relates to FaceTime.
Nothing if you only FaceTime in the security of your personal home network, and if the person you FaceTime with is also in a similar secure network.
If either party is on a public network or hotspot, different story. Sure the risk may be low, but how do you explain that to your Grandma when she answers your FaceTime call from StarBucks and and a week later her entire retirement savings is emptied out via her Paypal account?
Just because more people die of bee stings every hear than from being run over by a car doesn't mean you shouldn't look both ways when you cross the street, and certainly doesn't mean you should trick friends, family and acquaintances into believing that no cars are coming when there is a bus speeding right for the intersection they are about to cross.
It is that sort of irresponsible attitude towards security that predatory hackers thrive on.
I say do what you want with your own stuff, but don't put others at risk without their knowledge, that's just wilful negligence.
A patch is an update, though.
A third digit incremental release of iOS (such as 3.1.2 -> 3.1.3 or 7.1 -> 7.1.1) is equivalent to all the little updates that Microsoft releases on each Patch Tuesday (such as KB2964444) and also OS X Security Updates (such as 2014-001).
Updates are specifically created to fix problems. Refusing to install updates and then complaining about the problem that the update was created to fix is not Microsoft's problem. Nor is it Apple's or any other company's problem. It is the user or system administrator's problem.
in typical software world, Patches and Updates / Versions are not the same thing and often offer much different product support.
From a software company, there's a big difference.
For example, our version, 2014 gets 2 years of patches and support. Even when 2015 might be out, or 2016 is out. We do not say "oh, that bug is in 2014? guess you'll just have to upgrade to 2015/2016 now!" as long as the version is current life and support, patches that need to go out to recent supported version Also go out to previously still supported versions. if a bug is discovered in 2015 code, and 2012 is still in support cycle, that Patch should be backdated to go into those versions.
By doing this and stating "upgrade to 7", Apple has pretty much officially called an end to iOS6 support. While Apple is well within their right to do so, they are effectively calling EOL support, even though their current release is only 6ish months old.
From a software support perspective, that is absolutely abysmal length of support.
Would something like that truly be even a low risk item in a situation like that or basically a no risk item at all, especially on the recipient side of things, as something like that can't even happen in relation to using FaceTime (and having a potentially faked certificate on the sender's end)?
----------
A patch/update to a current version of OS is one thing, needing to upgrade to a whole new version to get a fix for a security issue (which was already fixed for your version, but just wasn't released to you), is a different thing.
Do you even realize how bad iOS4 performed on the iPhone 3G? I don't care what was fixed in iOS4, the update was definitely NOT worth the huge performance penalty.
Hahahaha... is it any wonder why people on this forum are bashed for succumbing to the Apple Reality Distortion field?
----------
So basically if an Apple update, that a user can't easily undo, significantly reduces performance just throw away your phone? Sounds like typical RDF.
First off you were complaining about your iPhone 3G and FaceTime not working if you were to update. Do you realize that phone doesn't even have a front facing camera? Complaining for the sake of complaining.
Lolz... you're clearly twisting others' words in your (pretty much hopeless) trying to justify Apple's anti-customer moves.
Actually, your previous answer at https://forums.macrumors.com/posts/19076788/ has clearly shown how blindly you're defending Apple.
FYI: he has NOT stated the 3G would run Facetime. He referred to the well-known fact the iPhone 3G as an example of Apple's forcing their customers to upgrade with absolutely hostile means like basically making a phone a paperweight.
The iPhone 3G which was running under iOS3 just fine, then, it was basically crippled with iOS4. Just an example: in Settings, opening "General" takes no less than 24 seconds under iOS4. Ridiculous...
Since I had already gotten an Android phone (LG G2) as a result of all of this iOS7 upgrade mess, I went ahead and upgraded my iPhone 4 just to see what 7.1.1 was like (I never planned to use the phone again as a phone anyway). As expected I hate the look, even after playing around with the settings for quite some time. Sorry Apple, I still like your computers but I expect that I have bought my last iPhone. You should take a very serious look at the way that you do iOS upgrades and allow at least a little flexibility. But do I expect that? Never!
So, there is still no sign of a class action lawsuit, like people were suggesting would happen? Just shows this really doesn't affect many people in the grand scheme of things.
You just forget that the vast majority of iOS users the tech illiterate people - basically, for whom anything released by Apple is sufficient, no matter how bad they are. They'll be the last to realize there could be other ways than the Apple way and, consequently, will never start a lawsuit.
iOS 6 Users on Devices Able to Run iOS 7 Must Upgrade to Fix FaceTime
I didn't forget anything. There were many in this thread that were adamant there was going to be a lawsuit. That was my point.
I didn't forget anything. There were many in this thread that were adamant there was going to be a lawsuit. That was my point.
Lawsuits, let alone class action ones, can and often do take at least some time, if not even a bit more than that, before they get even filed, so no real telling yet in relation to all of this.
That said, there's certainly something (similar/related) brewing already too: https://forums.macrumors.com/threads/1730855/