CCNA, CCNP, MCSA, CCNA Final Exam, All Answer Test Module With 100/100

I need to use to key-pair in one socket ssl connection without change nothing in clients. Why? Because one client use a CN attribute in trust store for connection handshake and other clients using another value in the same attribute to process the same task in the same way. So I need to use two key store (private) with distinct CN attributes and also aliases and share two different trust store (public key) with distinct CN attributes and also aliases too. Describing bellow: keyStore1 Keystore type: JKS Keystore provider: SUN ... Alias name: identity1 ... Owner: CN=app1, OU=..., ... Issuer: CN=app1, OU=..., ... ... keyStore2 ... Alias name: identity2 ... Owner: CN=app2, OU=..., ... Issuer: CN=app2, OU=..., ... trustStore1 ... Alias name: identity1 ... Owner: CN=app1, OU=..., ... Issuer: CN=app1, OU=..., ... ... trustStore2 ... Alias name: identity2 ... Owner: CN=app2, OU=..., ... Issuer: CN=app2, OU=..., ... I tried to implement this feature in this way: KeyStore Key

I am developing android apps on my very personal computer. Securing the keystore to sign android apps seems to me to be overkill. Securing is usally a pain, so I would apply it only when I get any realistic advantage. The android docs only talk about other users on the same computer, but that is not valid in my case. Is there any rational need to secure a keystore on a secured personal machine? Is there any rational need to use strong password on a keystore on a secured personal machine?