BlackBerry10 application is not signing properly due to keystore issue - blackberry-10

I am creating a sencha application and i want to run it on BB10 device. I have requested for signin Key files from BlackBerry and received two .csj registration files by mail . For signing my application i am using this command :
blackberry-signer –register –csjpin 01234567 –storepass mcube F:\BB10Key-28Feb\client-PBDT-1975809.csj F:\BB10Key-28Feb\client-RDK-1975809.csj
It gives error :
"Error: Keystore load: DerInputStream.getLength(): lengthTag=109, too big."
I don't have any idea about it that how it will be solve .

Welcome to StackOverflow.com
I think you are passing wrong files to the signer.
blackberry-signer -register -csjpin <csj pin>
-storepass <KeystorePassword> <client-RDK-xxxxxx.csj file>
<client-PBDT-xxxxx.csj file>
I see you are passing PBDT key first in place of RDK key.
Your code would be like this (please do not copy paste this command when signing yourself as this is for demo puposes only)
blackberry-signer –register –csjpin 01234567 –storepass mcube F:\BB10Key-28Feb\client-RDK-1975809.csj F:\BB10Key-28Feb\client-PBDT-1975809.csj
You should pass RDK key then PBDT key. Modify your bar signer tool command and run again with correct parameters. For more info visit Set up for signing BlackBerry 10 apps and Signing your BlackBerry 10 application.
If this solves your problem, check this as answer.

Related

During enabling Xcode Server fails with "Could not export API server SSL..."

After updating Xcode to latest version Xcode Server can not be turned on. It fails with error:
Could not export API server SSL certificate: Error Domain=XCSSecurity Code=-1 "OpenSSL: Error decrypting key
4304406060:error:06FFF089:digital envelope routines:CRYPTO_internal:bad key length:/System/Volumes/Data/SWE/macOS/BuildRoots/5b2e67f8af/Library/Caches/com.apple.xbs/Sources/libressl/libressl-75.60.3/libressl-2.8/crypto/apple/hmac/hmac.c:188:
4304406060:error:06FFF078:digital envelope routines:CRYPTO_internal:keygen failure:/System/Volumes/Data/SWE/macOS/BuildRoots/5b2e67f8af/Library/Caches/com.apple.xbs/Sources/libressl/libressl-75.60.3/libressl-2.8/crypto/evp/evp_pbe.c:166:
4304406060:error:23FFF073:PKCS12 routines:func(4095):pkcs12 algor cipherinit error:/System/Volumes/Data/SWE/macOS/BuildRoots/5b2e67f8af/Library/Caches/com.apple.xbs/Sources/libressl/libressl-75.60.3/libressl-2.8/crypto/pkcs12/p12_decr.c:83:
4304406060:error:23FFF075:PKCS12 routines:func(4095):pkcs12 pbe crypt error:/System/Volumes/Data/SWE/macOS/BuildRoots/5b2e67f8af/Library/Caches/com.apple.xbs/Sources/libressl/libressl-75.60.3/libressl-2.8/crypto/pkcs12/p12_decr.c:133:
" UserInfo={NSLocalizedDescription=OpenSSL: Error decrypting key
4304406060:error:06FFF089:digital envelope routines:CRYPTO_internal:bad key length:/System/Volumes/Data/SWE/macOS/BuildRoots/5b2e67f8af/Library/Caches/com.apple.xbs/Sources/libressl/libressl-75.60.3/libressl-2.8/crypto/apple/hmac/hmac.c:188:
4304406060:error:06FFF078:digital envelope routines:CRYPTO_internal:keygen failure:/System/Volumes/Data/SWE/macOS/BuildRoots/5b2e67f8af/Library/Caches/com.apple.xbs/Sources/libressl/libressl-75.60.3/libressl-2.8/crypto/evp/evp_pbe.c:166:
4304406060:error:23FFF073:PKCS12 routines:func(4095):pkcs12 algor cipherinit error:/System/Volumes/Data/SWE/macOS/BuildRoots/5b2e67f8af/Library/Caches/com.apple.xbs/Sources/libressl/libressl-75.60.3/libressl-2.8/crypto/pkcs12/p12_decr.c:83:
4304406060:error:23FFF075:PKCS12 routines:func(4095):pkcs12 pbe crypt error:/System/Volumes/Data/SWE/macOS/BuildRoots/5b2e67f8af/Library/Caches/com.apple.xbs/Sources/libressl/libressl-75.60.3/libressl-2.8/crypto/pkcs12/p12_decr.c:133:
}
Development and Xcode Server runs on the same Mac machine.
I have tried to restart xcscontrol, but it did not help.
sudo xcscontrol --reset
In my case here is no SWE folder at this location:
/System/Volumes/Data
How I could fix "Could not export API server SSL..." error?
It looks that needs to install macOS 12.3 beta and use Xcode 13.3 beta or 13.2.1.
If here is another way on fixing this problem I would like to know.
More discussion can be found here.

Unity 3D -- Failed to sign APK - while i have given correct keystore and password

