Symbian OS Platform Security/03. The Platform Security Environment - Revision history

Craig: /* SID */ 0 is not protected

2011-01-17T14:53:38Z

‎SID: 0 is not protected

2011-01-17T11:50:34Z

removed category, added copyright template

2011-01-06T16:50:16Z

chapter authors, navigation links, table formatting

2011-01-03T19:19:33Z

formatting, added back-up link

2010-12-18T16:03:14Z

10 revisions: import from developer.symbian.org

2010-03-24T11:49:43Z

2010-03-17T22:19:46Z

2010-03-12T13:45:48Z

2010-03-12T13:37:31Z

2010-03-11T16:08:28Z

‎Packaging the Completed Application

@@ Line 57: / Line 57: @@
 have a different SID from all other EXEs on that phone.
-SIDs are divided into two ranges: {{Icode|0x00000000–0x7FFFFFFF} is
+SIDs are divided into two ranges: {{Icode|0x00000001–0x7FFFFFFF}} is
 the ‘protected range’, and the installer (see Chapter 8) will only allow
 EXEs to be installed with SIDs in this range if the package is signed

← Older revision		Revision as of 11:50, 17 January 2011
Line 633:		Line 633:
	test your applications on your own hardware.		test your applications on your own hardware.

−	~~[[Category:Book]]~~	+	{{SymbianOSPlatformSecurity_Copyright}}

@@ Line 1: / Line 1: @@
 {| width="100%"
 |-
-|Reproduced by kind permission of John Wiley & Sons.||align="right"|[[Symbian OS Platform Security|Table of Contents]]
+|'''by Michael Bruce and Phil Spencer'''||align="center"|Reproduced by kind permission of John Wiley & Sons.||align="right"|'''[[Symbian OS Platform Security/02. Platform Security Concepts|Prev.]] &nbsp; [[Symbian OS Platform Security|Contents]] &nbsp; [[Symbian OS Platform Security/04. How to Write Secure Applications|Next]]'''
 |}
 =Building Your Application=
@@ Line 91: / Line 90: @@
 Table 3.1 summarizes the use of UIDs allocated under the new scheme.
-'''Table 3.1''' UID Allocation Ranges
+{| border="1" cellspacing="0" cellpadding="6"
-{| border="1" cellspacing="0" cellpadding="4"
+|+'''Table 3.1''' UID Allocation Ranges
 !UID Range !!Intended Use
 |-
@@ Line 222: / Line 221: @@
 Table 3.2.
-'''Table 3.2''' Capability Mismatches Between a DLL and an EXE
+{| border="1" cellspacing="0" cellpadding="6"
-{| border="1" cellspacing="0" cellpadding="4"
+|+'''Table 3.2''' Capability Mismatches Between a DLL and an EXE
 !DLL Capabilities !!Result
 |-
@@ Line 634: / Line 633: @@
 test your applications on your own hardware.
-[[Category: book]]
+[[Category:Book]]

← Older revision		Revision as of 13:45, 12 March 2010
Line 1:		Line 1:
		+	Reproduced by kind permission of John Wiley & Sons.
		+
	=Building Your Application=		=Building Your Application=
	Platform security introduces a number of new features for building		Platform security introduces a number of new features for building

← Older revision		Revision as of 13:37, 12 March 2010
Line 662:		Line 662:
	developer certificates which enable you to freely and easily develop and		developer certificates which enable you to freely and easily develop and
	test your applications on your own hardware.		test your applications on your own hardware.
		+
		+	[[Category: book]]

← Older revision	Revision as of 16:03, 18 December 2010
(No difference)

← Older revision	Revision as of 11:49, 24 March 2010
(No difference)

← Older revision	Revision as of 22:19, 17 March 2010
(No difference)

@@ Line 622: / Line 622: @@
 of your application to your target end-users. Once you have completed
 thorough testing and debugging on both the emulator and target phone as
-described in this chapter, you should rebuild a new SIS file with MakeSIS
+described in this chapter, you should rebuild a new SIS file with MakeSIS containing your final release build binaries. You will
-(see Section 3.3.2) containing your final release build binaries. You will
 then be guaranteed a ‘clean’ SIS file with the correct binaries inside it and
 without any developer certificates attached.