<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Exchange enhancements in iPhone 3.1 cause some users grief</title>
	<atom:link href="http://www.roughlydrafted.com/2009/09/17/exchange-enhancements-in-iphone-3-1-cause-some-users-grief/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.roughlydrafted.com/2009/09/17/exchange-enhancements-in-iphone-3-1-cause-some-users-grief/</link>
	<description>Daniel Eran Dilger in San Francisco</description>
	<lastBuildDate>Sun, 05 Feb 2012 17:03:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: duckie</title>
		<link>http://www.roughlydrafted.com/2009/09/17/exchange-enhancements-in-iphone-3-1-cause-some-users-grief/comment-page-1/#comment-21175</link>
		<dc:creator>duckie</dc:creator>
		<pubDate>Wed, 23 Sep 2009 16:33:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=3805#comment-21175</guid>
		<description>Now that I&#039;ve looked into this issue in a bit more depth, I should add that the policy setting that is likely to be making the real difference on Exchange  is &quot;allow non provisionable devices&quot;. When set to true, this allows legacy devices that don&#039;t support the &quot;require encryption&quot; rule (such as Windows Mobile 5 and 6.0, and iPhone OS 3.0 and earlier) to sync with Exchange. Exchange sites that previously allowed iPhones to sync would presumably have had this setting on and still do (and I&#039;d hazard a guess that their old WinMo devices are still happily syncing). There is therefore no reason for admins in such places not to make a policy exception for iPhone OS 3.1 users since this will effectively be preserving the status quo.

