02-22-2011 12:02 PM
ZanuZawa, I don't personally know you but would be sticking my neck out for you by doing the certificate. Surely parents, family members, or a colleague would be willing to assist? Even perhaps a professor?
It'd be different if you lived around the corner and I could stop over to smack you over the head for getting me in trouble
02-22-2011 12:47 PM
@jtegen @peter9477 : thanks for the replies guys.
@JohnPinkerton : nevermind, maybe the situation between my country with your country is different, I live in a small town so many people in here more often use the money in cash rather than credit card. anyway, thanks.
02-24-2011 05:52 PM
To get back to technical, about page:
I'm not sure about the first step:
blackberry-signer -csksetup -cskpass <create_a_password>
Is a param missing ?
From what I read in other post, it "may" be:
blackberry-signer -csksetup -cskpass -storepass <create_a_password>
02-24-2011 05:58 PM
In case it helps, these things do have some built-in help, not that it directly answers that question:
c:\> blackberry-signer -help Usage: blackberry-signer -cskpass <csk-password> [<options>] <bar-file> <rim-key-name> blackberry-signer [<options>] <bar-file> <alias> blackberry-signer -verify [<options>] <bar-file> blackberry-signer -csksetup -cskpass <csk-password> [<options>] blackberry-signer -cskdelete [<options>] blackberry-signer -register -cskpass <csk-password> -csjpin <csj-pin> [<options>] <csj-file> Where: <alias> - name of key in local keystore <bar-file> - input/output bar file <csj-file> - input csj file for registration <rim-key-name> - name of registered RIM key <options> are: -csksetup - generate new long-lived keys into csk file -cskdelete - delete long-lived keys in csk file -cskpass <csk-password> - password to encrypt long-lived keys -register - register with RIM signing server using csj file -csjpin <csj-pin> - PIN associated with csj file -keystore <url> - keystore location -storepass <password> - password for keystore integrity -storetype <type> - keystore type -keypass <password> - password for private key (if different) -sigfile <file> - name of .SF/.DSA file -signedbar <file> - name of signed bar file -digestalg <algorithm> - name of digest algorithm -sigalg <algorithm> - name of signature algorithm -verify - verify a signed bar file -verbose - verbose output when signing/verifying -certs - display certificates when verbose and verifying -tsa <url> - location of the Timestamping Authority -tsacert <alias> - public key certificate for Timestamping Authority -altsigner <class> - class name of an alternative signing mechanism -altsignerpath <pathlist> - location of an alternative signing mechanism -internalsf - include the .SF file inside the signature block -sectionsonly - don't compute hash of entire manifest -protected - keystore has protected authentication path -providerName <name> - provider name -providerClass <class> (-providerArg <arg>)* - name of cryptographic service provider's master class file and constructor arguments
02-25-2011 06:07 AM
so it looks like it's actually
blackberry-signer -csksetup -cskpass <password>
as specified in the official page.
(Well I'll "try" anyway, but I would like to have a clean howto before starting....)
02-25-2011 03:21 PM
I signed and submitted my app (and got the signed version approved) but I just got an email today saying that we should submit it as "<bundlename>_signed".
Do I need to resubmit this/get this changed or is it fine as is?
02-26-2011 08:41 AM
02-26-2011 12:35 PM
i think the email only applies to those who havent gotten their applications signed and approved already. i think its just their way of sorting through the pile of applications faster visually.
02-26-2011 02:39 PM
Do we get a email once its signed? I did run through the steps and got this:
so then I signed. but I didnt get an email say it signed.
02-26-2011 02:42 PM