Andrey S. Goncherov wrote:
> Hello Goetz Babin-Ebell.
Hello Andrey,

>>> We trying to connect to authorize.net via https:// but cURL give us
>>> error and we can't find any problem.

>>> We run it using this string:

>>> ./curl --key ./private.key --cacert ./ca_new.txt -v --cert
>>> ./www_site_com.crt https://secure.authorize.net/gateway/transact.dll

>>> But curl say:

>>>* About to connect() to secure.authorize.net:443
>>>* Connected to secure.authorize.net (206.253.210.201) port 443
>>>* unable to set private key file
>>>* Closing connection #0
>>>curl: (58) unable to set private key file
>>>
>>> But private.key is correct private key.
>
>
> GBE> Is in www_site_com.crt your certificate ?
> yes - it's 100% correct certificate from comodo.net or .org
> GBE> the key in --key must match the cert in --cert ...
> as private key we put private key generated by
>
> openssl req –new –nodes -keyout myserver.key –out server.csr

what gives
openssl x509 -text -noout -in www_site_com.crt

And try
openssl s_client -connect secure.authorize.net:443 \
  -key ./private.key -cert ./www_site_com.crt -debug

But why give you a client key/cert ?
the site requires no client authentication....

Bye

Goetz

-- 
Goetz Babin-Ebell, TC TrustCenter AG, http://www.trustcenter.de
Sonninstr. 24-28, 20097 Hamburg, Germany
Tel.: +49-(0)40 80 80 26 -0,  Fax: +49-(0)40 80 80 26 -126

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf