On Wed, Sep 17, 2008 at 05:21:11PM -0500, Ryan Graciano wrote:
> Thanks Dan. It does look like it changes. It used to be "curl:
> (35)", and now it's "curl: (58)".

That confirms where the problem lies.

> * SSLv3, TLS handshake, Client hello (1):
> * SSLv3, TLS handshake, Server hello (2):
> * SSLv3, TLS handshake, CERT (11):
> * SSLv3, TLS handshake, Request CERT (13):
> * SSLv3, TLS handshake, Server finished (14):
> * SSLv3, TLS handshake, CERT (11):
> * SSLv3, TLS handshake, Client key exchange (16):
> * SSLv3, TLS handshake, CERT verify (15):
> * SSLv3, TLS change cipher, Client hello (1):
> * SSLv3, TLS handshake, Finished (20):
> * SSLv3, TLS alert, Server hello (2):
> * error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca
> * Closing connection #0
> curl: (58) error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca

Could it be the remote server that can't verify the certificate? And it's
not a curl problem at all?

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved