Wiley.Symbian.OS.C.plus.plus.for.Mobile.Phones.Aug.2007 (779890), страница 54
Текст из файла (страница 54)
This is because, if an application you are developing makes use of capabilities, the application must be Symbian Signed. If itis not Symbian Signed, a phone will not install the application. If an application doesn’t use capabilities then it will install without signing – simple!Well actually, not quite that simple.Some Symbian OS v9 phones may allow unsigned applications thatuse certain capabilities to be installed with no problems. An unsignedapplication, however, behaves slightly differently to a signed applicationwhen used on the phone. Let’s say, for example, you create an applicationthat makes use of the UserEnvironment capability (i.e., it uses BluetoothAPIs) and you do not have to get it signed as you know it will install onthe phone you are developing for.
When using this unsigned applicationon the phone, any functionality that utilizes Bluetooth results in a dialogbox appearing on the phone’s screen asking the user whether to allow theOVERVIEW OF SYMBIAN SIGNED275application to use the Bluetooth functionality. This dialog appears everytime the functionality is needed. A Symbian Signed application does notdisplay these dialog boxes at all.A further consideration is that some phone manufacturers may requirethese applications to be signed by the developer, sometimes called ‘selfsigned’. This means that a signing must take place using a certificate thatyou have developed using tools on the SDK (i.e.
makekeys.exe) since,without this, the application will not install. It doesn’t require visiting theSymbian Signed website or obtaining an ACS Publisher ID, so it is a smalltask in relation to the overall development effort, but it is something tobear in mind.These policies are defined by the mobile phone manufacturers so it isrecommended that you check with them first. For the sake of simplicityin this book, we have assumed that all applications you are developingfor Symbian OS v9 phones will be Symbian Signed.However, there’s just one small catch – an application won’t install ona phone until you’ve had it Symbian Signed, so how do you test it on thephone before submitting it for testing and signing? The solution is to useDeveloper Certificates.Developer CertificatesDeveloper Certificates allow controlled capability access to specificphones.
By controlled access we mean that the range of phones that can beused is limited to specific phones according to their IMEI and capabilitiesaccess is restricted to only the ones that are needed by the application. Thelevel of access in terms of the number of IMEIs and capabilities requiredis determined according to identity of the developer (i.e. who you are)and whether the capability requires phone-manufacturer approval.If you are happy to test your application on just one phone and it onlyuses the capabilities that are ticked in the first column of Table 9.1, thenthere is no need for an ACS Publisher ID.
If you need to debug on morethan one phone then you need an ACS Publisher ID. If you need to debugyour application on more than 100 phones and/or you need any of theseven remaining capabilities, then you will need both an ACS PublisherID and phone-manufacturer approval.An ACS Publisher ID is a class 3 certificate, obtainable from organizations such as TC TrustCenter and costing US$200 per annum at the timeof writing.
It verifies that your organization exists and is bona fide.All Developer Certificates are issued via the Symbian Signed webportal, once you have registered. If you need a developer certificate thatrequires phone-manufacturer approval, you simply need to follow theappropriate links on the site.To request a developer certificate, you use a tool called DevCertRequest which can be downloaded from the Symbian Signed portal. You276PLATFORM SECURITY AND PUBLISHING APPLICATIONSTable 9.1 Developer certificate requirementsNumber of IMEIsIdentityRequirements11–100Phone ManufacturerApproved- Registration - Registration- Registration- IMEI- IMEIs- IMEIs- ACS Publisher ID - ACS Publisher ID- Phone ManufacturerApprovedCapabilityLocal ServicesLocationNetwork ServicesPower ManagementProtServRead User DataSurroundings DDSW EventUser EnvironmentWrite User DataRead Device DataTrusted UIWrite Device DataAll FilesCommDDDisk AdminDRMMultimediaDD√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√OVERVIEW OF SYMBIAN SIGNED277Table 9.1 (continued )Number of IMEIsIdentityRequirements11–100Phone ManufacturerApproved- Registration - Registration- Registration- IMEI- IMEIs- IMEIs- ACS Publisher ID - ACS Publisher ID- Phone ManufacturerApprovedCapabilityNetwork ControlTCB√√use this tool to enter the ACS Publisher ID, IMEI and capability information and create a Certificate Signing Request (CSR) file.
This file is thenuploaded to the Symbian Signed portal and the information contained init is used to generate a developer certificate (CER).The Signing ProcessNow you have developed your application for phones based on SymbianOS v9, you must get it signed. This section describes how.PreparationYou have written and tested your application successfully on the SymbianOS emulator. You have tested it on a Symbian OS v9 phone after signingit with a developer certificate and you are now confident that not onlyhas it passed your own strenuous black-box and white-box testing, ithas also passed all the Symbian Signed test criteria.
What’s the nextstage?ACS Publisher ID signingActually there isn’t that much more left to do other than sign yourapplication with your ACS Publisher ID and submit it to the website.Run the signsis.exe tool to sign your SIS file, specifying your publicACS Publisher ID certificate, private key and password:278PLATFORM SECURITY AND PUBLISHING APPLICATIONSsignsis OandX.sis OandX_Signed.sis myACS.cer myACS.key passwordYou should now have a SIS file that is signed and ready to be submittedfor testing.
You are almost there . . .SubmissionTo submit the SIS file, visit the Symbian Signed website at www.symbiansigned.com and log in using the username and password you createdwhen you first registered. Choose the Submit option and follow the stepsto select the Test House and enter the required information (user detailsand application details).
Finally submit the application and its supportingmaterials.The following files are required to be included in the ZIP file yousubmit.• the SIS file (signed with your ACS Publisher ID) to be tested by the testhouse• the PKG file used to create the SIS file; this will be cross-referencedby the Test House to ensure correct target platform and specification• a completed Readme.txt file, which should include any releasenotes and quick advice on how to use the application. Depending onthe nature of the application, you might choose to supplement – orreplace – this file with a user guide in PDF format.After you have submitted your application, it is sent to the test houseyou selected.
The test house verifies the validity of the ACS Publisher IDand the signature of the SIS file. If verification is successful, the test houseexamines your application and sends you a quote for the cost of thetest run. You receive notification emails throughout this process. If youwish to query the quote you receive, you should contact the test housedirectly – additional details can be found on the website.Once your application has successfully passed all of the tests conducted by the test house, the test house uploads your application to theCertificate Authority. The Certificate Authority removes the ACS PublisherID, stores details of the application in its revocation database, re-signsthe application against the Symbian root certificate and sends the signedapplication back to the test house. The test house then informs you thatyou can download your Symbian Signed application from the site, alongwith the test report.Your application is ready for distribution and can display the SymbianSigned logo as shown in Figure 9.4.INSTALLING A SIS FILE279Figure 9.4 Symbian Signed logo9.5 Installing a SIS FileOnce you have a working SIS file, it is easy to install it onto a SymbianOS v9 phone: all you need do is transfer it to the phone and launch theSIS file!There are several transfer methods available – choose what is supported on your PC or phone and what is most convenient for you at thetime:• serial or USB connection – install the PC Connectivity softwareaccompanying your phone and send files through a serial or a USBcable• infrared – you need to enable infrared on both your PC and thephone and to run software that allows you to send files between twoinfrared ports; this is normally part of the PC Connectivity softwareaccompanying your phone• Bluetooth – you need to enable Bluetooth on both your PC and yourphone• email – you can send the SIS file to your phone as an email attachmentif you activate the email account on your phone; as you will use themobile phone network to send the file, you may incur costs• Internet – you can download a SIS file straight from a website; youmay incur costs when using the mobile phone network to connect tothe website.Once you have transferred the SIS file, it should appear on the phoneas a ‘received’ file – simply select the icon to launch the file and beginthe installation process.
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