The hot air being blown around the web about &quot;security holes&quot;, &quot;bug fixes&quot; and Apple &quot;breaking things&quot; is quite frankly arrant toss and apparently written by people who have never been anywhere near an Exchange admin interface in their life.</description>
		<content:encoded><![CDATA[<p>Now that I&#8217;ve looked into this issue in a bit more depth, I should add that the policy setting that is likely to be making the real difference on Exchange  is &#8220;allow non provisionable devices&#8221;. When set to true, this allows legacy devices that don&#8217;t support the &#8220;require encryption&#8221; rule (such as Windows Mobile 5 and 6.0, and iPhone OS 3.0 and earlier) to sync with Exchange. Exchange sites that previously allowed iPhones to sync would presumably have had this setting on and still do (and I&#8217;d hazard a guess that their old WinMo devices are still happily syncing). There is therefore no reason for admins in such places not to make a policy exception for iPhone OS 3.1 users since this will effectively be preserving the status quo.</p>
<p>The hot air being blown around the web about &#8220;security holes&#8221;, &#8220;bug fixes&#8221; and Apple &#8220;breaking things&#8221; is quite frankly arrant toss and apparently written by people who have never been anywhere near an Exchange admin interface in their life.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pa</title>
		<link>http://www.roughlydrafted.com/2009/09/17/exchange-enhancements-in-iphone-3-1-cause-some-users-grief/comment-page-1/#comment-21051</link>
		<dc:creator>pa</dc:creator>
		<pubDate>Fri, 18 Sep 2009 01:49:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=3805#comment-21051</guid>
		<description>@duckie,

Good analogy. Just to get  a better feel for how Microsoft implements mobile device security on Exchange, you could have used airport security check in your example. 

- can you please remove your laptop, put your bags and jacket and shoes in a tray and place them on the conveyer to be checked by our x-ray technician?
- *no response* 
- please go right ahead sir!</description>
		<content:encoded><![CDATA[<p>@duckie,</p>
<p>Good analogy. Just to get  a better feel for how Microsoft implements mobile device security on Exchange, you could have used airport security check in your example. </p>
<p>- can you please remove your laptop, put your bags and jacket and shoes in a tray and place them on the conveyer to be checked by our x-ray technician?<br />
- *no response*<br />
- please go right ahead sir!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: duckie</title>
		<link>http://www.roughlydrafted.com/2009/09/17/exchange-enhancements-in-iphone-3-1-cause-some-users-grief/comment-page-1/#comment-21032</link>
		<dc:creator>duckie</dc:creator>
		<pubDate>Thu, 17 Sep 2009 18:14:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=3805#comment-21032</guid>
		<description>@Dorotea
It&#039;s not that it&#039;s up to the client to fully disclose security exactly. If a client doesn&#039;t know about a given policy rule (such as encryption) when Exchange asks about it, then Exchange simply allows it to connect anyway. It&#039;s a bit like someone asking you for ID at a nightclub door, and if you say nothing and produce no ID then they let you in anyway.</description>
		<content:encoded><![CDATA[<p>@Dorotea<br />
It&#8217;s not that it&#8217;s up to the client to fully disclose security exactly. If a client doesn&#8217;t know about a given policy rule (such as encryption) when Exchange asks about it, then Exchange simply allows it to connect anyway. It&#8217;s a bit like someone asking you for ID at a nightclub door, and if you say nothing and produce no ID then they let you in anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dorotea</title>
		<link>http://www.roughlydrafted.com/2009/09/17/exchange-enhancements-in-iphone-3-1-cause-some-users-grief/comment-page-1/#comment-21030</link>
		<dc:creator>Dorotea</dc:creator>
		<pubDate>Thu, 17 Sep 2009 15:57:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=3805#comment-21030</guid>
		<description>So lets see if I have this right.  

iPhone 3g/2g don&#039;t have hardware encryption.

 iPhone 3G/2g running OS 3.1 is able to connect to Exchange Server when the security policy doesn&#039;t require hardware encryption of the data on the iPhone.  If Exchange server security policy does require hardware encryption, then an iPhone 3g/2g running OS 3.1 cannot connect.

iPhone 3gs has the ability to do hardware encryption,  so it can connect to Exchange server using OS 3.0 and OS3.1

OS 3.0 did not fully implement client security policies for Exchange server.  OS 3.1 does.   It is left up to the client (iPhone OS) to fully disclose security to Exchange Server .</description>
		<content:encoded><![CDATA[<p>So lets see if I have this right.  </p>
<p>iPhone 3g/2g don&#8217;t have hardware encryption.</p>
<p> iPhone 3G/2g running OS 3.1 is able to connect to Exchange Server when the security policy doesn&#8217;t require hardware encryption of the data on the iPhone.  If Exchange server security policy does require hardware encryption, then an iPhone 3g/2g running OS 3.1 cannot connect.</p>
<p>iPhone 3gs has the ability to do hardware encryption,  so it can connect to Exchange server using OS 3.0 and OS3.1</p>
<p>OS 3.0 did not fully implement client security policies for Exchange server.  OS 3.1 does.   It is left up to the client (iPhone OS) to fully disclose security to Exchange Server .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Berend Schotanus</title>
		<link>http://www.roughlydrafted.com/2009/09/17/exchange-enhancements-in-iphone-3-1-cause-some-users-grief/comment-page-1/#comment-21019</link>
		<dc:creator>Berend Schotanus</dc:creator>
		<pubDate>Thu, 17 Sep 2009 09:59:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=3805#comment-21019</guid>
		<description>This actually might be good news for Apple.

The best way for companies to keep their employees satisfied and to prevent them for using workarounds that allow the use of private iPhones but threaten company security is to provide them with company owned iPhone 3GS&#039;s.</description>
		<content:encoded><![CDATA[<p>This actually might be good news for Apple.</p>
<p>The best way for companies to keep their employees satisfied and to prevent them for using workarounds that allow the use of private iPhones but threaten company security is to provide them with company owned iPhone 3GS&#8217;s.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MarkyMark</title>
		<link>http://www.roughlydrafted.com/2009/09/17/exchange-enhancements-in-iphone-3-1-cause-some-users-grief/comment-page-1/#comment-21007</link>
		<dc:creator>MarkyMark</dc:creator>
		<pubDate>Thu, 17 Sep 2009 05:40:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=3805#comment-21007</guid>
		<description>This whole interwebz &quot;episode&quot; is turning into kind of an amusing impromptu IQ test - which readers immediately grasp the situation and its consequences, and which are left baffled? Lots, I suspect...</description>
		<content:encoded><![CDATA[<p>This whole interwebz &#8220;episode&#8221; is turning into kind of an amusing impromptu IQ test &#8211; which readers immediately grasp the situation and its consequences, and which are left baffled? Lots, I suspect&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hypothesard</title>
		<link>http://www.roughlydrafted.com/2009/09/17/exchange-enhancements-in-iphone-3-1-cause-some-users-grief/comment-page-1/#comment-21006</link>
		<dc:creator>Hypothesard</dc:creator>
		<pubDate>Thu, 17 Sep 2009 05:28:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=3805#comment-21006</guid>
		<description>@jeromec
A device (iPhone) that would recognize (support) all the rules to apply (enforce) when connecting to a Server-side appliance (Exchange server) even those rules forbiding a device lacking capabilities (iPhone EDGE and 3G) like Hardware encryption  (which is present in iPhone 3GS)
Even if It means that the Device (iPhone EDGE or 3G) is now excluded from accessing the Server-side Appliance.

In natural language :
The iPhone (all of them) with iPhone OS 3.0 didn&#039;t have a full implentation of the latest “Rules to respect” when connecting themselves to an Exchange Server (2007 sp1) which sets to refuse connection with  a device not having Hardware encryption.

the iPhone OS 3.1 now fully support those setting on the server side and diplay the refusal and effectivelly forbid the connection to the Exchange server when the iPhone doesn&#039;t have Hardware encryption (iPhone 3G and iPhone EDGE).

Only the iPhone 3GS do have hardware encryption (Software encryption is not efficient in the real world : lack of speed when asked to &quot;remote wipe&quot;, which mean motivated party could crack open the device, then later on, decrypt the storage part, where Hardware encryption provides instantaneous “Remote Wipe out”)</description>
		<content:encoded><![CDATA[<p>@jeromec<br />
A device (iPhone) that would recognize (support) all the rules to apply (enforce) when connecting to a Server-side appliance (Exchange server) even those rules forbiding a device lacking capabilities (iPhone EDGE and 3G) like Hardware encryption  (which is present in iPhone 3GS)<br />
Even if It means that the Device (iPhone EDGE or 3G) is now excluded from accessing the Server-side Appliance.</p>
<p>In natural language :<br />
The iPhone (all of them) with iPhone OS 3.0 didn&#8217;t have a full implentation of the latest “Rules to respect” when connecting themselves to an Exchange Server (2007 sp1) which sets to refuse connection with  a device not having Hardware encryption.</p>
<p>the iPhone OS 3.1 now fully support those setting on the server side and diplay the refusal and effectivelly forbid the connection to the Exchange server when the iPhone doesn&#8217;t have Hardware encryption (iPhone 3G and iPhone EDGE).</p>
<p>Only the iPhone 3GS do have hardware encryption (Software encryption is not efficient in the real world : lack of speed when asked to &#8220;remote wipe&#8221;, which mean motivated party could crack open the device, then later on, decrypt the storage part, where Hardware encryption provides instantaneous “Remote Wipe out”)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kris</title>
		<link>http://www.roughlydrafted.com/2009/09/17/exchange-enhancements-in-iphone-3-1-cause-some-users-grief/comment-page-1/#comment-21004</link>
		<dc:creator>kris</dc:creator>
		<pubDate>Thu, 17 Sep 2009 05:16:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=3805#comment-21004</guid>
		<description>@jeromec

My understanding is that the iPhone 3.1. supports the encryption option(feature), but this  setting(when set to TRUE) is above the capabilities of all iPhones and iPod touches released before 2009 

I hope I&#039;m makings sense to you.</description>
		<content:encoded><![CDATA[<p>@jeromec</p>
<p>My understanding is that the iPhone 3.1. supports the encryption option(feature), but this  setting(when set to TRUE) is above the capabilities of all iPhones and iPod touches released before 2009 </p>
<p>I hope I&#8217;m makings sense to you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeromec</title>
		<link>http://www.roughlydrafted.com/2009/09/17/exchange-enhancements-in-iphone-3-1-cause-some-users-grief/comment-page-1/#comment-21002</link>
		<dc:creator>jeromec</dc:creator>
		<pubDate>Thu, 17 Sep 2009 04:56:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.roughlydrafted.com/?p=3805#comment-21002</guid>
		<description>I have a hard time understanding this article. The sentence &quot;mobile devices that fully support those feature options will stop working if the server-side policy settings raise the bar beyond the devices’ capabilities&quot; in particular, keeps puzzling me:
What is a mobile device that fully supports feature options which are beyond the device&#039;s capabilities???</description>
		<content:encoded><![CDATA[<p>I have a hard time understanding this article. The sentence &#8220;mobile devices that fully support those feature options will stop working if the server-side policy settings raise the bar beyond the devices’ capabilities&#8221; in particular, keeps puzzling me:<br />
What is a mobile device that fully supports feature options which are beyond the device&#8217;s capabilities???</p>
]]></content:encoded>
	</item>
</channel>
</rss>

