keystore

Certificate on the client's side?

佐手、 提交于 2020-01-05 10:14:17
问题 I have a server application and a client application. The server uses https, and has a .jks file. Apart from that, I use authentication with login and password. I wonder if the client side should use a .cert certificate. I thought the client's certificate should match servers certificate, but it seems that I was wrong. I have some troubles understatding the topic, so please be understanding. 回答1: Keystore A Java KeyStore (JKS) is a repository of security certificates – either authorization

How to import RSA private key, which generated by openssl, into AndroidKeyStore

好久不见. 提交于 2020-01-03 09:28:21
问题 I would like to import into AndroidKeyStore a key. So, I can generate it by openssl in following way openssl rsa -text -in privateKey2048.pem openssl pkcs8 -topk8 -inform PEM -in ./privateKey2048.pem -outform DER -out private2048.der -nocrypt then I can convert it from private2048.der into hex format, which can be converted in byteArray in android app. But it's not clear for me, How to import this byteArray into AndroidKeyStore? So in general, my question is how import into KeyStore key which

Should the trusted Root CA be a part of the certificate chain?

早过忘川 提交于 2020-01-03 04:15:13
问题 I'm setting up 2-way SSL communication between services on different hosts. Let's say I have my own CA called A. A is trusted by all of my services through a centralized jks. Now let's say I have certificate B signed by A. When services send the certificate should they be sending the entire chain B - A, or just B? I believe both tend to work with most implementations. I tried to find canonical information about this online, but I'm coming up with nothing. Thanks for the help 回答1: As per tls -

Should the trusted Root CA be a part of the certificate chain?

自闭症网瘾萝莉.ら 提交于 2020-01-03 04:15:06
问题 I'm setting up 2-way SSL communication between services on different hosts. Let's say I have my own CA called A. A is trusted by all of my services through a centralized jks. Now let's say I have certificate B signed by A. When services send the certificate should they be sending the entire chain B - A, or just B? I believe both tend to work with most implementations. I tried to find canonical information about this online, but I'm coming up with nothing. Thanks for the help 回答1: As per tls -

Use BouncyCastle PKCS12SafeBagBuilder or PKCS12BagAttributeCarrier to change PKCS12 safe bag attributes when writing KeyStore to file in Android?

♀尐吖头ヾ 提交于 2020-01-03 03:42:27
问题 I am trying to write a private key and associated signed certificate to a PKCS12 (.p12) file on an Android device using BouncyCastle 1.47 ( bckpix-jdk15on-147.jar and bcprov-jdk15on-147.jar ) and would like to change the key encryption algorithms and other bag attributes. I am trying to implement the same control available to OpenSSL's PKCS12_create() function, where you can set: the private key encryption algorithm the certificate encryption algorithm the encryption iteration count the MAC

Android->Settings->Security->StorageType get Value inside app

南笙酒味 提交于 2020-01-03 03:30:09
问题 In newer versions of Android (I guess since 4.2) there is an option called "hardware-backed" and "software only". As Google supposes: Android also now supports hardware-backed storage for your KeyChain credentials, providing more security by making the keys unavailable for extraction. That is, once keys are in a hardware-backed key store (Secure Element, TPM, or TrustZone) , they can be used for cryptographic operations but the private key material cannot be exported. Even the OS kernel

ECDH with key in Android Key Store

安稳与你 提交于 2020-01-02 10:18:29
问题 I'm developping an Android App that generates an EC Asymetric key. When my app gets connected to a device, they exchange their public key. They then use ECDH to establish a shared secret. This shared secret is then used to derive an AES session key. All this is working fine. I'm now working on the storage of the asymetric key. I wanted to put it in the Android KeyStore but I don't see how I can then do the ECDH operation. The key in the key store can be used to sign, decrypt or encrypt but I

Why java uses default location keystore/truststore of JAVA_HOME/lib/security/cacerts though I have supplied -Djavax.net.ssl.trustStore properties

雨燕双飞 提交于 2020-01-02 07:25:47
问题 In my java application I am running with supplied -Djavax.net.ssl.trustStore System properties as below. -Djavax.net.ssl.trustStore=/myapp/app.jks -Djavax.net.ssl.trustStorePassword=XXXXX -Djavax.net.ssl.trustStoreType=jks -Djavax.net.debug=ssl This is my Complete command line : $JAVA_HOME/bin/java -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp -Xms512m -Xmx1024m -XX:MaxPermSize=192m -Djavax.net.ssl.trustStore=/myapp/app.jks -Djavax.net.ssl.keyStore=/myapp/app.jks -Djavax.net.ssl

Why java uses default location keystore/truststore of JAVA_HOME/lib/security/cacerts though I have supplied -Djavax.net.ssl.trustStore properties

此生再无相见时 提交于 2020-01-02 07:25:11
问题 In my java application I am running with supplied -Djavax.net.ssl.trustStore System properties as below. -Djavax.net.ssl.trustStore=/myapp/app.jks -Djavax.net.ssl.trustStorePassword=XXXXX -Djavax.net.ssl.trustStoreType=jks -Djavax.net.debug=ssl This is my Complete command line : $JAVA_HOME/bin/java -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp -Xms512m -Xmx1024m -XX:MaxPermSize=192m -Djavax.net.ssl.trustStore=/myapp/app.jks -Djavax.net.ssl.keyStore=/myapp/app.jks -Djavax.net.ssl

Use provided upload_cert.der to sign a release Android APK file

邮差的信 提交于 2020-01-02 03:33:47
问题 I've just enrolled in the Google Play App Signing program, which required uploading an encrypted version of the release keystore and had an "optional" step for creating an upload keystore - optional is in quotes, because I think it should be a required step, but anyway, after a successful enrollment, I'm now left with an Upload certificate , which I should somehow use to sign my future app releases. What I've done so far: I created a new keystore from Android Studio, set the store and alias