Installing on OSX 10.5

[HenryL]

I followed the command on the homepage and ran into an error building
pycurl. Interestingly, got this output:

Using curl-config (libcurl 7.16.3)
src/pycurl.c:54:4: error: #error "Need libcurl version 7.16.2 or
greater to compile pycurl."
src/pycurl.c:54:4: error: #error "Need libcurl version 7.16.2 or
greater to compile pycurl."
...
lipo: can't figure out the architecture type of: /var/tmp//
cczzv77u.out
error: Setup script exited with error: command 'gcc' failed with exit
status 1

Anyone else having trouble with pycurl on osx 10.5? I'm thinking about
upgrading libcurl to a higher version to try out other versions of
pycurl.

[HenryL]

I upgraded to libcurl 7.19.6 and installed pycurl 7.19.0 and now it
seems to work.

[Casey]

What version of pycurl is currently installed? You can find out with
"curl --version".

Try changing the command so that pycurl==version is your version
number.

Casey

On Sep 10, 2:19 pm, HenryL <hanyang...@gmail.com> wrote:

[HenryL]

The version that comes with OS X 10.5 is libcurl 7.16.2. The
corresponding pycurl version is 7.16.2.1 but that failed for me. I
upgraded libcurl/pycurl as mentioned before and the "hello, world"
demo works now. The chat demo returns a 500 error, though. I get a
"Invalid OpenID response: 60: HTTP 599". Hopefully that isn't a result
of using an incompatible version of pycurl.

[Casey]

Sorry for the trouble Henry, can you post the entire logging and stack
trace output starting with the first redirect?

Thanks,
Casey

[HenryL]

[I 090910 15:00:21 httpclient:404] GET
https://www.google.com/accounts/o8/ud?openid.op_endpoint=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fud&openid.sig=7pu9mkMLRM0G1M2tNhNOs6t3mqg%3D&openid.ext1.value.firstname=Henry&openid.response_nonce=2009-09-10T21%3A57%3A41ZLDCn-60BEfPDPA&openid.ns.ext1=http%3A%2F%2Fopenid.net%2Fsrv%2Fax%2F1.0&openid.ext1.type.lastname=http%3A%2F%2Faxschema.org%2FnamePerson%2Flast&openid.return_to=http%3A%2F%2Flocalhost%3A8888%2Fauth%2Flogin&openid.claimed_id=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawmZYG7Wxci6npU3CeYic_TS1CdCVi-F2o0&openid.ext1.mode=fetch_response&openid.signed=op_endpoint%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle%2Cns.ext1%2Cext1.mode%2Cext1.type.firstname%2Cext1.value.firstname%2Cext1.type.lastname%2Cext1.value.lastname&openid.ext1.value.lastname=Liu&openid.assoc_handle=AOQobUf3dTQEHzut8q2FZGrZONN_xmMma-40VKxJHTpEMjtRSQS8THRj&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.mode=check_authentication&openid.identity=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawmZYG7Wxci6npU3CeYic_TS1CdCVi-F2o0&openid.ext1.type.firstname=http%3A%2F%2Faxschema.org%2FnamePerson%2Ffirst
/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-
packages/tornado/httpclient.py:333: DeprecationWarning:
BaseException.message has been deprecated as of Python 2.6
return "%d: %s" % (self.errno, self.message)
[W 090910 15:00:21 auth:149] Invalid OpenID response: 60: HTTP 599
[W 090910 15:00:21 web:725] 500 GET /auth/login?openid.ns=http%3A%2F
%2Fspecs.openid.net%2Fauth
%2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F
%2Fwww.google.com%2Faccounts
%2Fo8%2Fud&openid.response_nonce=2009-09-10T21%3A57%3A41ZLDCn-60BEfPDPA&openid.return_to=http
%3A%2F%2Flocalhost%3A8888%2Fauth
%2Flogin&openid.assoc_handle=AOQobUf3dTQEHzut8q2FZGrZONN_xmMma-40VKxJHTpEMjtRSQS8THRj&openid.signed=op_endpoint
%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle
%2Cns.ext1%2Cext1.mode%2Cext1.type.firstname%2Cext1.value.firstname
%2Cext1.type.lastname
%2Cext1.value.lastname&openid.sig=7pu9mkMLRM0G1M2tNhNOs6t3mqg
%3D&openid.identity=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid
%3Fid%3DAItOawmZYG7Wxci6npU3CeYic_TS1CdCVi-F2o0&openid.claimed_id=https
%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid
%3DAItOawmZYG7Wxci6npU3CeYic_TS1CdCVi-F2o0&openid.ns.ext1=http%3A%2F
%2Fopenid.net%2Fsrv%2Fax
%2F1.0&openid.ext1.mode=fetch_response&openid.ext1.type.firstname=http
%3A%2F%2Faxschema.org%2FnamePerson
%2Ffirst&openid.ext1.value.firstname=Henry&openid.ext1.type.lastname=http
%3A%2F%2Faxschema.org%2FnamePerson
%2Flast&openid.ext1.value.lastname=Liu (127.0.0.1): Google auth failed
[E 090910 15:00:21 web:714] 500 GET /auth/login?openid.ns=http%3A%2F
%2Fspecs.openid.net%2Fauth
%2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F
%2Fwww.google.com%2Faccounts
%2Fo8%2Fud&openid.response_nonce=2009-09-10T21%3A57%3A41ZLDCn-60BEfPDPA&openid.return_to=http
%3A%2F%2Flocalhost%3A8888%2Fauth
%2Flogin&openid.assoc_handle=AOQobUf3dTQEHzut8q2FZGrZONN_xmMma-40VKxJHTpEMjtRSQS8THRj&openid.signed=op_endpoint
%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle
%2Cns.ext1%2Cext1.mode%2Cext1.type.firstname%2Cext1.value.firstname
%2Cext1.type.lastname
%2Cext1.value.lastname&openid.sig=7pu9mkMLRM0G1M2tNhNOs6t3mqg
%3D&openid.identity=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid
%3Fid%3DAItOawmZYG7Wxci6npU3CeYic_TS1CdCVi-F2o0&openid.claimed_id=https
%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid
%3DAItOawmZYG7Wxci6npU3CeYic_TS1CdCVi-F2o0&openid.ns.ext1=http%3A%2F
%2Fopenid.net%2Fsrv%2Fax
%2F1.0&openid.ext1.mode=fetch_response&openid.ext1.type.firstname=http
%3A%2F%2Faxschema.org%2FnamePerson
%2Ffirst&openid.ext1.value.firstname=Henry&openid.ext1.type.lastname=http
%3A%2F%2Faxschema.org%2FnamePerson
%2Flast&openid.ext1.value.lastname=Liu (127.0.0.1) 47.62ms

