Jun 16, 2025
Оfftopic Community
Оfftopic Community
Forums
New posts
Search forums
What's new
Featured content
New posts
New media
New media comments
New resources
New profile posts
Latest activity
Media
New media
New comments
Search media
Resources
Latest reviews
Search resources
Members
Current visitors
New profile posts
Search profile posts
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Information & News
News
iPhone OS 3.1 Breaks MS Exchange On Older iPhones [IPhone]
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Geek" data-source="post: 1989671" data-attributes="member: 246624"><p><img src="http://cache.gawker.com/assets/images/gizmodo/2009/09/ehangebrok.jpg" alt="" class="fr-fic fr-dii fr-draggable " data-size="" style="" />To an email-syncing office drone with an iPhone 3G, this change looks like a bug. To an IT admin, this change actually looks like a bug<em>fix</em>. But no matter how you see it, Apple screwed up somewhere down the line.</p><p></p><p> Users are reporting that <a href="http://gizmodo.com/tag/iphone-3%271/" target="_blank">iPhone 3.1</a>, which just dropped <a href="http://gizmodo.com/5355752/iphone-os-31-is-live-itunes-app-management-mms-better-syncing" target="_blank">Wednesday</a>, won't sync with some Exchange servers—in particular, any that ask for full device encryption. Which quite a few do! Apple's <a href="http://support.apple.com/kb/TS2941" target="_blank">official note</a> on the change:</p><p></p><p style="margin-left: 20px"> iPhone OS (beginning with the <a href="http://gizmodo.com/tag/iphone-os-3%271/" target="_blank">iPhone OS 3.1</a> update) can enforce the Exchange ActiveSync mailbox policy requiring encryption on the device. If your Exchange Server administrator has selected this option, only devices that support device-level encryption are allowed to sync Mail, Contacts, and Calendars.</p> <p style="margin-left: 20px"></p> <p style="margin-left: 20px"></p><p>So in a direct way, the iPhone has actually <em>increased</em> Exchange support, in that it honors Exchange servers' requirements for device-level encryption, and won't connect if the device doesn't meet them. Since they don't support hardware encryption at all, the iPhone 2G and 3G can in no way meet these requirements, so blocking them from connecting is just good security policy. </p><p></p><p> Here's the problem: Before 3.1, firmwares just falsely reported that a user's iPhone supported device-level encryption. To frame this change as a bugfix is basically dishonest, since this "bug" was intentionally planted by Apple in order to rush full Exchange support out the door on devices that, by their very nature, can't have it. Now, anyone who bought an iPhone 3G under the (reasonable!) impression that they'd be able to use it to connect to their company's security-enabled Exchange server now can't. Oops? Sorry? Both? </p><p></p><p> Apple's solution: Convince your company to slacken its security demands, or just buy a 3GS. Thanks dudes,<em> I'll look into that. </em>[<a href="http://www.broadbandreports.com/forum/r22999133-iPhone-31-breaks-Exchange-Sync-for-pre3GS-phones" target="_blank">Broadband Reports</a> via <a href="http://www.tuaw.com/2009/09/10/iphone-os-3-1-now-enforces-exchange-encryption-policy-may-block/" target="_blank">TUAW</a> via <a href="http://www.appleinsider.com/articles/09/09/11/apple_plugs_loopholes_with_security_updates_in_iphone_os_3_1.html" target="_blank">AppleInsider</a>]</p><p></p><p> </p><p></p><p><a href="http://ads.pheedo.com/click.phdo?p=1" target="_blank"><img src="http://ads.pheedo.com/img.phdo?p=1" alt="" class="fr-fic fr-dii fr-draggable " data-size="" style="" /></a><img src="http://a.rfihub.com/eus.gif?eui=2226" alt="" class="fr-fic fr-dii fr-draggable " data-size="" style="" /><a href="http://feedads.g.doubleclick.net/~a/PCEI35SooDpRS0MT0w4utuGM0kk/0/da" target="_blank"><img src="http://feedads.g.doubleclick.net/~a/PCEI35SooDpRS0MT0w4utuGM0kk/0/di" alt="" class="fr-fic fr-dii fr-draggable " data-size="" style="" /></a></p><p><a href="http://feedads.g.doubleclick.net/~a/PCEI35SooDpRS0MT0w4utuGM0kk/1/da" target="_blank"><img src="http://feedads.g.doubleclick.net/~a/PCEI35SooDpRS0MT0w4utuGM0kk/1/di" alt="" class="fr-fic fr-dii fr-draggable " data-size="" style="" /></a></p><p></p><p><a href="http://feeds.gawker.com/~ff/gizmodo/full?a=3aHayAabG8E:o-kY_PjSdB4:H0mrP-F8Qgo" target="_blank"><img src="http://feeds.feedburner.com/~ff/gizmodo/full?d=H0mrP-F8Qgo" alt="" class="fr-fic fr-dii fr-draggable " data-size="" style="" /></a> <a href="http://feeds.gawker.com/~ff/gizmodo/full?a=3aHayAabG8E:o-kY_PjSdB4:yIl2AUoC8zA" target="_blank"><img src="http://feeds.feedburner.com/~ff/gizmodo/full?d=yIl2AUoC8zA" alt="" class="fr-fic fr-dii fr-draggable " data-size="" style="" /></a> <a href="http://feeds.gawker.com/~ff/gizmodo/full?a=3aHayAabG8E:o-kY_PjSdB4:D7DqB2pKExk" target="_blank"><img src="http://feeds.feedburner.com/~ff/gizmodo/full?i=3aHayAabG8E:o-kY_PjSdB4:D7DqB2pKExk" alt="" class="fr-fic fr-dii fr-draggable " data-size="" style="" /></a> <a href="http://feeds.gawker.com/~ff/gizmodo/full?a=3aHayAabG8E:o-kY_PjSdB4:V_sGLiPBpWU" target="_blank"><img src="http://feeds.feedburner.com/~ff/gizmodo/full?i=3aHayAabG8E:o-kY_PjSdB4:V_sGLiPBpWU" alt="" class="fr-fic fr-dii fr-draggable " data-size="" style="" /></a></p><p><img src="http://feeds.feedburner.com/~r/gizmodo/full/~4/3aHayAabG8E" alt="" class="fr-fic fr-dii fr-draggable " data-size="" style="" /></p></blockquote><p></p>
[QUOTE="Geek, post: 1989671, member: 246624"] [IMG]http://cache.gawker.com/assets/images/gizmodo/2009/09/ehangebrok.jpg[/IMG]To an email-syncing office drone with an iPhone 3G, this change looks like a bug. To an IT admin, this change actually looks like a bug[I]fix[/I]. But no matter how you see it, Apple screwed up somewhere down the line. Users are reporting that [URL="http://gizmodo.com/tag/iphone-3%271/"]iPhone 3.1[/URL], which just dropped [URL="http://gizmodo.com/5355752/iphone-os-31-is-live-itunes-app-management-mms-better-syncing"]Wednesday[/URL], won't sync with some Exchange servers—in particular, any that ask for full device encryption. Which quite a few do! Apple's [URL="http://support.apple.com/kb/TS2941"]official note[/URL] on the change: [INDENT] iPhone OS (beginning with the [URL="http://gizmodo.com/tag/iphone-os-3%271/"]iPhone OS 3.1[/URL] update) can enforce the Exchange ActiveSync mailbox policy requiring encryption on the device. If your Exchange Server administrator has selected this option, only devices that support device-level encryption are allowed to sync Mail, Contacts, and Calendars. [/INDENT] So in a direct way, the iPhone has actually [I]increased[/I] Exchange support, in that it honors Exchange servers' requirements for device-level encryption, and won't connect if the device doesn't meet them. Since they don't support hardware encryption at all, the iPhone 2G and 3G can in no way meet these requirements, so blocking them from connecting is just good security policy. Here's the problem: Before 3.1, firmwares just falsely reported that a user's iPhone supported device-level encryption. To frame this change as a bugfix is basically dishonest, since this "bug" was intentionally planted by Apple in order to rush full Exchange support out the door on devices that, by their very nature, can't have it. Now, anyone who bought an iPhone 3G under the (reasonable!) impression that they'd be able to use it to connect to their company's security-enabled Exchange server now can't. Oops? Sorry? Both? Apple's solution: Convince your company to slacken its security demands, or just buy a 3GS. Thanks dudes,[I] I'll look into that. [/I][[URL="http://www.broadbandreports.com/forum/r22999133-iPhone-31-breaks-Exchange-Sync-for-pre3GS-phones"]Broadband Reports[/URL] via [URL="http://www.tuaw.com/2009/09/10/iphone-os-3-1-now-enforces-exchange-encryption-policy-may-block/"]TUAW[/URL] via [URL="http://www.appleinsider.com/articles/09/09/11/apple_plugs_loopholes_with_security_updates_in_iphone_os_3_1.html"]AppleInsider[/URL]] [URL="http://ads.pheedo.com/click.phdo?p=1"][IMG]http://ads.pheedo.com/img.phdo?p=1[/IMG][/URL][IMG]http://a.rfihub.com/eus.gif?eui=2226[/IMG][URL="http://feedads.g.doubleclick.net/~a/PCEI35SooDpRS0MT0w4utuGM0kk/0/da"][IMG]http://feedads.g.doubleclick.net/~a/PCEI35SooDpRS0MT0w4utuGM0kk/0/di[/IMG][/URL] [URL="http://feedads.g.doubleclick.net/~a/PCEI35SooDpRS0MT0w4utuGM0kk/1/da"][IMG]http://feedads.g.doubleclick.net/~a/PCEI35SooDpRS0MT0w4utuGM0kk/1/di[/IMG][/URL] [URL="http://feeds.gawker.com/~ff/gizmodo/full?a=3aHayAabG8E:o-kY_PjSdB4:H0mrP-F8Qgo"][IMG]http://feeds.feedburner.com/~ff/gizmodo/full?d=H0mrP-F8Qgo[/IMG][/URL] [URL="http://feeds.gawker.com/~ff/gizmodo/full?a=3aHayAabG8E:o-kY_PjSdB4:yIl2AUoC8zA"][IMG]http://feeds.feedburner.com/~ff/gizmodo/full?d=yIl2AUoC8zA[/IMG][/URL] [URL="http://feeds.gawker.com/~ff/gizmodo/full?a=3aHayAabG8E:o-kY_PjSdB4:D7DqB2pKExk"][IMG]http://feeds.feedburner.com/~ff/gizmodo/full?i=3aHayAabG8E:o-kY_PjSdB4:D7DqB2pKExk[/IMG][/URL] [URL="http://feeds.gawker.com/~ff/gizmodo/full?a=3aHayAabG8E:o-kY_PjSdB4:V_sGLiPBpWU"][IMG]http://feeds.feedburner.com/~ff/gizmodo/full?i=3aHayAabG8E:o-kY_PjSdB4:V_sGLiPBpWU[/IMG][/URL] [IMG]http://feeds.feedburner.com/~r/gizmodo/full/~4/3aHayAabG8E[/IMG] [/QUOTE]
Insert quotes…
Name
Verification
Please enable JavaScript to continue.
Loading…
Post reply
Top