|
From: Carlos V. <car...@ni...> - 2012-04-10 02:03:56
|
> Apart of this patch all seems to be working fine in the OCSP with Cisco. > Will be making more tests soon. I got tired of always seeing "CORE::Connection from [0.0.0.0]", so here is another patch to show the correct address of connections. Code explanation: As connection is handled now by libpki, the function there only returns fd and not a proper socket. So OCSPd code must derive socket from fd using getpeername function. Also I am looking for another problem in code where a fragmented HTTP OCSP request from a Cisco router is getting this in OCSPd: ocspd[5077]: [request.c:45]::ERR::Network Error while reading Request! ocspd[5077]: [threads.c:79]::ERR::Can not parse REQ |