Quote:
Originally Posted by schettj
Did you select the enterprise protocols OEM? I have no idea if it comes into play there or not, but its something to try - I use a self-signed cert for ssl via email/imap, and my ROM build (with that oem included) was able to handle it as usual by popping up the warning and proceeding when I hit OK.
|
I'll give this a shot, didn't even notice it when I was building the OS.
Quote:
Originally Posted by StarDestroyer
I run Exchange 2003 and use CAcert for my certificates. Unfortunately, CAcert's root certificates aren't included in mainstream browsers or in Windows mobile by default. So I found a way around it... I found instructions on an MS blog about how to create a .cab file for importing a certificate. I also managed to make an OEM for the CAcert root certificates. You can either sign up with CAcert and put one of the certificates on your exchange server or use the instructions to create a .cab or OEM of your self signed cert and try that... I am using the OEM method successfully on the latest kitchen. |
This is just another way of adding the cert into the phone right ? Because I have had success in past versions by just dumping the cert onto my SD card and then opening it in file explorer. I checked where it installed on the device and it was put into the trusted root certs.
I moved back down to the 3.5 AKU but I'll give it another shot today. Gives me an excuse not to answer emails at night!
11-20-2007, 01:06 PM
Threaded Mode
