Curl Issues when trying to port https-server into Graphene

[njriasan]

Hi so this issue is not necessarily related to any of the examples but I thought perhaps someone who worked on the project could provide some guidance. I am working on porting the https-server into Graphene (and later once I get that ported I plan on changing the API to prevent writing files to /tmp). To do so I built a shared library to be imported by python using its C Foreign Function Interface and then linked inside the library ldpreload.so (or a renamed variant). Upon moving it into Graphene I encountered an issue with

curl_easy_perform= 35

I then modified the version of Curl being used to rely on openssl in reference to issue I saw in #1 and rebuilt curl as a dynamic library as opposed to static, which now results in

curl_easy_perform= 58

I was wondering if this could be related to #8 as it seems to rejecting the certificate or if anyone had any experience with a similar issue.

[thomasknauth]

I'd try a clean build first. The issue you are seeing may be related to the super-finicky build system which does not really support partial re-builds. Maybe that's what you are experiencing. Other than that, I cannot recall having seen these error codes from libcurl in the past. Standard debug methodology applies: enable debug outputs and potentially build with debug symbols to step through the code. Dealing with TLS/certificate-related issues is rather painful and time consuming, I'm afraid. Keep us posted on your discoveries!