diff -r 51a74ef9ed63 -r ae94777fff8f Symbian3/SDK/Source/GUID-B9414AE8-820E-4CA5-A9C4-29560CD6F2EF.dita --- a/Symbian3/SDK/Source/GUID-B9414AE8-820E-4CA5-A9C4-29560CD6F2EF.dita Wed Mar 31 11:11:55 2010 +0100 +++ b/Symbian3/SDK/Source/GUID-B9414AE8-820E-4CA5-A9C4-29560CD6F2EF.dita Fri Jun 11 12:39:03 2010 +0100 @@ -1,50 +1,53 @@ - - - - - -Application -signing -

All Symbian applications must be signed before they can be installed. -All applications which use capability-protected -APIs, where the capability cannot be granted by the end user, have to be certified. -Such certification can be obtained through Symbian -Signed.

-

Signing is a means of encoding a digital certificate into the application -installation file. The certificate identifies the application’s vendor, and -grants access to capabilities defined during the build process.

-

The signing process is described in detail on the Symbian -Signed website.

-
Signing options -

If your application only needs user capabilities (LocalServices, NetworkServices, ReadUserData, WriteUserData, UserEnvironment, andLocation), -you can self-sign the application.

- -

When the end users are installing a self-signed application, they are -informed that the application is untrusted and may decide to abort the installation. -In Nokia E-series devices the user must change a setting to allow self-signed -applications to install.

-
-

Sign the sis installation -file with any private key. You can use the MakeKeys application -to create the needed private key and, for example, SignSIS to -sign the application. Both applications are delivered with the SDK. For more -information, see How -to sign a .Sis file with Self-Sign Certificate in the Forum Nokia -Developer Community Wiki.

-

The other signing options (Open Signed, Express Signed and Certified -Signed) are described in detail in The -Complete Guide to Symbian Signed.

-
-
Additional information -on signing -

The UID value you need to use for your application depends on whether -your application is signed or self-signed. For more information, see UID and How -to use UIDs.

-
+ + + + + +Application +signing +

All Symbian applications must be signed before they can be installed. +All applications which use capability-protected +APIs, where the capability cannot be granted by the end user, have to be certified. +Such certification can be obtained through Symbian +Signed.

+

Signing is a means of encoding a digital certificate into the application +installation file. The certificate identifies the application’s vendor, and +grants access to capabilities defined during the build process.

+

The signing process is described in detail on the Symbian +Signed website.

+
Signing options +

If your application only needs user capabilities (LocalServices, NetworkServices, ReadUserData, WriteUserData, UserEnvironment, andLocation), +you can self-sign the application.

+ +

When the end users are installing a self-signed application, they are +informed that the application is untrusted and may decide to abort the installation. +In Nokia E-series devices the user must change a setting to allow self-signed +applications to install.

+
+ +

Sign the sis installation +file with any private key. You can use the MakeKeys application +to create the needed private key and, for example, SignSIS to +sign the application. Both applications are delivered with the SDK. For more +information, see How +to sign a .Sis file with Self-Sign Certificate in the Forum Nokia +Developer Community Wiki.

+

The other signing options (Open Signed, Express Signed and Certified +Signed) are described in detail in The +Complete Guide to Symbian Signed.

+
+
Additional information +on signing + +

The UID value you need to use for +your application depends on whether your application is signed or self-signed. +For more information, see How +to use UIDs.

+
\ No newline at end of file