RE: (no subject)

From: Kjetil Jacobsen <>
Date: Thu, 26 May 2005 15:43:54 +0200

pycurl.SSLCERT takes a string as argument.

[] On Behalf Of Peter Schott
Sent: 26 May 2005 01:10
Subject: (no subject)

OK - trying that now, but when I set SSLCERT = the same PEM file, I get:
debug - unable to set private key file: 'D:/MyCert.pem' type PEM
regular output - ''' pycurl.error : (58, "unable to set private key file:
D:/MyCert.pem' type PEM\n") '''
Am I doing something wrong by trying to pass in (pycurl.SSLCERT, MyCert) for
values? Is this supposed to be a list or dictionary instead of a string?

> OK - I can kind of see that, but why don't I get prompted for this when I
> use curl.exe? I don't pass this in for my command line and it works.

Aaaah. Now I finally start to understand... Sorry for being slow.

I went back and compared your python with the command line, and spotted that

you use -E but you don't pass in your certificate (using SSLCERT) in the
python program. You only pass in the SSLKEY, and both are likely to be

curl -E assumes that your privaate key and client cert are both kept in the
same PEM file.

Peter A. Schott
drive financial services
Database Administrator
p: 214.237.3567
c: 214.734.1792
f: 214.237.3495
email: <>


This e-mail is covered by the Electronic Communications Privacy Act, 18

Sections 2510-2521. The information contained in this e-mail is confidential

and intended only for use of the individual or entity named above. If the

of this message is not the intended recipient, or the employee or agent

responsible to deliver it to the intended recipient, you are hereby notified

that any dissemination, distribution or copying of this communication is

prohibited. If you have received this message in error or there are any

please notify the originator immediately.

The unauthorized use, disclosure, copying or alteration of this message is

strictly forbidden. This mail and any attachments have been scanned for

prior to leaving the Drive Financial Services network. Drive Financial

will not be liable for direct, special, indirect or consequential damages

from alteration of the contents of this message by a third party or as a
result of

any virus being passed on.


Received on 2005-05-26