Certificate Authorities: curl-ca-bundle, certsync, keychain

[Ryan Schmidt]

On Dec 6, 2013, at 08:02, Landon Fuller wrote:

> On Nov 29, 2013, at 3:38 , Ryan Schmidt wrote:
> 
>> I’ve switched many of my MacPorts installs to certsync, including on Leopard, but I don’t know if it’s working correctly (how would I test that?).
> 
> As long as you're getting a populated cert file, you're set.

On my Leopard machine I have:

$ file /Volumes/Data/macports/leopard/etc/openssl/cert.pem
/Volumes/Data/macports/leopard/etc/openssl/cert.pem: PEM certificate
$ ls -l /Volumes/Data/macports/leopard/etc/openssl/cert.pem
-rw-r--r--  1 root  wheel  255951 Nov 29 01:34 /Volumes/Data/macports/leopard/etc/openssl/cert.pem


Whereas on my Mavericks machine I have:

$ file /opt/local/etc/openssl/cert.pem 
/opt/local/etc/openssl/cert.pem: ASCII text
$ ls -l /opt/local/etc/openssl/cert.pem 
-rw-r--r--  1 root  wheel  313476 Dec  6 08:27 /opt/local/etc/openssl/cert.pem


Seems to make sense that the Mavericks machine would have more certificates.


>> Unfortunately certsync fails to build on Tiger; I would love to get that fixed.
> 
> What are the errors you're hitting? I don't have a Tiger install to work with locally, but in theory I could try to bring it up in VMware.

I’ll find out and file a ticket for you.