self-signed CA cert

Hi experts,

I've got a self-signed cert working fine in windows.  When I try to import this certificate into the android trusted store, I can't because it doesn't have the CA cert flag set.  Is there a quick fix for this?  I'm not interested in getting any third party signer involved.

I'm aware that all users will have to import my certificate into their trusted root certificate stores - that's exactly what I want.

If possible using keytool, I'd prefer that over OpenSSL.

Thanks!
Mike
LVL 1
threadyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

btanExec ConsultantCommented:
do see the below example using the root certificate PEM format (root.crt) and the Class 3 PKI key in PEM format (class3.crt). But the key is this - Installing CAcert certificates as 'user trusted'-certificates is very easy. Installing new certificates as 'system trusted'-certificates requires more work (and requires root access)
Starting from Android 4.0 (Android ICS/'Ice Cream Sandwich', Android 4.3 'Jelly Bean' & Android 4.4 'KitKat'), system trusted certificates are on the (read-only) system partition in the folder '/system/etc/security/' as individual files. However, users can now easily add their own 'user' certificates which will be stored in '/data/misc/keychain/certs-added'.

System-installed certificates can be managed on the Android device in the Settings -> Security -> Certificates -> 'System'-section, whereas the user trusted certificates are manged in the 'User'-section there.
http://wiki.cacert.org/FAQ/ImportRootCert#Android_Phones_.26_Tablets

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Dave HoweSoftware and Hardware EngineerCommented:
Self signed are usually easier to accept on sight than get into a keystore; if you *want* to go down the CA route, you are probably better served to create a (self signed) CA using a keytool (or much easier, use XCA), Import that into keystores, then issue leaf certs signed by that CA (again, you can do that with XCA fairly trivially)
btanExec ConsultantCommented:
Better to have your own trust store, and you have control
The sample project contains a shell script that does this automatically. All you need is a recent Bouncy Castle jar file and the openssl command (usually available on Linux systems).  Drop the jar and a certificate (in PEM format) in the script's directory and run it.....If you are not the command-line type, you can use the Portecle GUI utility to create the key store file.
 
http://nelenkov.blogspot.in/2011/12/using-custom-certificate-trust-store-on.html
threadyAuthor Commented:
Thank you very much everyone, sorry for the late reply!  Very helpful answers!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SSL / HTTPS

From novice to tech pro — start learning today.