[Benjamin]

I'm seeing the same problem. OSX 10.5. I didn't see the previous
issues, however; Tornado installed fine following the instructions.

My terminal output:
[I 090912 19:10:04 httpclient:404] GET
https://www.google.com/accounts/o8/ud?openid.op_endpoint=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fud&openid.sig=00npCJSNRZ7W%2BJAIrnrxSNwN%2BU0%3D&openid.ext1.value.firstname=Benjamin&openid.response_nonce=2009-09-12T11%3A10%3A04ZKjKcqSu3-Vmw2w&openid.ns.ext1=http%3A%2F%2Fopenid.net%2Fsrv%2Fax%2F1.0&openid.ext1.type.lastname=http%3A%2F%2Faxschema.org%2FnamePerson%2Flast&openid.return_to=http%3A%2F%2Flocalhost%3A8888%2Fauth%2Flogin&openid.claimed_id=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawkiT967dDZ57Li2cZmCmKS32abpDMylIps&openid.ext1.mode=fetch_response&openid.signed=op_endpoint%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle%2Cns.ext1%2Cext1.mode%2Cext1.type.firstname%2Cext1.value.firstname%2Cext1.type.lastname%2Cext1.value.lastname&openid.ext1.value.lastname=Anderson&openid.assoc_handle=AOQobUdbpAi4Kysdtxo88d-kqHWWx49MJQg_vhUVs9fn949n82oP45nP&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.mode=check_authentication&openid.identity=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawkiT967dDZ57Li2cZmCmKS32abpDMylIps&openid.ext1.type.firstname=http%3A%2F%2Faxschema.org%2FnamePerson%2Ffirst
[W 090912 19:10:04 auth:149] Invalid OpenID response: 1: HTTP 599
[W 090912 19:10:04 web:725] 500 GET /auth/login?openid.ns=http%3A%2F
%2Fspecs.openid.net%2Fauth
%2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F
%2Fwww.google.com%2Faccounts
%2Fo8%2Fud&openid.response_nonce=2009-09-12T11%3A10%3A04ZKjKcqSu3-
Vmw2w&openid.return_to=http%3A%2F%2Flocalhost%3A8888%2Fauth
%2Flogin&openid.assoc_handle=AOQobUdbpAi4Kysdtxo88d-
kqHWWx49MJQg_vhUVs9fn949n82oP45nP&openid.signed=op_endpoint
%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle
%2Cns.ext1%2Cext1.mode%2Cext1.type.firstname%2Cext1.value.firstname
%2Cext1.type.lastname%2Cext1.value.lastname&openid.sig=00npCJSNRZ7W
%2BJAIrnrxSNwN%2BU0%3D&openid.identity=https%3A%2F%2Fwww.google.com
%2Faccounts%2Fo8%2Fid%3Fid
%3DAItOawkiT967dDZ57Li2cZmCmKS32abpDMylIps&openid.claimed_id=https%3A
%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid
%3DAItOawkiT967dDZ57Li2cZmCmKS32abpDMylIps&openid.ns.ext1=http%3A%2F
%2Fopenid.net%2Fsrv%2Fax
%2F1.0&openid.ext1.mode=fetch_response&openid.ext1.type.firstname=http
%3A%2F%2Faxschema.org%2FnamePerson
%2Ffirst&openid.ext1.value.firstname=Benjamin&openid.ext1.type.lastname=http
%3A%2F%2Faxschema.org%2FnamePerson
%2Flast&openid.ext1.value.lastname=Anderson (127.0.0.1): Google auth
failed
[E 090912 19:10:04 web:714] 500 GET /auth/login?openid.ns=http%3A%2F
%2Fspecs.openid.net%2Fauth
%2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F
%2Fwww.google.com%2Faccounts
%2Fo8%2Fud&openid.response_nonce=2009-09-12T11%3A10%3A04ZKjKcqSu3-
Vmw2w&openid.return_to=http%3A%2F%2Flocalhost%3A8888%2Fauth
%2Flogin&openid.assoc_handle=AOQobUdbpAi4Kysdtxo88d-
kqHWWx49MJQg_vhUVs9fn949n82oP45nP&openid.signed=op_endpoint
%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle
%2Cns.ext1%2Cext1.mode%2Cext1.type.firstname%2Cext1.value.firstname
%2Cext1.type.lastname%2Cext1.value.lastname&openid.sig=00npCJSNRZ7W
%2BJAIrnrxSNwN%2BU0%3D&openid.identity=https%3A%2F%2Fwww.google.com
%2Faccounts%2Fo8%2Fid%3Fid
%3DAItOawkiT967dDZ57Li2cZmCmKS32abpDMylIps&openid.claimed_id=https%3A
%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid
%3DAItOawkiT967dDZ57Li2cZmCmKS32abpDMylIps&openid.ns.ext1=http%3A%2F
%2Fopenid.net%2Fsrv%2Fax
%2F1.0&openid.ext1.mode=fetch_response&openid.ext1.type.firstname=http
%3A%2F%2Faxschema.org%2FnamePerson
%2Ffirst&openid.ext1.value.firstname=Benjamin&openid.ext1.type.lastname=http
%3A%2F%2Faxschema.org%2FnamePerson
%2Flast&openid.ext1.value.lastname=Anderson (127.0.0.1) 4.93ms


On Sep 11, 6:00 am, HenryL <hanyang...@gmail.com> wrote:
> [I 090910 15:00:21 httpclient:404] GEThttps://www.google.com/accounts/o8/ud?openid.op_endpoint=https%3A%2F%...

[Eiso Kant]

I am seeing the same problem on Ubuntu Hardy.

GET Output:

