11-23-2009 08:26 AM
In this case, try appending your license key as a "signature" to the module. See my earlier post for details.
11-23-2009 08:42 AM
Will try that. This is new territory for me though. How does this signature coexist with the already existing signature for the signed cod?
11-23-2009 08:46 AM - edited 11-23-2009 08:48 AM
All signatures are appended to the end of the module. You can freely append one more -- this won't overwrite or remove the previously appended signatures (those obtained via the Signature Tool). Also, since your signature will use a non-standard signer ID, the OS will not be automatically verifying it against the contents of the module.
11-23-2009 08:48 AM
Cool! That seems to be the solution then. Thanks a lot!
Ps. I mark your first post as the accepted solution.
11-23-2009 08:48 AM
I suggest you first confirm that it works for you.
12-18-2009 09:27 AM
The solution worked for me. But only 128 Byte signatures worked. If more data is needed you have to divide it into more signatures.
12-18-2009 09:35 AM
Interesting! Have you tried modifying the value of the "signature length" byte?
12-18-2009 09:38 AM
Yes I did, signature was ok in the signature tool. But on the device the returned certificate was equal null.