Subject: CAcert Code Development list.
List archive
- From: mapc <mapc AT cupdev.net>
- To: cacert-support AT lists.cacert.org
- Cc: cacert-devel AT lists.cacert.org, ulrich AT cacert.org
- Subject: Re: [HTTPS API] CSR format; certificate auth; also
- Date: Sun, 09 Jun 2013 23:40:16 +0200
Hiho,
is there a feasible way to fix these issues myself?
In particular is there
* access to the source
* some way to get my code tested & included
* some way to setup a test enviroment
Cheers,
mapc
On 09.06.2013 23:20, Andre Klärner wrote:
I noticed similiar during my tests with curl. Despite a correct CSR is
sent to the server I was not able to get back a correct certificate, only
the error-message from api/ccsr.php:103. I don't know how the actual
certificate is generated by the api/ccsr.php but from my POV it seems to
get generated in the background and the ccsr.php just waits and looks if
there was a cert generated within the 10s waiting time. So if there is
nothing generated that quickly it always fails. Might this be what
api/ccsr.php:99 is about: "// THIS IS BROKEN AND SHOULD BE FIXED"?
- Re: [HTTPS API] CSR format; certificate auth; also, mapc, 06/08/2013
- <Possible follow-up(s)>
- Re: [HTTPS API] CSR format; certificate auth; also, mapc, 06/09/2013
- Re: [HTTPS API] CSR format; certificate auth; also, Benny Baumann, 06/09/2013
Archive powered by MHonArc 2.6.16.