Hello Goetz Babin-Ebell.

>> 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

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Received on 2002-12-05