Hello,
I am trying to add a certificate to several Android devices. One is a Droid X (2.2 Froyo) and another is a Xoom (3.0 Honeycomb). I've converted the certificate to the correct format and added it but it seems like it never adds it to the correct store. Everything I've read says I have to root the device to to modify the certificate manager on the devices. What am I missing? Thanks!
Related
Hi,
I have a problem with installing p12 certificate to my samsung galaxy S (android 2.1)...I export certificate as pfx file from internet explorer...import to firefox and export as p12 file...this file copied to my phone and try to install, but it still asks for password, even I input correct one.
I found this problem for example here (***.google.com/support/forum/p/android/thread?tid=7fbf6c44175dca0b&hl=en) but no answer how to fix it
Hi, does anybody knows if this is bug of the system and will be fix in android 2.2 or, it can be fixed without updating the system to newer version?
thanks
im having the same issues as u are. try to install the p12 file to my Legend but somehow keep on asking for password....hmmm wonder why...
Same here. No password looks good for certificate extraction
Android 2.1
Maybe the problem is 2.1?!
Same problem here. My phones I am running 2.3.3 VillianROM on S5830. [email protected]#$% the password for the .p12. HELP!! Someone Please!!!
Hi there,
I have downloaded a root CA certificate and now I want to install it on my Android Froyo device (HTC Vision / Desire Z / G2), so that the device trusts the certificate and does not complain about an untrusted certificate every time I start an SSL connection.
Android stores CA certificates in its Java keystore in /system/etc/security/cacerts.bks. I copied the file to my computer, added my certificate using portecle 1.5 and pushed it back to the device.
Now, Android does not seem to reload the file automatically. I have read in several blog posts that I need to restart the device. Doing so results in the file being overwritten with the original one again.
My next try was to install the certificate from SD card by copying it and using the according option from the settings menu. The device tells me that the certificate has been installed, but apparently it does not trust the certificate. Moreover, when I try to copy the keystore to my computer, I still find the original stock cacerts.bks.
Is there any way to add my certificate to the trusted ones? What mechanism restores the original keystore on every boot? Can I reload the keystore without rebooting? This would be at least a preliminary solution. Is there a chance do do it programmatically?
Thanks in advance!
Hi!
At Windows-Firefox I do as follows:
1. Logging into electronic banking site with user name and password
2. At my own profile settings there is a button for installing the CA certificate (direct import into Firefox, no download at PC first and no extra clicking on downloaded file)
3. Installing my own .p12 certificate-file from my PC, (I have the file from the bank)
4. Initializing and electronic signing of transactions etc.
Due to settings from the bank, it works, of course, only if I install the CA certificate from the site first, and after that I install my own .p12 certificate.
So, the same thing, I am trying to do at Android 4, Xperia Mini (not Xperia Mini X10), Android own build in browser.
Here are the steps:
1. Downloading the .crt (not .cer!) file of the CA certificate from the site into my PC, then copying the same .crt file into the main directory of my Xperia internal SD card.
2. Copying the .p12 certificate file from my PC into the main directory of my Xperia internal SD card.
3. Installing the CA certificate from the .crt file at the security settings of Android
4. Installing the .p12 certificate at the security settings of Android
5. Logging in at the Android own build in browser
The pop-up with the correctly installed certificate (.p12) shows normally by logging in. So I am able to get into initializing of a transaction.
But at the confirmation of the electronic signing of the transaction, I am getting a pop-up "unknown error"
Could someone help?
I have no idea about the certificate stuff, but have you tried if Firefox for Android handles them the same way?
[Q] Difficulties with electonic banking certificate
post-mortem said:
I have no idea about the certificate stuff, but have you tried if Firefox for Android handles them the same way?
Click to expand...
Click to collapse
FF for Android had only for the 13 Beta (Fennec) Version an addon (Cert Manager), which is no more compatible with Android 4...
I already contacted the developer... There are still no compatible updates, so we can temporarily forget about working with such certificates on Android-FF...
Hey guys,
I have a vanilla non-rooted Nexus 5 and i'm trying to get Lync 2013 to work. it installs, i find the lync server fine and i installed the cert but it still says cannot verify the certificate.
I install the exported cert into my N5 and it says it installs but under User Certificates nothing is listed.
Here is what i have found on the interwebs:
https://android.stackexchange.com/q...laims-success-but-android-acts-as-if-cert-isn
I have not tried the above because i am not in front of a linux terminal right now. My fear is unless i do this from the lync server, my cert wont be signed with the correct key so it work anyways.
I have tried taking the cert i have and exporting from IE into the DER format but that doesnt work either.
Anyone have any ideas?
Shaner
Hello everybody,
I recently purchased a Palm Pre 1 running webOS 1.4.5. I unlocked, devmoded it and installed Preware. Now, e-mail does not work because of SSL errors, and websites annoy asking me to trust every certificate manually. What I tried to fix it, is to download the Root Certicate Update from Preware, I also copied the certificates from my Ubuntu machine to /usr/lib/ssl certs. All of this didn't work, but I found out that it might have something to do with a new certificate format (which uses sha-256 or something).
So I installed the alpha version of this here: https://forums.webosnation.com/webos-internals/330666-openssl-updater-fixing-certificate-issues.html but it didn't work either.
So my question is: Is there a way to get webOS 1.4.5 to work with the interweb of today properly?
I'd thank you for any comment!
Yours sincerely,
Jano