CAcert Code Development list.

["Kenneth R. van Wyk" <ken AT krvw.com>]

Well guys, I have given up on CAcert's ability to ever fix this problem (re 
certs not working in iOS 5 (or 6, I should add)).

I've been a CAcert user and supporter for years. I've donated money. I've 
donated time (I'm a certificate assurer).

But your certs still don't work on iOS. I've reported the problem. I've 
tested proposed fixes. I've offered to help more.

But here we are, months later, and still nothing.

Today, I did the unspeakable -- I purchased a Verisign certificate. I hated 
myself for doing it, but this lack of any forward progress has been overruled 
by my own business needs.

I hope things change. I love the idea of CAcert and would gladly continue to 
donate time and money for a worthwhile project -- if it worked.

Sorry.

Cheers,

Ken van Wyk



On Jul 30, 2012, at 3:25 PM, Kenneth R. van Wyk 
<Ken AT krvw.com>
 wrote:

> 
> On Jul 28, 2012, at 4:22 AM, Wytze van der Raay 
> <wytze AT cacert.org>
>  wrote:
>> Do you still have the working certificate from the test system?
>> If so, could you please send us the output from these:
>> 
>> openssl x509 -in old-working-certificate -text -noout
>> openssl x509 -in new-nonworking-certificate -text -noout
>> 
>> Even if you don't have the old working certificate anymore, it will
>> still be useful to send us the output for the new-nonworking-cert.
> 
> Alas, that test cert was long ago discarded. But I do have the two I 
> generated after the patch was installed. One is signed with the class-3....
> 
> Neither of these work on my iPhone or iPad (running standard, off the shelf 
> iOS 5.1.1).
> 
> Attached is the above output for each of my certs. I hope it helps. If I 
> can do any further testing, just let me know.
> 
> Cheers,
> 
> Ken
> 
> <krvw1.txt>
> <krvw2.txt>

Attachment: smime.p7s
Description: S/MIME cryptographic signature