Open M66B opened 12 years ago
I will see what's required to get it to build for 2.0 & up, as I have a device that's "stuck" on 2.0. No promises. It's probably an API call
From what I've done so far (total noob at actually building packages here), it seems like dropping the SDK version to 7 (2.1) from 8 (2.2) seems to have no ill effects on the build process. I'm still setting everything up so I need to build a signed version - but my PD Novel (stuck on some weird build of Eclair) rejected the APK for that reason instead of "I can't parse this".
That doesn't, however, mean the certificate store didn't change formats between those API revisions. Hopefully it did not.
On Sat, 2011-10-01 at 00:10 -0700, Ivo Ugrina wrote:
I've build it for my android 2.2 without any problems. You can find the build in my private f-droid repo http://www.iugrina.com/fdroidrepot
Ivo -
The issue is that we're trying to build it for 2.1 or earlier. My problems with building the code & installing a test APK are due to the fact that I've never built an APK before. :)
aside: I'm glad F-Droid hosts CACertMan - that's the primary market I use - if we can get it to build for older Android versions with no issues, then that means we can help more users take control of their certificate store.
--BK
--Brian Kemp brian.kemp@gmail.com PGP Key fingerprint: 1E5BF363
I can easily get it to build & run on 2.1; I'm having troubles not making the application NOT trash the certificate store. A trashed certificate store means all browsers that use it will crash trying to connect to an HTTPS site.
I suspect it's related to this specific ROM that I use on this device (and su binary) & will report back when I have better results. (The ROM always turns on both mass storage & usb debugging with a cable plugged in, which I think is causing the problems.)
My suspicions are correct. Just related to this ROM's Mass Storage mode. It works beautifully compiled against the 2.1 SDK. I will see if it'll compile against 1.6. Sorry to be so chatty. Short version - yes, we can easily do 2.1.
Hey there. Just committed that can run on Android 1.6 and above, but we haven't fully tested it yet.
There is a new build available here: https://github.com/guardianproject/cacert/CACertMan-0.0.2-alpha-20111011.apk/qr_code
Is it possible to make CaCertMan working for Android 2.1 and earlier versions?