Paragon
05-16-2005, 03:06 AM
As we all learned a few days ago Microsoft has chosen to remove WiFi syncing from AS 4.0 which is the only version that will work with upcoming Windows Mobile 5.0 devices. This adversely effects how thousands and thousands of people use their Windows Mobile devices.
Apparently this was done because there are security issues when using WiFi to Activesync, and they don’t have enough time to fix the problems before Windows Mobile 5.0 and AS 4.0 start shipping. They were faced with a choice of removing it, or delaying the release. I can’t be the only one here who sees a major flaw in this decision. If there are security issues with WiFi and Activesync they have been there for quite sometime. They didn’t just come to light in the past few weeks. They would have been there much longer. I don’t think I’m violating any NDA here by stating that I was provided a build of AS 4.0 a year ago. A year ago! The largest software company in the world, its OS is on the huge majority of computers around the world, and they don’t have the resources to fix this issue in a timely manner? This has been an ongoing problem with Microsoft and its mobile devices. I’m being careful not to place this squarely on the shoulders of the Mobile Devices team, because AS is developed by the Windows team now, if I’m not mistaken.
I know I must sound like my normal, pessimistic, negative self here, my apologies, but geez, this one seems a bit much to me. Actually removing a very popular, useful feature that tens of thousands of people use everyday, because one of the largest corporations in the world doesn’t have the time and resources to fix it…Come on!
I’m willing to bet that the vast majority of users would choose to use WiFi to sync regardless of the security issues, because to them it isn’t of great importance, or doesn’t come into play for a number of reasons which make it highly unlikely anyone would have the opportunity to take advantage the security problems. That’s not to say that this is not an important issue by any means. It is a very important issue that must be dealt with. My point is that WiFi syncing is being taken away from all users regardless of their situation, or choice.
To me I think there is a very simple temporary fix to this problem. When syncing via WiFi have a window pop up stating that there are security flaws when syncing using WiFi, and ask if you wish to continue, perhaps with a hyperlink to more information on the subject. This brings the issue to the attention of the user, yet allows those who wish to continue, to do so. On an enterprise level I’m sure there could be a locking function that could be enabled so that admins can block WiFi sync to keep their systems secure.
Personally I think this issue brings to the surface the priorities Microsoft has placed on mobile devices. It is committed to mobile devices, but the current state is just a temporary one on a path to somewhere yet defined. They want it to succeed but don’t want to put too deep of a commitment into the current situation because it will likely change considerably, make it work but don’t go too deep with it since it will evolve to something else, probably very soon anyway.
I have to ask this question of Microsoft, why spend time and resources developing something like a mobile Powerpoint application, that is already available through several third parties, as an example, when there are serious security holes in your syncing application that need to be repaired, but are left untouched, then say you don't have the resources to fix the problems?
How am I to properly evangelize your platform when you do stupid things like this?
Dave
Apparently this was done because there are security issues when using WiFi to Activesync, and they don’t have enough time to fix the problems before Windows Mobile 5.0 and AS 4.0 start shipping. They were faced with a choice of removing it, or delaying the release. I can’t be the only one here who sees a major flaw in this decision. If there are security issues with WiFi and Activesync they have been there for quite sometime. They didn’t just come to light in the past few weeks. They would have been there much longer. I don’t think I’m violating any NDA here by stating that I was provided a build of AS 4.0 a year ago. A year ago! The largest software company in the world, its OS is on the huge majority of computers around the world, and they don’t have the resources to fix this issue in a timely manner? This has been an ongoing problem with Microsoft and its mobile devices. I’m being careful not to place this squarely on the shoulders of the Mobile Devices team, because AS is developed by the Windows team now, if I’m not mistaken.
I know I must sound like my normal, pessimistic, negative self here, my apologies, but geez, this one seems a bit much to me. Actually removing a very popular, useful feature that tens of thousands of people use everyday, because one of the largest corporations in the world doesn’t have the time and resources to fix it…Come on!
I’m willing to bet that the vast majority of users would choose to use WiFi to sync regardless of the security issues, because to them it isn’t of great importance, or doesn’t come into play for a number of reasons which make it highly unlikely anyone would have the opportunity to take advantage the security problems. That’s not to say that this is not an important issue by any means. It is a very important issue that must be dealt with. My point is that WiFi syncing is being taken away from all users regardless of their situation, or choice.
To me I think there is a very simple temporary fix to this problem. When syncing via WiFi have a window pop up stating that there are security flaws when syncing using WiFi, and ask if you wish to continue, perhaps with a hyperlink to more information on the subject. This brings the issue to the attention of the user, yet allows those who wish to continue, to do so. On an enterprise level I’m sure there could be a locking function that could be enabled so that admins can block WiFi sync to keep their systems secure.
Personally I think this issue brings to the surface the priorities Microsoft has placed on mobile devices. It is committed to mobile devices, but the current state is just a temporary one on a path to somewhere yet defined. They want it to succeed but don’t want to put too deep of a commitment into the current situation because it will likely change considerably, make it work but don’t go too deep with it since it will evolve to something else, probably very soon anyway.
I have to ask this question of Microsoft, why spend time and resources developing something like a mobile Powerpoint application, that is already available through several third parties, as an example, when there are serious security holes in your syncing application that need to be repaired, but are left untouched, then say you don't have the resources to fix the problems?
How am I to properly evangelize your platform when you do stupid things like this?
Dave