Bug 29492 - Correction of Symbian UID3 values
Summary: Correction of Symbian UID3 values
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Qt (show other bugs)
Version: 528+ (Nightly build)
Hardware: S60 Hardware S60 3rd edition
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 27065
  Show dependency treegraph
 
Reported: 2009-09-18 10:02 PDT by Norbert Leser
Modified: 2009-09-18 13:49 PDT (History)
4 users (show)

See Also:


Attachments
Patch with corrected UID3 values (5.89 KB, patch)
2009-09-18 10:02 PDT, Norbert Leser
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Norbert Leser 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.
Comment 1 Eric Seidel (no email) 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.
Comment 2 Norbert Leser 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
Comment 3 WebKit Commit Bot 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>
Comment 4 WebKit Commit Bot 2009-09-18 13:49:23 PDT
All reviewed patches have been landed.  Closing bug.