10-25-2008 09:06 PM
I am running the BlackBerry Password Based Code Signing Authority for my own signer service.
I have created the key and sent the csi file to myself and have gone through the registration process with my server
However, when I try to sign my code using the SignatureTool it still shows my key as not registered with the authority.
Has anyone else had success with this?
BTW: I also have some errors/bugs/oversights to report on this tool. What is the best way to provide that feedback?
Solved! Go to Solution.
10-25-2008 09:39 PM
I don't know if this is a good sign or a bad sign but I have solved my own problem.
I am using the 4.2.1 tools so maybe this is fixed in later releases. however, in order to fix my problem I had
to manually add my key into the sigtool.db file so that the SignatureTool would acknowledge the signing authority.
Just doubleclicking the .csi file and going through the registration with my signing authority did not do this for me.
Here are my entries in the sigtool.db
#The database file containing information for requesting signatures.
#Sun Mar 04 10:36:09 EST 2007
I had to add the last line which is my signing key. The LHS is the key ID the number on the RHS is the Client ID that should
show up in your Remote Client Administration tool when you provision a key to a user (in this case myself). the rest is the url
to the signing service (in my case my local machine on port 3600)
Kudos to me.