[I 090915 12:48:20 web:714] 302 GET / (127.0.0.1) 0.00ms
[I 090915 12:48:20 web:714] 302 GET /auth/login?next=%2F (127.0.0.1)
0.00ms
[I 090915 12:48:21 httpclient:404] GET
https://www.google.com/accounts/o8/ud?openid.op_endpoint=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fud&openid.sig=yehZ0HSWYVfLU%2Fu6DUTRD4ZXMzU%3D&openid.ext1.value.firstname=Eiso&openid.response_nonce=2009-09-15T12%3A48%3A20ZJwYJ0GHzU2L3Wg&openid.ns.ext1=http%3A%2F%2Fopenid.net%2Fsrv%2Fax%2F1.0&openid.ext1.type.lastname=http%3A%2F%2Faxschema.org%2FnamePerson%2Flast&openid.return_to=http%3A%2F%2F173.45.228.123%2Fauth%2Flogin&openid.claimed_id=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawmvzdhARGsy0Bu7Tu4jWXLp0D6vPTkPVG4&openid.ext1.mode=fetch_response&openid.signed=op_endpoint%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle%2Cns.ext1%2Cext1.mode%2Cext1.type.firstname%2Cext1.value.firstname%2Cext1.type.lastname%2Cext1.value.lastname&openid.ext1.value.lastname=Kant&openid.assoc_handle=AOQobUdeEGr-HXBKkVlvUt8CjACNzM-pYGchZ6M28p_5EyepdTOw8HF4&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.mode=check_authentication&openid.identity=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawmvzdhARGsy0Bu7Tu4jWXLp0D6vPTkPVG4&openid.ext1.type.firstname=http%3A%2F%2Faxschema.org%2FnamePerson%2Ffirst
[W 090915 12:48:21 auth:149] Invalid OpenID response: 77: HTTP 599
[W 090915 12:48:21 web:725] 500 GET /auth/login?openid.ns=http%3A%2F
%2Fspecs.openid.net%2Fauth
%2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F
%2Fwww.google.com%2Faccounts
%2Fo8%2Fud&openid.response_nonce=2009-09-15T12%3A48%3A20ZJwYJ0GHzU2L3Wg&openid.return_to=http
%3A%2F%2F173.45.228.123%2Fauth%2Flogin&openid.assoc_handle=AOQobUdeEGr-
HXBKkVlvUt8CjACNzM-pYGchZ6M28p_5EyepdTOw8HF4&openid.signed=op_endpoint
%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle
%2Cns.ext1%2Cext1.mode%2Cext1.type.firstname%2Cext1.value.firstname
%2Cext1.type.lastname%2Cext1.value.lastname&openid.sig=yehZ0HSWYVfLU
%2Fu6DUTRD4ZXMzU%3D&openid.identity=https%3A%2F%2Fwww.google.com
%2Faccounts%2Fo8%2Fid%3Fid
%3DAItOawmvzdhARGsy0Bu7Tu4jWXLp0D6vPTkPVG4&openid.claimed_id=https%3A
%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid
%3DAItOawmvzdhARGsy0Bu7Tu4jWXLp0D6vPTkPVG4&openid.ns.ext1=http%3A%2F
%2Fopenid.net%2Fsrv%2Fax
%2F1.0&openid.ext1.mode=fetch_response&openid.ext1.type.firstname=http
%3A%2F%2Faxschema.org%2FnamePerson
%2Ffirst&openid.ext1.value.firstname=Eiso&openid.ext1.type.lastname=http
%3A%2F%2Faxschema.org%2FnamePerson
%2Flast&openid.ext1.value.lastname=Kant (127.0.0.1): Google auth
failed
[E 090915 12:48:21 web:714] 500 GET /auth/login?openid.ns=http%3A%2F
%2Fspecs.openid.net%2Fauth
%2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F
%2Fwww.google.com%2Faccounts
%2Fo8%2Fud&openid.response_nonce=2009-09-15T12%3A48%3A20ZJwYJ0GHzU2L3Wg&openid.return_to=http
%3A%2F%2F173.45.228.123%2Fauth%2Flogin&openid.assoc_handle=AOQobUdeEGr-
HXBKkVlvUt8CjACNzM-pYGchZ6M28p_5EyepdTOw8HF4&openid.signed=op_endpoint
%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle
%2Cns.ext1%2Cext1.mode%2Cext1.type.firstname%2Cext1.value.firstname
%2Cext1.type.lastname%2Cext1.value.lastname&openid.sig=yehZ0HSWYVfLU
%2Fu6DUTRD4ZXMzU%3D&openid.identity=https%3A%2F%2Fwww.google.com
%2Faccounts%2Fo8%2Fid%3Fid
%3DAItOawmvzdhARGsy0Bu7Tu4jWXLp0D6vPTkPVG4&openid.claimed_id=https%3A
%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid
%3DAItOawmvzdhARGsy0Bu7Tu4jWXLp0D6vPTkPVG4&openid.ns.ext1=http%3A%2F
%2Fopenid.net%2Fsrv%2Fax
%2F1.0&openid.ext1.mode=fetch_response&openid.ext1.type.firstname=http
%3A%2F%2Faxschema.org%2FnamePerson
%2Ffirst&openid.ext1.value.firstname=Eiso&openid.ext1.type.lastname=http
%3A%2F%2Faxschema.org%2FnamePerson
%2Flast&openid.ext1.value.lastname=Kant (127.0.0.1) 20.00ms
[I 090915 12:48:35 web:714] 302 GET /auth/logout (127.0.0.1) 4.00ms
[I 090915 12:48:36 web:714] 302 GET / (127.0.0.1) 0.00ms
[I 090915 12:48:36 web:714] 302 GET /auth/login?next=%2F (127.0.0.1)
0.00ms
[I 090915 12:48:37 httpclient:404] GET
https://www.google.com/accounts/o8/ud?openid.op_endpoint=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fud&openid.sig=Rq%2BSCGrHpctXZBOTzHL6INqPQTM%3D&openid.ext1.value.firstname=Eiso&openid.response_nonce=2009-09-15T12%3A48%3A37ZQXR910hB1hM9ng&openid.ns.ext1=http%3A%2F%2Fopenid.net%2Fsrv%2Fax%2F1.0&openid.ext1.type.lastname=http%3A%2F%2Faxschema.org%2FnamePerson%2Flast&openid.return_to=http%3A%2F%2F173.45.228.123%2Fauth%2Flogin&openid.claimed_id=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawmvzdhARGsy0Bu7Tu4jWXLp0D6vPTkPVG4&openid.ext1.mode=fetch_response&openid.signed=op_endpoint%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle%2Cns.ext1%2Cext1.mode%2Cext1.type.firstname%2Cext1.value.firstname%2Cext1.type.lastname%2Cext1.value.lastname&openid.ext1.value.lastname=Kant&openid.assoc_handle=AOQobUcOBagR040jQr2bkBkbHjb6mTKuVZx0OxeHC3bNhlNJ-jRHYmhI&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.mode=check_authentication&openid.identity=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawmvzdhARGsy0Bu7Tu4jWXLp0D6vPTkPVG4&openid.ext1.type.firstname=http%3A%2F%2Faxschema.org%2FnamePerson%2Ffirst
[W 090915 12:48:37 auth:149] Invalid OpenID response: 77: HTTP 599
[W 090915 12:48:37 web:725] 500 GET /auth/login?openid.ns=http%3A%2F
%2Fspecs.openid.net%2Fauth
%2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F
%2Fwww.google.com%2Faccounts
%2Fo8%2Fud&openid.response_nonce=2009-09-15T12%3A48%3A37ZQXR910hB1hM9ng&openid.return_to=http
%3A%2F%2F173.45.228.123%2Fauth
%2Flogin&openid.assoc_handle=AOQobUcOBagR040jQr2bkBkbHjb6mTKuVZx0OxeHC3bNhlNJ-
jRHYmhI&openid.signed=op_endpoint%2Cclaimed_id%2Cidentity%2Creturn_to
%2Cresponse_nonce%2Cassoc_handle%2Cns.ext1%2Cext1.mode
%2Cext1.type.firstname%2Cext1.value.firstname%2Cext1.type.lastname
%2Cext1.value.lastname&openid.sig=Rq%2BSCGrHpctXZBOTzHL6INqPQTM
%3D&openid.identity=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid
%3Fid%3DAItOawmvzdhARGsy0Bu7Tu4jWXLp0D6vPTkPVG4&openid.claimed_id=https
%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid
%3DAItOawmvzdhARGsy0Bu7Tu4jWXLp0D6vPTkPVG4&openid.ns.ext1=http%3A%2F
%2Fopenid.net%2Fsrv%2Fax
%2F1.0&openid.ext1.mode=fetch_response&openid.ext1.type.firstname=http
%3A%2F%2Faxschema.org%2FnamePerson
%2Ffirst&openid.ext1.value.firstname=Eiso&openid.ext1.type.lastname=http
%3A%2F%2Faxschema.org%2FnamePerson
%2Flast&openid.ext1.value.lastname=Kant (127.0.0.1): Google auth
failed
[E 090915 12:48:37 web:714] 500 GET /auth/login?openid.ns=http%3A%2F
%2Fspecs.openid.net%2Fauth
%2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F
%2Fwww.google.com%2Faccounts
%2Fo8%2Fud&openid.response_nonce=2009-09-15T12%3A48%3A37ZQXR910hB1hM9ng&openid.return_to=http
%3A%2F%2F173.45.228.123%2Fauth
%2Flogin&openid.assoc_handle=AOQobUcOBagR040jQr2bkBkbHjb6mTKuVZx0OxeHC3bNhlNJ-
jRHYmhI&openid.signed=op_endpoint%2Cclaimed_id%2Cidentity%2Creturn_to
%2Cresponse_nonce%2Cassoc_handle%2Cns.ext1%2Cext1.mode
%2Cext1.type.firstname%2Cext1.value.firstname%2Cext1.type.lastname
%2Cext1.value.lastname&openid.sig=Rq%2BSCGrHpctXZBOTzHL6INqPQTM
%3D&openid.identity=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid
%3Fid%3DAItOawmvzdhARGsy0Bu7Tu4jWXLp0D6vPTkPVG4&openid.claimed_id=https
%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid
%3DAItOawmvzdhARGsy0Bu7Tu4jWXLp0D6vPTkPVG4&openid.ns.ext1=http%3A%2F
%2Fopenid.net%2Fsrv%2Fax
%2F1.0&openid.ext1.mode=fetch_response&openid.ext1.type.firstname=http
%3A%2F%2Faxschema.org%2FnamePerson
%2Ffirst&openid.ext1.value.firstname=Eiso&openid.ext1.type.lastname=http
%3A%2F%2Faxschema.org%2FnamePerson
%2Flast&openid.ext1.value.lastname=Kant (127.0.0.1) 24.00ms