i was building my sign apk, there was no issue. but suddenly its start giving me error of "Failed to sign APK Package."
my keystore is correct,
password is correct,
alias is correct....
** This is the error below **
Failed to sign APK package.
D:\Plugins\Android_SDK\build-tools\27.0.3\apksigner.bat sign --ks "G:/__KeyStore/ormeoo.keystore" --ks-pass stdin --ks-key-alias "ormeoo" --key-pass stdin "F:\Projects\Current Working_2\OR - 98% Impossible Monster Car\Temp/StagingArea/Package.apk"
Perhaps another work around;
Try changing the Build System to Gradle (New) instead of Internal (Default).
Hope it helps..

How to resolve error Salt must be 8 bytes long

I am writing a program to sign a pdf using certificate (pfx file). For few of the certificates I am getting below exception.
java.security.InvalidAlgorithmParameterException: Salt must be at least 8 bytes long
This happens when I execute the below code.
Keystore ks = KeyStore.getInstance("pkcs12");
I am getting an exception in the below java file at line number 123.
http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/8-b132/com/sun/crypto/provider/HmacPKCS12PBESHA1.java?av=h
Your keystore has one or more certificate(s) that has a salt length which is less than 8. The crypto program requires atleast 8 bytes.
I would recommend creating a new keystore with just the one certificate that you need and try signing with that.
I resolved the exception using pkcs12-DEF keystore. I have added my code lines below.
BouncyCastleProvider provider = new BouncyCastleProvider();
Security.addProvider(provider);
KeyStore ks = KeyStore.getInstance("pkcs12-DEF");
Earlier I had not added BountyCastleProvider to Security, because of which I was not able to get instance of pkcs12-DEF keystore.
Apart from this I have also downloaded jar files from http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html location and replaced it with jar files present in Java\Jdk1.7\jre\lib\security. These are JCE 7 Unlimited strength policy files.

Corona iPhone Deployment Warning

I have developed a game using corona. Now I get this warning while trying to build for iPhone using new provisioning profile.
warning: Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate. (-19011)
failed to extract requirements data: 1
/Users/codemenmini2012-4/Desktop/ArcheryClassiciOS.app: invalid signature (code or signature have been modified)
failed to extract entitlements: 1
AssertMacros: entitlements_requested, At least need an application-identifier entitlements file: codesign_wrapper.c, line: 879
- (null)
warning: Unable to extract codesigning entitlements from your application. Please make sure ArcheryClassiciOS is a valid Mach executable that's properly codesigned. (-19050)
/Users/codemenmini2012-4/Desktop/ArcheryClassiciOS.app/ArcheryClassiciOS: invalid signature (code or signature have been modified)- (null)
Have you tried revoking the Profile and requesting it again with a key from your machine? Apples profiles are annoying me quite often, too....

Exception while creating sp.xml using ssoadmin

I am facing this exception when I trying to create the sp.xml using the ssoadmin :
com.sun.identity.cli.CLIException: AdminTokenAction: FATAL ERROR: Cannot obtain Application SSO token.
Check AMConfig.properties for the following properties
com.sun.identity.agents.app.username
com.iplanet.am.service.password
at com.sun.identity.cli.LogWriter.log(LogWriter.java:109)
at com.sun.identity.cli.Authenticator.ldapLogin(Authenticator.java:170)
at com.sun.identity.cli.AuthenticatedCommand.ldapLogin(AuthenticatedCommand.java:144)
at com.sun.identity.federation.cli.CreateMetaDataTemplate.handleRequest(CreateMetaDataTemplate.java:113)
at com.sun.identity.cli.SubCommand.execute(SubCommand.java:291)
at com.sun.identity.cli.CLIRequest.process(CLIRequest.java:212)
at com.sun.identity.cli.CLIRequest.process(CLIRequest.java:134)
at com.sun.identity.cli.CommandManager.serviceRequestQueue(CommandManager.java:573)
at com.sun.identity.cli.CommandManager.(CommandManager.java:171)
at com.sun.identity.cli.CommandManager.main(CommandManager.java:148)
And I also tried adding something like this in the ssoamdin.bat :
-D"com.iplanet.am.naming.map.site.to.server=https://lb.example.com:443/openam=http://server1.example.com:8080/openam"
But the same exception...
How to fix it?
Thanks in advance,
The 'map-to-site' property is only needed if you have a site configured an the host where you run ssoadm is not able to talk to the siteURL.
You may set -Dcom.iplanet.services.debug.level=message -Dcom.iplanet.services.debug.directory=WRITABLE_EXISTING_DIRECTORY' as JVM options within ssoadm.bat.
You may then look into the debug directory you should find a pointer what's wrong.
The above got sorted in my case when i went to the ssoadmin folder openam/bin and found the ssoadm.bat file and opened it in the edit mode and added the following two lines in the java comaand :
-D"javax.net.ssl.trustStore=F:\tomcatsslkeystore" (tomcat keystore path)
-D"javax.net.ssl.trustStorePassword=tomcatsslkeystore" (tomcat keystore password)