Wiley.Symbian.OS.C.plus.plus.for.Mobile.Phones.Aug.2007 (779890), страница 53
Текст из файла (страница 53)
To do this, we first show you how to build yourapplication so that it can be installed on a phone and then go through thesteps required to authorize your application via Symbian Signed.Building the ApplicationUp to this point, we’ve done everything in the emulator. Now it is time torebuild the application for ARM and install it onto a Symbian OS phoneusing the appropriate user interface.Building the application for the target phone is simple. You can buildit from the Carbide.c++ IDE, after selecting the ARM UREL target, or youcan build it from the command line by typing:abld build armv5 urelThis builds a releasable application, which is ready to be copied ontothe phone itself. To install the application on to the phone, Symbian OSPREPARING AN APPLICATION FOR DISTRIBUTION269provides a powerful, yet straightforward installation system that offers asimple and consistent user interface for installing applications, data orconfiguration information on to phones.The basic idea is that end users install all the code, packaged inSymbian OS installation (SIS) files.
These can be transferred to the phonefrom a PC using connectivity software, Bluetooth, infrared or even emailand an Internet connection, as illustrated in Figure 9.1..pkg.exePC connectivity.rscInstallation filegenerator(makesis).mbmInfraredSymbian OSphone.sisBluetoothEmail/Internet.cerOtherdatafilesFigure 9.1 Installation methodsThe SIS files are generally very small in size (at most a few hundredkilobytes) and are therefore very quick to transfer to the target phone.Three command-line tools are provided to enable you to create SIS files:• the Installation File Generator, makesis .exe, creates the installationfiles from information specified in the package file• the Certificate Generator, makekeys .exe, creates private–publickey pairs and a certificate file; it is used by the Installation FileGenerator to digitally sign the installation files• the Installation File Signer, signsis .exe, digitally signs the installation files with a Class 3 ID certificate such as an ACS Publisher IDissued by TC TrustCenter.There are three steps involved in generating the SIS file.1.
Create a PKG package file that specifies all the files that go into theSIS file, and where they are to be installed on the target phone.270PLATFORM SECURITY AND PUBLISHING APPLICATIONS2.Run the makesis command line tool to generate the SIS file.3.Sign the application using signsis.exe.
If the application is tobe submitted to Symbian Signed, you sign it with an ACS PublisherID. If the application does not need to be Symbian Signed, certainphone manufacturers may require you to sign it with a user-generatedcertificate.Producing the Package FileBefore you create the SIS file, you need to specify information about theapplication in a package file. This is a plain text file but, because of itsflexibility, the format is one of the most obscure of the Symbian OS toolcontrol files.For our example, we start with the OandX.pkg file from the Noughtsand Crosses application that is described in Chapter 12.
Bear in mind thatthe resulting SIS file cannot be installed on any phone based on SymbianOS v9, unless it is signed. Here is the content of OandX.pkg for an S60phone:; OandX.pkg; Language – standard language definitions&EN; Vendor:"Symbian Software Ltd."%{"Symbian Software Ltd."}; standard SIS file header#{"OandX (S60)"},(0xE04E4143),1,0,0,TYPE=SA; Supports S60 v3.0[0x101F7961], 0, 0, 0, {"Series603rdEditionProductID"}"\epoc32\data\z\resource\apps\OandX.rsc""!:\resource\apps\OandX.rsc""\epoc32\data\z\resource\apps\OandX_loc.rsc""!:\resource\apps\OandX_loc.rsc""\epoc32\data\z\resource\apps\OandX.mbm""!:\resource\apps\OandX.mbm""\epoc32\data\z\private\10003a3f\import\apps\OandX_reg.rsc""!:\private\10003a3f\import\apps\OandX_reg.rsc""\epoc32\release\armv5\urel\OandX.exe"-"!:\sys\bin\OandX.exe"The body of this file should be obvious enough: all source files thatwill be packaged into the SIS file are listed, along with information aboutwhere they should be unpacked upon installation.
The ‘!’ drive specifiermeans ‘the chosen installation drive’. If you require a file to reside on theC: drive of the phone, for instance, you can specify that instead, but thisis rare, and should only be used if absolutely necessary.The header is more interesting.• The & line specifies the languages supported by this installation file:in this case, English only.PREPARING AN APPLICATION FOR DISTRIBUTION271• The : and % lines specify the localized and non-localized vendorname.• The # line specifies the application’s caption to be used at install time,its final SID and its three-part version number – 1,0,0 is specifiedhere, which will be displayed as 1.0(000), indicating major, minorand build.This is the general form of a PKG file for a basic, single-languageapplication.
In fact, the PKG file format supports more options than this,including nested packages, multi-language installation files and requireddependencies. All these are documented in the SDK.One thing to note is that, because Symbian OS is so flexible andallows many different user interfaces to be developed, you should alwaysensure that your SIS file can only be installed on the user interface forwhich it was designed. If you don’t, you – or, more importantly, yourend-users – may experience problems.To enable you to do this, each product is assigned a unique IDwhich is used by the application installation mechanism to ensure thatonly compatible applications can be installed on the phone.
Also, eachplatform version is assigned a unique ID. It is assumed that a platformversion is compatible with all earlier platform versions, but not with anylater versions. You can specify the platform information by including inthe package file a line of the following form:[0x101F6300], 1, 0, 0, {"UIQ30ProductID"}where:• [0x101F6300] is the product and platform version SID• 1, 0, 0 is the major version, minor version and build numbers of theplatform (not the application)• {"UIQ30ProductID"} is a feature-identification string.Not all products support this mechanism: for those that do, you canfind exact details of the SIDs, feature-identification strings and versionnumbers to use in the appropriate product-specific SDK.
On productsthat support this mechanism, the installation software refuses to installany SIS file that does not contain the correct platform information.Generating the Final SIS fileWhen all the source files and application information have been specifiedin the PKG file, you can create an installable OandX.sis file in yourcurrent directory by issuing the command:272PLATFORM SECURITY AND PUBLISHING APPLICATIONSmakesis OandX.pkg OandX.sisYou then need to sign the SIS file:signsis OandX.sis OandX_Signed.sis myCert.cer myCert.key passwordwhere:• OandX_Signed.sis is the filename for the signed version of theapplication• myCert.cer is the certificate filename• myCert.key is the certificate’s private key• password is the password of the private key.The SIS file is now ready. If you need to have the application SymbianSigned, read Section 9.5, otherwise go to Section 9.6 to see how to installyour application on a mobile phone.9.5 Overview of Symbian SignedSymbian Signed was introduced against a background in which, althoughopen phones offer revenue opportunities, there are also associated threatssuch as fear of viruses, billing storms (where the user is billed illegally orwithout their knowledge), etc.
With an open environment comes responsibility and Symbian Signed is intended to support that responsibility,hence the need for a testing and certification programme that ensures thatyou know the source and provenance of an application. It also means thatthe application has been tested to meet certain industry-agreed minimumcriteria. Applications that are signed must then be tamper-proof in orderto be trusted.Symbian Signed is a foundation programme on which other licensees,network operators and partners can build if they have a specific need.
Asa result there are mechanisms to support additional tests where required,for example where:• access to prototype devices is needed• the application is going to be a signature application shipped withphones or has operator requirements it must fulfill• the application makes extensive use of the network and so the networkimpact of the application needs to be assessed.OVERVIEW OF SYMBIAN SIGNED273To date, over 18 000 SIS files have been signed, with more andmore network operators around the world insisting that applications areSymbian Signed before they even consider selling and distributing themvia their portals.Test CriteriaIn order to get your application Symbian Signed, it must pass the SymbianSigned test criteria (available at www.symbiansigned.com).
We recommend that you make these tests part of your usual development lifecyclefor your application to minimize the chances of failure when it comes totesting against the Symbian Signed test criteria.The test criteria are split into six categories as outlined in Figure 9.2.Package and InstallationPhone OperationGeneral OS UsageUser Data and ControlMemoryIdentityFigure 9.2 Symbian Signed test criteria categoriesThe Identity category refers to the ACS Publisher ID that you can obtainfrom TC TrustCenter. The other five categories focus on functionalityaspects of the application. For example, Memory tests ensure that yourapplication starts and closes gracefully in low-memory situations.
PhoneOperation tests ensure that your application does not stop the phone fromundertaking its primary function – making phone calls. Various other testssuch as installation and uninstallation, verification of the use of correctSIDs and so on are also part of the test criteria.
These all combine to helpmake the use of Symbian OS devices a pleasant experience.To get your application Symbian Signed, you develop the application,test it and send it to a test house. If it passes the test criteria, yourapplication is Symbian Signed (see Figure 9.3).Signed or Unsigned?It is optional for developers to put applications written for versions ofSymbian OS before v9 through the Symbian Signed process. The benefits274Register onsymbiansigned.comDownload SIS fromaccountPLATFORM SECURITY AND PUBLISHING APPLICATIONSRequest ACSPublisher ID fromTC TrustCenterSign SIS file withACS publisher IDSIS file testedSubmit SIS file toTest HouseInstall on SymbiansmartphoneFigure 9.3 Application-signing processof doing so are driven by market demand.
Application robustness, qualityand identification of the origin of the application are the primary driversof this demand. Due to this, some phone manufacturers now insistthat all applications delivered in a SIS file are Symbian Signed priorto distribution via their channels. Many network operators are alsoincreasingly aware of the importance of testing and signing applicationsand require applications to be Symbian Signed prior to distribution viatheir portals.If you are developing for Symbian OS v9, Symbian Signed becomeseven more significant.
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
