Wiley.Developing.Software.for.Symbian.OS.2nd.Edition.Dec.2007 (779887), страница 48
Текст из файла (страница 48)
Upon passing of the tests, they send you the signed application.Let’s look at the steps in more detail.Getting a Publisher IDBefore you can submit your application to a test house for SymbianSigning, you will need a Publisher ID from TC TrustCenter.2 This is acertificate that identifies your company or organization. You also get theprivate key for the certificate so you can self-sign your application withit. The Publisher ID costs 200 US dollars which is paid annually.Signing your application with the Publisher ID is required by SymbianSigned to ensure that submitted applications come from an identifiablesource and that they have not been tampered with along the way.
Thisis always required before your application can be Symbian Signed viaany route (although someone else could sign your application with theirPublisher ID on your behalf, which is the case if you use a PublisherCertifier – more on that shortly).To get the Publisher ID, you should go to the TC TrustCenter website(http://www.trustcenter.de/order/publisherid/dev). You can also navigate to the site from the Symbian Signed portal.2Prior to May 2007, the Publisher ID required by Symbian Signed was supplied byVerisign, and if you have already acquired a Verisign Publisher ID, you can continue to usethis until it expires.
At that point, you should get a replacement from TC TrustCenter ratherthan renew with Verisign. The transition is seamless, and applications previously submittedto Symbian Signed using a Verisign Publisher ID will continue to work on your customers’phones.242PLATFORM SECURITY AND SYMBIAN SIGNEDSimply follow the instructions on the TC TrustCenter site to acquireyour Publisher ID. Once your identity has been verified you will getthe certificate and private key associated with the Publisher ID. Detailedinstructions on how to use the files you download are available on theSymbian Signed website.Sign your application with the Publisher IDOnce you have the .cer and .key files, you can use the Symbiansignsis command line tool to sign your application, as shown earlier. For example, to sign app.sis, you would use the followingcommand:signsis app.sis app_publisherid.sis publish.cer private.keywhere publish.cer and private.key are your Publisher ID files.Submit your application to Symbian SignedSubmit your application to Symbian Signed via the http://www.symbiansigned.com portal.
Follow the instructions given in the detailed documentation provided to guide you in making a submission. You will bedirected to select a third-party test house to make sure your applicationpasses the tests in the test criteria document (they will provide you witha quote for the costs).You should make sure your application passes the tests in the testcriteria document before you submit it to Symbian Signed.
This will savetime and money, since every time your application has to change, itneeds to be resubmitted to the test house at a cost to you. It also preparesyou better to handle issues and any problems reported by the third-partytest house.To submit to the Symbian Signed website you need the SIS file (signedwith the Publisher ID), a readme containing description and usageinformation, and your application’s package (i.e., PKG) file. When thetest house receives your application it verifies the signature to make surethe submitted application came from you.Support the test house as neededTesting with the test house can be interactive depending on what yourapplication does, how complex it is, and the issues and problems found.If you have any questions prior to submitting the Test Houses will provideGETTING YOUR APPLICATION SYMBIAN SIGNED243support to ensure your submission runs smoothly.
The contact details forthe Test Houses can be found on the Symbian Signed website.Receiving your Symbian Signed applicationOn successful completion of the process, you will be notified and canthen download your application which is now Symbian Signed.Behind the scenes, when your application passes all its tests and isapproved, the test house uploads your application to TC TrustCenter. TCTrustCenter then sign the file using the Symbian Signed root certificate,allowing the installer on the phone to check that the file has been SymbianSigned and can install. This means that the creator of the application canbe identified by the user through the phone’s application manager.
OnceSymbian Signed, the user will no longer see an ‘untrusted source’ warningmessage when they install it.If you require phone manufacturer capabilitiesIf your application uses any of the phone manufacturer capabilities (Tcb,Drm, AllFiles, MultimediaDD, DiskAdmin, NetworkControl, orCommDD) you have extra steps to go through. You must get approval fromthe phone manufacturer to use these. To request this approval, you mustcomplete and submit a capability request form that indicates which of thecapabilities you need and the reason why you need them.
The third-partytest house will also need to run through some specific tests required bythe phone manufacturer in question.7.6.4Self-CertificationAn alternative to sending your application to a test house for approval is tobecome a self-certifier. This means that you run the Symbian Signed testsspecified in the test criteria document yourself, without going to a thirdparty test house.
Once you have completed all testing, you submit the testresults, along with your application (and other information you normallysend to a test house including waiver documents) via the Symbian Signedwebsite. Once uploaded the SIS file is Symbian Signed and is availableto download. Note that you must still have signed your application withyour Publisher ID before submitting it.If your application has phone manufacturer capabilities, you will alsoneed a self-certification agreement with that manufacturer. Symbian willnot sign a self-certified application with those sensitive capabilities untilit has verified with the manufacturer that this agreement is in place.244PLATFORM SECURITY AND SYMBIAN SIGNED7.7 Developer CertificatesYou may ask how you can test your application on hardware beforesubmitting it to Symbian Signed if it requires it to be Symbian Signedto run on devices.
This is a good question! You can always test it onthe emulator, which does not require Symbian Signing, but you do alsoneed to test your application on a real phone. The answer to this, ashinted before, is to use a developer certificate (like Symbian Signing, youdo not need a developer certificate if your application does not requirecapabilities from the extended or phone manufacturer sets).7.7.1 What is a Developer Certificate?Instead of signing with a certificate and key generated by the makekeystool, a developer certificate is a certificate you download from Symbianfor your day-to-day development work. You can sign your applicationyourself with this certificate, and then test the software on one or morephones.There are, however, some limitations:1.The signed application will only work on a specified phone or set ofphones. The IMEI (i.e., serial numbers) of each phone is hardcodedinto the certificate.2.The developer certificate will expire after six months, after whichtime you will need to download a new certificate.Developer certificates can be configured to contain a particular set ofcapabilities, and you must get approval from the phone manufacturer ifyou need the most sensitive capabilities in your developer certificate.Developer certificateA developer certificate allows you to install the signed software on anumber of phones as long as they are registered in the certificate.
Adeveloper certificate can be used with any of the basic and extendedcapabilities.Phone manufacturer certificateIf your application uses any of the phone manufacturer capabilities, youwill need a phone manufacturer approved developer certificate. It isnecessary to apply to the phone manufacturer for a developer certificatecontaining phone manufacturer capabilities. The Symbian Signed website provides information on how to apply for a developer certificatecontaining these type of capabilities.DEVELOPER CERTIFICATES2457.7.2 How Do I Get a Developer Certificate?To get a developer certificate, you need to log into the Symbian Signedsite (registering if you’ve not already done so) and perform the followingsteps:1. Download the DevCertRequest tool.2.
Create the CSR request file using DevCertRequest.3. Apply for the developer certificate, which includes uploading the.csr request file.4. Download the certificate.Let’s look at these steps in more detail.Download the DevCertRequest toolThe DevCertRequest tool can be downloaded from the SymbianSigned site. DevCertRequest runs on a PC and is used to create a CSRrequest file that is used to submit a developer certificate request.Create the CSR request file using DevCertRequestRun DevCertRequest and follow the instructions in the tool to generatea CSR request file. You will be prompted to enter the capabilities that youneed and also the IMEI numbers of the phones you intend to use (a SISfile signed with the developer certificate generated from the request canonly be installed on the devices specified at this prompt).Upload the request fileOnce the CSR file has been generated by the DevCertRequest tool,follow the instructions on the Symbian Signed site to submit the requestby uploading the CSR file you created.
If your development certificaterequests manufacturer capabilities then follow the path for requestinga phone manufacturer approved development certificate. You will beprompted as to what phone manufacturer must be contacted (e.g., Nokiaor Sony Ericsson).
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
