Bug 29492

Summary: Correction of Symbian UID3 values
Product: WebKit Reporter: Norbert Leser <norbert.leser>
Component: WebKit QtAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: commit-queue, hausmann, laszlo.gombos, yongjun.zhang
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: S60 Hardware   
OS: S60 3rd edition   
Bug Depends on:    
Bug Blocks: 27065    
Attachments:
Description Flags
Patch with corrected UID3 values none

Norbert Leser
Reported 2009-09-18 10:02:19 PDT
Created attachment 39764 [details] Patch with corrected UID3 values Symbian executable components are identified on the device by unique UID3 values. There are multiple categories of these values, providing different protection levels. The 11 demo and test components submitted in this patch either had UID3s assigned that were from a "protected" pool, or some new demos/tests such as QGVLauncher did not have any assigned yet. The new values are from a range (above 0xA0000000) that allow for self-signing, which is needed for 3rd-party developers to utilize these components.
Attachments
Patch with corrected UID3 values (5.89 KB, patch)
2009-09-18 10:02 PDT, Norbert Leser
no flags
Eric Seidel (no email)
Comment 1 2009-09-18 11:38:05 PDT
Comment on attachment 39764 [details] Patch with corrected UID3 values Rubber-stamped. I can't remember if you're a committer or not, so not setting cq+. You can set cq=? if you want someone to mark this for auto-commit.
Norbert Leser
Comment 2 2009-09-18 11:54:58 PDT
Comment on attachment 39764 [details] Patch with corrected UID3 values Already reviewed by Eric Seidel, but I'm not a committer
WebKit Commit Bot
Comment 3 2009-09-18 13:49:17 PDT
Comment on attachment 39764 [details] Patch with corrected UID3 values Clearing flags on attachment: 39764 Committed r48528: <http://trac.webkit.org/changeset/48528>
WebKit Commit Bot
Comment 4 2009-09-18 13:49:23 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.