-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jim Cole wrote:
> On Mar 30, 2007, at 10:51 AM, Joe Auty wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>
>> Joe R. Jah wrote:
>>> Here it is on the patch site:
>>>
>>> ftp://ftp.ccsf.org/htdig-patches/3.2.0b6/SSL_pending.0
>>>
>>> Regards,
>>>
>>> Joe
>>
>>
>> Hmmm... After running teh patch on the source and recompiling
>> from source, I'm still getting the following... Any ideas?
>
> If you haven't already done so, I would suggest you visually verify
> that the patch applied correctly; the key is the addition of the
> SSL_pending line in htnet/SSLConnection.cc. I would also double
> check that the new htdig executable was rebuilt and installed to
> the correct location. Is there any chance that another copy of
> htdig is installed somewhere on the system? Perhaps from a previous
> build, RPM install, etc? If so, make sure there is no chance that
> it is being executed in place of your patched version.
>
Yes, the patch has been applied:
$ diff SSLConnection.cc orig_SSLConnection.cc
134,147c134,145
< if (!SSL_pending(ssl)) {
< if (timeout_value > 0) {
< FD_SET_T fds;
< FD_ZERO(&fds);
< FD_SET(sock, &fds);
<
< timeval tv;
< tv.tv_sec = timeout_value;
< tv.tv_usec = 0;
<
< int selected = select(sock+1, &fds, 0, 0, &tv);
< if (selected <= 0)
< need_io_stop++;
< }
- ---
> if (timeout_value > 0) { FD_SET_T fds; FD_ZERO(&fds); FD_SET(sock,
> &fds);
>
> timeval tv; tv.tv_sec = timeout_value; tv.tv_usec = 0;
>
> int selected = select(sock+1, &fds, 0, 0, &tv); if (selected <= 0)
> need_io_stop++;
Could this problem be with my using a self-signed certificate?
> The error you are seeing is occurring when htdig tries to read the
> header returned from its first request. Its attempt to read from
> the connection times out waiting for data. This ultimately occurs
> in Read_Partial() of SSLConnection, which is the method that the
> patch (theoretically) fixes. The fact that you are still seeing the
> same errors here indicates that you might not really be running a
> properly patched version of htdig. The other possibility is that
> there is still a problem in this code that the patch does not fully
> address. If this is the case, I don't know what else to suggest at
> this point. If the site is publicly accessible, I could try
> reproducing the problem and taking a closer look at what is
> happening at the connection level.
>
> Jim
>
- --
Joe Auty
UITS Messaging
Indiana University
[EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGEqEGIGoilq3QRWsRAk11AJ9c5dfHFpvQqLbCl6VZIN6Dx6UK7ACgpZCF
uQkJTCWc4aFSW/GhN7wzsx4=
=nv49
-----END PGP SIGNATURE-----
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
ht://Dig general mailing list: <[email protected]>
ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-general