Curl version:

~/tornado-0.1/demos/chat: curl --version
curl 7.18.0 (x86_64-pc-linux-gnu) libcurl/7.18.0 OpenSSL/0.9.8g zlib/
1.2.3.3 libidn/1.1
Protocols: tftp ftp telnet dict ldap ldaps http file https ftps
Features: GSS-Negotiate IDN IPv6 Largefile NTLM SSL libz

On Sep 12, 1:12 pm, Benjamin <brande...@gmail.com> wrote:
> I'm seeing the same problem. OSX 10.5. I didn't see the previous
> issues, however; Tornado installed fine following the instructions.
>
> My terminal output:

> [I 090912 19:10:04 httpclient:404] GEThttps://www.google.com/accounts/o8/ud?openid.op_endpoint=https%3A%2F%...

> [W 090912 19:10:04 auth:149] Invalid OpenID response: 1: HTTP 599

> [W 090912 19:10:04 web:725]500GET /auth/login?openid.ns=http%3A%2F

> %2Fspecs.openid.net%2Fauth
> %2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F
> %2Fwww.google.com%2Faccounts
> %2Fo8%2Fud&openid.response_nonce=2009-09-12T11%3A10%3A04ZKjKcqSu3-
> Vmw2w&openid.return_to=http%3A%2F%2Flocalhost%3A8888%2Fauth
> %2Flogin&openid.assoc_handle=AOQobUdbpAi4Kysdtxo88d-
> kqHWWx49MJQg_vhUVs9fn949n82oP45nP&openid.signed=op_endpoint
> %2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle
> %2Cns.ext1%2Cext1.mode%2Cext1.type.firstname%2Cext1.value.firstname
> %2Cext1.type.lastname%2Cext1.value.lastname&openid.sig=00npCJSNRZ7W
> %2BJAIrnrxSNwN%2BU0%3D&openid.identity=https%3A%2F%2Fwww.google.com
> %2Faccounts%2Fo8%2Fid%3Fid
> %3DAItOawkiT967dDZ57Li2cZmCmKS32abpDMylIps&openid.claimed_id=https%3A
> %2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid
> %3DAItOawkiT967dDZ57Li2cZmCmKS32abpDMylIps&openid.ns.ext1=http%3A%2F
> %2Fopenid.net%2Fsrv%2Fax
> %2F1.0&openid.ext1.mode=fetch_response&openid.ext1.type.firstname=http
> %3A%2F%2Faxschema.org%2FnamePerson
> %2Ffirst&openid.ext1.value.firstname=Benjamin&openid.ext1.type.lastname=htt p
> %3A%2F%2Faxschema.org%2FnamePerson
> %2Flast&openid.ext1.value.lastname=Anderson (127.0.0.1): Google auth
> failed

