| |
|
| Classification: |
General |
Category: |
Symbian Signed |
| Created: |
03/09/2005 |
Modified: |
03/23/2005 |
| Number: |
FAQ-1229 |
| Platform: |
Not Applicable |
|
Question:
After I signed the SIS file for my UIQ device with my ACS Publisher Certificate (prior to submitting it to Symbian Signed)
it doesn't install. It does install on Series 60 devices, but displays a warning. What is going on?
Answer:
This is normal behaviour.
SIS files that are only signed with a ACS Publisher ID will be rejected at installation on most UIQ devices and pass (with
a warning) on Series 60. The test house use your ACS Publisher ID to verify the source of your application when it is submitted,
but strip the certificate away in order to install the application on the device.
The reason for this is that the root of the "chain of trust" for the ACS Publisher Certificate is not on your phone. This
is reasonable - the ACS Publisher certificate verifies the identity of the signer; it does not verify that the SIS file has
undergone SymbianSigned testing.
After the SIS file is tested, it is Symbian Signed with an ACS Content ID ( that chains to the "Symbian B" CA certificate)
and therefore installs without warnings on phones that support SymbianSigned (i.e. the phone contains the Symbian B root certificate).
More detail on PKI and the different certificates is provided here .
|
| |
|
![[Index]](../../a_stock/btn_index_wt.gif){kind=small}
![[spacer]](../../a_stock/btn_spacer.gif){kind=small}
![[Previous]](../../a_stock/btn_prev_wt.gif){kind=small}
![[Next]](../../a_stock/btn_next_wt.gif){kind=small}
![[Previous]](../../a_stock/btn_prev.gif){kind=small}
![[Top]](../../a_stock/btn_top.gif)
![[Next]](../../a_stock/btn_next.gif){kind=small}