|
|
 Mobile Windows News |  Podcasts |  Videos | Search | Forums | Site News |
|
A Practical Guide to the Smartphone Application Security and Code Signing Model for Developers January 06, 2004 [MS Smartphone] | By anonymous 1. Last year we have published an article about code signing of MS Smartphone applications (click here to read it): 
(on picture above: "Tanager" smartphone at the top and USB token for code signing from GeoTrust at the bottom) ... but now Microsoft itself published extensive article on this topic: Learn what an application developer must understand regarding the Smartphone Application Security model and the different policy options a mobile operator has when bringing a Windows Mobile-based Smartphone to market. Microsoft Windows Mobile-based Smartphones implement an application security model based on digital code signing. An application developer who wants to target Windows Mobile-based Smartphones needs to understand the Smartphone Application Security model and the different policy options a mobile operator has when bringing a Windows Mobile-based Smartphone to market. If you are a Smartphone developer with a knowledge of building Pocket PC or Smartphone applications and are also building Pocket PC and/or Smartphone installation (.cab) packages, this article should provide you with everything you need to know about the Smartphone Application Security model, the difference between privileged and unprivileged applications, how to determine if your application needs privileged trust, how to configure your development environment for Smartphone development, and how to sign your application through a code-signing vendor. To read the article, including several screenshots click here. The article has no photos of USB code signing token, so to see such photos visit our article here.  Post your comment (free registration is required to post, but if you register you can edit your posts later)
   |
| ||||||
| Mobile Windows News | Podcasts | Videos | Search | Forums | Site News |