> [E 090912 19:10:04 web:714]500GET /auth/login?openid.ns=http%3A%2F

> %2Fspecs.openid.net%2Fauth
> %2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F
> %2Fwww.google.com%2Faccounts
> %2Fo8%2Fud&openid.response_nonce=2009-09-12T11%3A10%3A04ZKjKcqSu3-
> Vmw2w&openid.return_to=http%3A%2F%2Flocalhost%3A8888%2Fauth
> %2Flogin&openid.assoc_handle=AOQobUdbpAi4Kysdtxo88d-
> kqHWWx49MJQg_vhUVs9fn949n82oP45nP&openid.signed=op_endpoint
> %2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle
> %2Cns.ext1%2Cext1.mode%2Cext1.type.firstname%2Cext1.value.firstname
> %2Cext1.type.lastname%2Cext1.value.lastname&openid.sig=00npCJSNRZ7W
> %2BJAIrnrxSNwN%2BU0%3D&openid.identity=https%3A%2F%2Fwww.google.com
> %2Faccounts%2Fo8%2Fid%3Fid
> %3DAItOawkiT967dDZ57Li2cZmCmKS32abpDMylIps&openid.claimed_id=https%3A
> %2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid
> %3DAItOawkiT967dDZ57Li2cZmCmKS32abpDMylIps&openid.ns.ext1=http%3A%2F
> %2Fopenid.net%2Fsrv%2Fax
> %2F1.0&openid.ext1.mode=fetch_response&openid.ext1.type.firstname=http
> %3A%2F%2Faxschema.org%2FnamePerson
> %2Ffirst&openid.ext1.value.firstname=Benjamin&openid.ext1.type.lastname=htt p

> %3A%2F%2Faxschema.org%2FnamePerson
> %2Flast&openid.ext1.value.lastname=Anderson (127.0.0.1) 4.93ms
>
> On Sep 11, 6:00 am, HenryL <hanyang...@gmail.com> wrote:
>
>
>
> > [I 090910 15:00:21 httpclient:404] GEThttps://www.google.com/accounts/o8/ud?openid.op_endpoint=https%3A%2F%...
> > packages/tornado/httpclient.py:333: DeprecationWarning:
> > BaseException.message has been deprecated as of Python 2.6
> >   return "%d: %s" % (self.errno, self.message)
> > [W 090910 15:00:21 auth:149] Invalid OpenID response: 60: HTTP 599

> > [W 090910 15:00:21 web:725]500GET /auth/login?openid.ns=http%3A%2F

> > %2Fspecs.openid.net%2Fauth
> > %2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F
> > %2Fwww.google.com%2Faccounts
> > %2Fo8%2Fud&openid.response_nonce=2009-09-10T21%3A57%3A41ZLDCn-60BEfPDPA&ope nid.return_to=http
> > %3A%2F%2Flocalhost%3A8888%2Fauth
> > %2Flogin&openid.assoc_handle=AOQobUf3dTQEHzut8q2FZGrZONN_xmMma-40VKxJHTpEMj tRSQS8THRj&openid.signed=op_endpoint
> > %2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle
> > %2Cns.ext1%2Cext1.mode%2Cext1.type.firstname%2Cext1.value.firstname
> > %2Cext1.type.lastname
> > %2Cext1.value.lastname&openid.sig=7pu9mkMLRM0G1M2tNhNOs6t3mqg
> > %3D&openid.identity=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid
> > %3Fid%3DAItOawmZYG7Wxci6npU3CeYic_TS1CdCVi-F2o0&openid.claimed_id=https
> > %3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid
> > %3DAItOawmZYG7Wxci6npU3CeYic_TS1CdCVi-F2o0&openid.ns.ext1=http%3A%2F
> > %2Fopenid.net%2Fsrv%2Fax
> > %2F1.0&openid.ext1.mode=fetch_response&openid.ext1.type.firstname=http
> > %3A%2F%2Faxschema.org%2FnamePerson
> > %2Ffirst&openid.ext1.value.firstname=Henry&openid.ext1.type.lastname=http
> > %3A%2F%2Faxschema.org%2FnamePerson
> > %2Flast&openid.ext1.value.lastname=Liu (127.0.0.1): Google auth failed

> > [E 090910 15:00:21 web:714]500GET /auth/login?openid.ns=http%3A%2F

> > > > demo works now. The chat demo returns a500error, though. I get a

[Teemu Kurppa]

This seems to be common problem, I've tried to investigate it a bit as
it's failing for me too.

I'm having same problem both on
- Mac OS X 10.5: python 2.6, curl (7.19.6), pycurl (7.19.0) and
simplejson installed via Mac Ports.
- Ubuntu Hardy 8.04: python 2.5, curl 7.18.0-1ubuntu2.2, pycurl
7.16.4-1, simplejson

I've three theories why it's failing

a) either it's really sensitive to curl versions, which seems unlikely
to me, given that it gets responses
b) My Google account behaves differently for some reason than for
those people that have succeed to run Tornado demos requiring
authentication.
c) I have understood Google's Open ID incorrectly and haven't enabled
something on my account. I was thinking that it works out of the box.

Teemu

--
Teemu Kurppa
Co-Founder, Huikea Experience Ltd.
http://huikea.com
te...@huikea.com
+358 40 48 13012
http://dirtyaura.org/blog

[Casey Maloney Rosales Muller]

Good theories Teemu, sorry we haven't had time to look into this further.

You can test theory two by trying the chat demo we left up at
http://chan.friendfeed.com:8888/

We didn't modify the demo in any way, if that's what your third theory
is suggesting, so it would test that too.

Please let us know what you find, and hopefully we will be able to
reproduce it locally at some point.

Thanks,
Casey

[Teemu Kurppa]

Casey, thanks, that was useful.

I was able to use chat demo, so back to the square one - my
environment is borked somehow.

