Difference between revisions of "Symbian OS Platform Security/Errata"

From Franklin Heath Ltd Wiki
Jump to: navigation, search
m (7 revisions: import from developer.symbian.org)
(note that these errata are now fixed in the wiki edition, and include corrections)
Line 1: Line 1:
Book: [[Symbian Press Books#SymbianOSPlatformSecurity|Platform Security on Symbian OS]]
+
Book: [[Symbian OS Platform Security]]
  
 +
These errata apply to the paper edition; they have been corrected in this wiki edition.
  
Page 102-103
+
===Pages 102-104===
* The table on 102 says 8 maps to 8 maps to 1 maps to C2 and EPanicClient.
+
* Directly opposite on 103 the text walks through this example, but says the action is {{Icode|EFailClient}} not {{Icode|EPanicClient}}. If we are panicing, {{Icode|KErrPermissionDenied}} is not returned. So either the diagram needs correcting, in which case there wouldn't be any {{Icode|EPanicClient}} examples in the diagram and there needs to be one from a teaching point of view; or the text needs to be corrected. I'd get back to the author as he'll know what he wants to achieve.
+
  
Page 104
+
Issues:
* The first paragraph "If you get confused..." is a combination of wrong, misleading and difficult to understand:
+
*The text states that lack of the appropriate capability for IPC number 8 in figure 5.1 would complete the message with a {{Icode|KErrPermissionDenied}} error code, but the figure shows an {{Icode|iAction}} of {{Icode|EPanicClient|}}.
** the IPC number does not go through a reverse lookup, currently a binary chop search is used in {{Icode|CPolicyServer::FindPolicyElement();}}
+
*The code sample shows the {{Icode|iPolicy}} for the {{Icode|iOnConnect}} element as a {{Icode|C1}} (single capability) policy, but the figure shows {{Icode|S2}}.
** the sentence also uses the term "forward lookup" twice, this is not a term I've found having looked in several computing dictionaries.
+
*The phrases "reverse lookup" and "forward lookup" on p.104 are unclear.
 +
 
 +
Corrections:
 +
*p.102 (figure 5.1): {{Icode|iAction}} for {{Icode|iElements[1]}} should be {{Icode|EFailClient}}
 +
*p.102 (figure 5.1): {{Icode|iPolicy}} for {{Icode|iElements[3]}} should be {{Icode|C1}}
 +
*p.102 (figure 5.1): {{Icode|iAction}} for {{Icode|iElements[3]}} should be {{Icode|EPanicClient}}
 +
*p.104: second initialiser for {{Icode|myElements[1]}} should be {{Icode|CPolicyServer::EFailClient}}
 +
*p.104: second initialiser for {{Icode|myElements[3]}} should be {{Icode|CPolicyServer::EPanicClient}}
 +
*p.104 first paragraph of text should read "The process followed to look up the appropriate {{Icode|TPolicyElement}} could be confusing so, to summarize:  The IPC number is first used to do a binary search in {{Icode|iRanges}}; the index of the result (the ''range index'') is then used as an index into {{Icode|iElementsIndex}}, and the result of that (the ''policy index'') is used as an index into {{Icode|iElements}}."
  
 
<!-- Categories -->
 
<!-- Categories -->
 
[[Category: Book|Errata]]
 
[[Category: Book|Errata]]

Revision as of 01:41, 28 December 2010

Book: Symbian OS Platform Security

These errata apply to the paper edition; they have been corrected in this wiki edition.

Pages 102-104

Issues:

  • The text states that lack of the appropriate capability for IPC number 8 in figure 5.1 would complete the message with a KErrPermissionDenied error code, but the figure shows an iAction of EPanicClient.
  • The code sample shows the iPolicy for the iOnConnect element as a C1 (single capability) policy, but the figure shows S2.
  • The phrases "reverse lookup" and "forward lookup" on p.104 are unclear.

Corrections:

  • p.102 (figure 5.1): iAction for iElements[1] should be EFailClient
  • p.102 (figure 5.1): iPolicy for iElements[3] should be C1
  • p.102 (figure 5.1): iAction for iElements[3] should be EPanicClient
  • p.104: second initialiser for myElements[1] should be CPolicyServer::EFailClient
  • p.104: second initialiser for myElements[3] should be CPolicyServer::EPanicClient
  • p.104 first paragraph of text should read "The process followed to look up the appropriate TPolicyElement could be confusing so, to summarize: The IPC number is first used to do a binary search in iRanges; the index of the result (the range index) is then used as an index into iElementsIndex, and the result of that (the policy index) is used as an index into iElements."