keytool

问题 I am adding google-maps-api for the my hellomapview progam for android appilication developement refering the website [http://developer.android.com/guide/tutorials/views/hello-mapview.html][1] .Before generating the api key it ask for md5-signature certificate.So when try to create md5 certificate using keytool via commandline in windows i got the following error.Please guide to this clear this error or how to set password and what is the default password for keytool. Error: C:\Documents and

问题 I am trying to sign an APK manually using APK signer using this code apksigner sign --ks D:\Android\SDK\keystores\release.keystore --ks-key-alias uploadcertificate --out app-release.apk app.apk but it's giving me an error saying that Failed to load signer "signer #1": D:\Android\SDK\keystores\release.keystore entry "uploadcertificate" does not contain a key however, when I use keytool to list the aliases in my keystore, I am able to see the alias uploadcertificate. keytool -v -list -keystore

问题 I have a keystore (keytool key storage), which is used for signing .apk's from Eclipse-ADT. Due to the extremely annoying password requests at each export, I'm trying to figure out how to avoid reentering password. My current options are: by using Perl/X1::::XTEST, automate password entering (insecure) hack Eclipse to cache passwords (potentially insecure, explicit timeloss) remove keystore password, which seems to be the best possible idea Attempt to set empty password failed: >> keytool

问题 We have a jck keystore (jceks) format containing a secret key. It was generated using keytool command keytool -genseckey -alias mykey -keyalg AES -keysize 256 -storetype jceks -keystore mykeystore.jks We need to share this with another application and they seem to have limitations in working with jck store. They are asking for the key to be exported and supplied to them. We tried a few tools, but are not able to export the secret key. Is there a command or workaround to achieve this ? 回答1:

问题 I am trying to create a PKCS12 keystore file using Java API. However as soon as I try to import the certificate I get the exception java.security.KeyStoreException: TrustedCertEntry not supported my code is: Provider p = Security.getProvider(BouncyCastleProvider.PROVIDER_NAME); ... KeyStore keyStore = KeyStore.getInstance("PKCS12"); keyStore.load(null, keystorePass); keyStore.setCertificateEntry("certificate", certificate); keyStore.setKeyEntry("key",privateKey, keypass, certChain); The same

问题 I am signing the jar file. The certificate provided by VeriSign. It provide 2 certificates: aplha-primary.cer and aplha-secoandary.cer I generate the keystore file using the following commands: keytool -importcert -v -alias -primary -keystore keystore/keystore.jks -file aplha-primary.cer and keytool -importcert -v -alias -secoandary -keystore keystore/keystore.jks -file aplha-secoandary.cer It is exported to keystore file. when I tried to sign the jar file it's giving the exception like

问题 I am trying to create a "bks" keystore using keytool (using terminal app on Mac OS X). I am following the instructions in: keytool error: java.security.KeyStoreException: BKS not found This is my usage: keytool -genkeypair -v -alias androiddebugkey -keyalg RSA -keysize 2048 -validity 10000 -keypass android -keystore /Users/djames/dropbox/bc146keystore/debug.keystore -storepass android -storetype BKS -providerclass org.bouncycastle.jce.provider.BouncyCastleProvider –providerpath /Users/djames

问题 It seems to me that there are hardly any good tools out there that help webapp deployers secure their environment. I feel like a lot of deployment grief comes in because the admin hasn't been properly tooled to ignore the intricacies and of TLS/SSL. I once had the good luck of seeing a really good UI management that was intuitive, for an admin of any level, in either websphere or weblogic (i forget) but nothing like that is available today out in the open source community. I would like to put

问题 I have a gradle-based android project and trying to generate a release apk. However, it seems that somehow gradle is picking up the wrong key/cert. This is what I have in build.gradle: signingConfigs { release { storeFile file("mykey.jks") storePassword "mypass" keyAlias "mykey.key" keyPassword "mypass" } } buildTypes { release { debuggable false jniDebugBuild false runProguard true proguardFile getDefaultProguardFile('proguard-android.txt') signingConfig signingConfigs.release } } And after

问题 I'm trying to create a keystore using keytool with a keyalg ECC. This should be possible according to Oracle. I quote: Area: Tools Synopsis: The keytool and jarsigner tools now support the ECC algorithm in keypair generation and jar signing. RFE: 6870812 I'm using the 32-bit version 1.7.0_07, and I've tried keytool with -keyalg ECC, ECIES, ECDSA,... but I always get Cannot derive signature algorithm . Am I using the wrong Java version? Am I using the wrong name for ECC? 回答1: Here is the