So my best option is to use the exact same version of pycurl and also
check that correct version of libcurl used, right?

Cheers,
Teemu

[Eiso Kant]

I decided to spend a little but more time trying to figure this out.

I went ahead and installed libcurl-7.19.6 and pycurl-7.19.0 on my
Ubuntu Hardy machine.

I have checked the versions and all is installed well however I still
get the same errors:

Just to speed things up for other people trying different versions,
I'll put paste my steps here:

mkdir ~/libcurl-7.19.6
cd ~/libcurl-7.19.6
wget http://curl.haxx.se/download/curl-7.19.6.tar.gz
tar xvfz curl-7.19.6.tar.gz
cd curl-7.19.6
./configure
make
sudo make install

sudo rm /usr/lib/libcurl*
sudo ln -s /usr/local/lib/libcurl.so.4 /usr/local/libcurl.so.4

mkdir ~/python-pycurl-7.19
cd ~/python-pycurl-7.19
wget http://pycurl.sourceforge.net/download/pycurl-7.19.0.tar.gz
tar xvfz pycurl-7.19.0.tar.gz
cd pycurl-7.19.0
sudo python setup.py install

cd ~/tornado-0.1/demos/chat
./chatdemo.py (which is the latest one taken from the github
repository)

This was the output:


[I 090916 13:37:01 httpclient:404] GET
https://www.google.com/accounts/o8/ud?openid.op_endpoint=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fud&openid.sig=taAqeHw5nIB2j1kse0PYRHzX4GI%3D&openid.response_nonce=2009-09-16T13%3A37%3A00Z7qtnE1wViy6kmw&openid.return_to=http%3A%2F%2F173.45.228.123%2Fauth%2Flogin&openid.claimed_id=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawnY45BT1E5Yt8C18kM_yGhKuScuSaD_3zo&openid.mode=check_authentication&openid.signed=op_endpoint%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle&openid.assoc_handle=AOQobUedZU9jHsXMRIQOZDN0mvM9SNYvDOilGgj8UVF2p93xhGRQqb_-&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.identity=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid%3DAItOawnY45BT1E5Yt8C18kM_yGhKuScuSaD_3zo
[W 090916 13:37:01 auth:149] Invalid OpenID response: 60: HTTP 599
[W 090916 13:37:01 web:725] 500 GET /auth/login?openid.ns=http%3A%2F
%2Fspecs.openid.net%2Fauth
%2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F
%2Fwww.google.com%2Faccounts
%2Fo8%2Fud&openid.response_nonce=2009-09-16T13%3A37%3A00Z7qtnE1wViy6kmw&openid.return_to=http
%3A%2F%2F173.45.228.123%2Fauth
%2Flogin&openid.assoc_handle=AOQobUedZU9jHsXMRIQOZDN0mvM9SNYvDOilGgj8UVF2p93xhGRQqb_-
&openid.signed=op_endpoint%2Cclaimed_id%2Cidentity%2Creturn_to
%2Cresponse_nonce%2Cassoc_handle&openid.sig=taAqeHw5nIB2j1kse0PYRHzX4GI
%3D&openid.identity=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid
%3Fid%3DAItOawnY45BT1E5Yt8C18kM_yGhKuScuSaD_3zo&openid.claimed_id=https
%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid
%3DAItOawnY45BT1E5Yt8C18kM_yGhKuScuSaD_3zo (127.0.0.1): Google auth
failed
[E 090916 13:37:01 web:714] 500 GET /auth/login?openid.ns=http%3A%2F
%2Fspecs.openid.net%2Fauth
%2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F
%2Fwww.google.com%2Faccounts
%2Fo8%2Fud&openid.response_nonce=2009-09-16T13%3A37%3A00Z7qtnE1wViy6kmw&openid.return_to=http
%3A%2F%2F173.45.228.123%2Fauth
%2Flogin&openid.assoc_handle=AOQobUedZU9jHsXMRIQOZDN0mvM9SNYvDOilGgj8UVF2p93xhGRQqb_-
&openid.signed=op_endpoint%2Cclaimed_id%2Cidentity%2Creturn_to
%2Cresponse_nonce%2Cassoc_handle&openid.sig=taAqeHw5nIB2j1kse0PYRHzX4GI
%3D&openid.identity=https%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid
%3Fid%3DAItOawnY45BT1E5Yt8C18kM_yGhKuScuSaD_3zo&openid.claimed_id=https
%3A%2F%2Fwww.google.com%2Faccounts%2Fo8%2Fid%3Fid
%3DAItOawnY45BT1E5Yt8C18kM_yGhKuScuSaD_3zo (127.0.0.1) 48.00ms

----

I'll continue to try things but right now I am out of ideas.

All the best,

Eiso

On Sep 15, 7:40 pm, Teemu Kurppa <teemu.kur...@gmail.com> wrote:
> Casey, thanks, that was useful.
>
> I was able to use chat demo, so back to the square one - my
> environment is borked somehow.
>
> So my best option is to use the exact same version of pycurl and also
> check that correct version of libcurl used, right?
>
> Cheers,
> Teemu
>
> On Tue, Sep 15, 2009 at 7:49 PM, Casey Maloney Rosales Muller
>
>
>
> <casey...@gmail.com> wrote:
>
> > Good theories Teemu, sorry we haven't had time to look into this further.
>
> > You can test theory two by trying the chat demo we left up at
> >http://chan.friendfeed.com:8888/
>
> > We didn't modify the demo in any way, if that's what your third theory
> > is suggesting, so it would test that too.
>
> > Please let us know what you find, and hopefully we will be able to
> > reproduce it locally at some point.
>
> > Thanks,
> > Casey
>

> > On Tue, Sep 15, 2009 at 6:49 AM, Teemu Kurppa <teemu.kur...@gmail.com> wrote:
>
> >> This seems to be common problem, I've tried to investigate it a bit as
> >> it's failing for me too.
>
> >> I'm having same problem both on
> >> - Mac OS X 10.5: python 2.6, curl (7.19.6), pycurl  (7.19.0) and
> >> simplejson installed via Mac Ports.
> >> - Ubuntu Hardy 8.04: python 2.5, curl 7.18.0-1ubuntu2.2, pycurl
> >> 7.16.4-1, simplejson
>
> >> I've three theories why it's failing
>
> >> a) either it's really sensitive to curl versions, which seems unlikely
> >> to me, given that it gets responses
> >> b) My Google account behaves differently for some reason than for
> >> those people that have succeed to run Tornado demos requiring
> >> authentication.
> >> c) I have understood Google's Open ID incorrectly and haven't enabled
> >> something on my account. I was thinking that it works out of the box.
>
> >> Teemu
>

> >> On Tue, Sep 15, 2009 at 3:49 PM, Eiso Kant <cont...@eiso-kant.com> wrote:
>
> >>> I am seeing the same problem on Ubuntu Hardy.
>
> >>> GET Output:
>
> >>> [I 090915 12:48:20 web:714] 302 GET / (127.0.0.1) 0.00ms
> >>> [I 090915 12:48:20 web:714] 302 GET /auth/login?next=%2F (127.0.0.1)
> >>> 0.00ms
> >>> [I 090915 12:48:21 httpclient:404] GET

> >>>https://www.google.com/accounts/o8/ud?openid.op_endpoint=https%3A%2F%...

> >>>https://www.google.com/accounts/o8/ud?openid.op_endpoint=https%3A%2F%...

> ...
>
> read more »

[Eiso Kant]

I've been going over everything and I think I found the source of the
problem.

Since Google's URI is https:// curl wants to verify certificates, if
you don't have any certificates locally setup with CURL it will fail
and hence throw the error (60).

There are several ways this can be fixed.

Adding the following line in tornado/httpclient.py (after line 351):

curl.setopt(pycurl.SSL_VERIFYPEER, 0)

or you can create local certificates and add the path to them (see:
http://curl.haxx.se/docs/sslcerts.html) there is some great example
code here: http://www.gnu-darwin.org/www001/ports-1.5a-CURRENT/net-p2p/py-bittorrent-core/work/BitTorrent-5.0.8/BTL/pycurllib.py
(look for CA_PATH and the set_use_cert_authority they define).

This is my first second day writing Python so I am just getting the
hang of it slowly but I am enjoying it.

All the best,

Eiso

On Sep 16, 3:43 pm, Eiso Kant <cont...@eiso-kant.com> wrote:
> I decided to spend a little but more time trying to figure this out.
>
> I went ahead and installed libcurl-7.19.6 and pycurl-7.19.0 on my
> Ubuntu Hardy machine.
>
> I have checked the versions and all is installed well however I still
> get the same errors:
>
> Just to speed things up for other people trying different versions,
> I'll put paste my steps here:
>
> mkdir ~/libcurl-7.19.6
> cd ~/libcurl-7.19.6

> wgethttp://curl.haxx.se/download/curl-7.19.6.tar.gz

> tar xvfz curl-7.19.6.tar.gz
> cd curl-7.19.6
> ./configure
> make
> sudo make install
>
> sudo rm /usr/lib/libcurl*
> sudo ln -s /usr/local/lib/libcurl.so.4 /usr/local/libcurl.so.4
>
> mkdir ~/python-pycurl-7.19
> cd ~/python-pycurl-7.19

> wgethttp://pycurl.sourceforge.net/download/pycurl-7.19.0.tar.gz

> tar xvfz pycurl-7.19.0.tar.gz
> cd pycurl-7.19.0
> sudo python setup.py install
>
> cd ~/tornado-0.1/demos/chat
> ./chatdemo.py (which is the latest one taken from the github
> repository)
>
> This was the output:
>

> [I 090916 13:37:01 httpclient:404] GEThttps://www.google.com/accounts/o8/ud?openid.op_endpoint=https%3A%2F%...

> ...
>
> read more »

[Henry Liu]

Thanks! Is this going to be patched in?

Sent from my iPhone

[Casey Maloney Rosales Muller]

Thanks for the detective work Eiso, this is interesting.

If you get a second, are you able to curl the https url from the
commandline? Or do you need to add the -k option there to also skip
the certificate check?

Since it works on some installations of OSX, maybe some other package
or program is quietly adding the appropriate certificate authorities.

To all the other people having these problems, does adding that
curl.setopt line fix your problem?

Thanks again,
Casey

[Eiso Kant]

Hi Casey,

Here are the bash commands. They are done from an Ubuntu Hardy machine. It seems to confirm the issue with curl. The line I suggested (curl.setopt(pycurl.SSL_VERIFYPEER, 0)) is equal to the -k option.

tyba ~: curl https://google.com

curl: (60) SSL certificate problem, verify that the CA cert is OK. Details:

error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"

 of Certificate Authority (CA) public keys (CA certs). If the default

 bundle file isn't adequate, you can specify an alternate file

 using the --cacert option.

If this HTTPS server uses a certificate signed by a CA represented in

 the bundle, the certificate verification probably failed due to a

 problem with the certificate (it might be expired, or the name might

 not match the domain name in the URL).

If you'd like to turn off curl's verification of the certificate, use

 the -k (or --insecure) option.

tyba ~: curl -k https://google.com

<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">

<TITLE>302 Moved</TITLE></HEAD><BODY>

<H1>302 Moved</H1>

The document has moved

<A HREF="http://www.google.com">here</A>.

</BODY></HTML>

I am new to Python but Tornado is perfect for a project I am working on so I hope I can contribute more while I build my app.

All the best,

Eiso

--
--
Eiso Kant - CEO & Founder of Twollars
Finca Sta Ana
Postbox 3041
29610 - Ojén
Malaga
Spain

Mobile: +34 648 80 2995
Email: con...@eiso-kant.com

Company Website: http://twollars.com
Personal Blog: http://eisokant.com
Twitter: http://twitter.com/eisokant

==================================================
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of,
or taking of any action in reliance upon this information by persons
or entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.

==================================================

[Teemu Kurppa]

Eiso, kudos for investigating this, I got my installation working.

Problem for me on Mac/MacPorts was that curl was not installed with
ssl and me being an ignorant mobile coder, I didn't check with curl
https://google.com first... Blah.

By the way, just doing
sudo port install curl+ssl
wasn't enough. Installation succeeded, but it didn't actually work. I
first had to clean the previous installation properly and then
reinstall.

Thus, steps:
sudo port uninstall py-curl
sudo port uninstall curl
sudo port clean curl
sudo port install curl+ssl
sudo port install py-curl

After that, blog demo works without disabling SSL_VERIFYPEER.

Cheers,
Teemu

--

[Casey Maloney Rosales Muller]

Just out of curiousity Eiso, does this fix it for you:
sudo apt-get install ca-certificates

Rather than disable SSL checks, we'd rather include instructions about
how to fix the underlying issue.

Also, it'd be good to hear from Henry, Benjamin, or Teemu about if
this is the problem they're experiencing under OS X.

Casey

[Teemu Kurppa]

Casey, excellent, I just tested installing ca-certificates on Ubuntu
Hardy 8.04 and it fixed the problem. And as I noted on previous email,
on Mac OS X/MacPorts, reinstalling curl+ssl fixed the problem.

Thanks for the help guys,
Teemu

On Wed, Sep 16, 2009 at 11:28 PM, Casey Maloney Rosales Muller

--

[Eiso Kant]

Hi Casey,

That's a great solution and much more elegant. 

One thing to keep in mind. On my Ubuntu machine I had installed the latest version of curl (7.19.6) and the latest version of pycurl (7.19.0). 

When I executed sudo apt-get install ca-certificates (after reverting the code to its original state) the old errors came back. 

I then reinstalled those latest versions of curl and pycurl and was expecting it to work, it didn't. 

I then removed those versions and installed the standard packages

sudo apt-get install curl php5-curl libcurl3-gnutls libcurl3 python-pycurl 

and then your solution did work.

The error with the latest versions might have just been on my end and that when removed some files were left behind causing the problem. 

Either way it's good to keep in mind if future errors come up.

All the best,

Eiso

[Casey]

Thanks for the info Eiso.

If anybody knows how to get curl to use the certificate store in OS X
without using MacPorts, please let us know.

Casey

On Sep 16, 2:35 pm, Eiso Kant <cont...@eiso-kant.com> wrote:
> Hi Casey,
> That's a great solution and much more elegant.
>
> One thing to keep in mind. On my Ubuntu machine I had installed the latest
> version of curl (7.19.6) and the latest version of pycurl (7.19.0).
>

> When I executed *sudo apt-get install ca-certificate*s (after reverting the

> code to its original state) the old errors came back.
> I then reinstalled those latest versions of curl and pycurl and was
> expecting it to work, it didn't.
>
> I then removed those versions and installed the standard packages
>

> *sudo apt-get install curl php5-curl libcurl3-gnutls libcurl3 python-pycurl
> *

>
> and then your solution did work.
>
> The error with the latest versions might have just been on my end and that
> when removed some files were left behind causing the problem.
> Either way it's good to keep in mind if future errors come up.
>
> All the best,
>
> Eiso
>
> On Wed, Sep 16, 2009 at 10:28 PM, Casey Maloney Rosales Muller <
>
>
>
> casey...@gmail.com> wrote:
>
> > Just out of curiousity Eiso, does this fix it for you:
> > sudo apt-get install ca-certificates
>
> > Rather than disable SSL checks, we'd rather include instructions about
> > how to fix the underlying issue.
>
> > Also, it'd be good to hear from Henry, Benjamin, or Teemu about if
> > this is the problem they're experiencing under OS X.
>
> > Casey
>

> > On Wed, Sep 16, 2009 at 12:27 PM, Eiso Kant <cont...@eiso-kant.com> wrote:
> > > Hi Casey,
> > > Here are the bash commands. They are done from an Ubuntu Hardy machine.
> > It
> > > seems to confirm the issue with curl. The line I suggested
> > > (curl.setopt(pycurl.SSL_VERIFYPEER, 0)) is equal to the -k option.

> > > tyba ~: curlhttps://google.com

> > > curl: (60) SSL certificate problem, verify that the CA cert is OK.
> > Details:
> > > error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate
> > verify
> > > failed
> > > More details here:http://curl.haxx.se/docs/sslcerts.html
> > > curl performs SSL certificate verification by default, using a "bundle"
> > >  of Certificate Authority (CA) public keys (CA certs). If the default
> > >  bundle file isn't adequate, you can specify an alternate file
> > >  using the --cacert option.
> > > If this HTTPS server uses a certificate signed by a CA represented in
> > >  the bundle, the certificate verification probably failed due to a
> > >  problem with the certificate (it might be expired, or the name might
> > >  not match the domain name in the URL).
> > > If you'd like to turn off curl's verification of the certificate, use
> > >  the -k (or --insecure) option.

> > > tyba ~: curl -khttps://google.com

> > > <HTML><HEAD><meta http-equiv="content-type"
> > > content="text/html;charset=utf-8">
> > > <TITLE>302 Moved</TITLE></HEAD><BODY>
> > > <H1>302 Moved</H1>
> > > The document has moved
> > > <A HREF="http://www.google.com">here</A>.
> > > </BODY></HTML>
> > > I am new to Python but Tornado is perfect for a project I am working on
> > so I
> > > hope I can contribute more while I build my app.
> > > All the best,
> > > Eiso
> > > On Wed, Sep 16, 2009 at 9:03 PM, Casey Maloney Rosales Muller
> > > <casey...@gmail.com> wrote:
>
> > >> Thanks for the detective work Eiso, this is interesting.
>
> > >> If you get a second, are you able to curl the https url from the
> > >> commandline? Or do you need to add the -k option there to also skip
> > >> the certificate check?
>
> > >> Since it works on some installations of OSX, maybe some other package
> > >> or program is quietly adding the appropriate certificate authorities.
>
> > >> To all the other people having these problems, does adding that
> > >> curl.setopt line fix your problem?
>
> > >> Thanks again,
> > >> Casey
>

> > >> On Wed, Sep 16, 2009 at 7:45 AM, Eiso Kant <cont...@eiso-kant.com>

> > wrote:
>
> > >> > I've been going over everything and I think I found the source of the
> > >> > problem.
>
> > >> > Since Google's URI is https:// curl wants to verify certificates, if
> > >> > you don't have any certificates locally setup with CURL it will fail
> > >> > and hence throw the error (60).
>
> > >> > There are several ways this can be fixed.
>
> > >> > Adding the following line in tornado/httpclient.py (after line 351):
>
> > >> > curl.setopt(pycurl.SSL_VERIFYPEER, 0)
>
> > >> > or you can create local certificates and add the path to them (see:
> > >> >http://curl.haxx.se/docs/sslcerts.html) there is some great example
> > >> > code here:
>

> >http://www.gnu-darwin.org/www001/ports-1.5a-CURRENT/net-p2p/py-bittor...

> ...
>
> read more »