php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #31559 fsockopen() timeout STILL(!!!) does not work
Submitted: 2005-01-14 20:52 UTC Modified: 2005-01-31 22:34 UTC
Votes:2
Avg. Score:5.0 ± 0.0
Reproduced:2 of 2 (100.0%)
Same Version:2 (100.0%)
Same OS:1 (50.0%)
From: shelby at coolpage dot com Assigned:
Status: Wont fix Package: Sockets related
PHP Version: 4.3.10 OS: FreeBSD 4.8-STABLE
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: shelby at coolpage dot com
New email:
PHP Version: OS:

 

 [2005-01-14 20:52 UTC] shelby at coolpage dot com 
Description:
------------
This bug has been reported numerous times and it still is not fixed, even though the dozens of previous reports have been closed:

http://bugs.php.net/bug.php?id=24867

http://bugs.php.net/bug.php?id=12360

This is a serious bug.  For example, it enabled a hacker to hang the whole anti-spam engine of AccuSpam.com.

How can we simulate a timeout for fsockopen to work around this bug (since it seems it will NEVER be fixed)???

Is there some other safe test we can do on the "target" before calling fsockopen to determine a target that will lockup the application?

I do not think so.

So that means instead we will have to set up a thread that monitors for hung threads.  Yuk!  Why can't you guys fix this thing after so many years?


Reproduce code:
---------------
See previous similar bug reports.

Expected result:
----------------
See previous similar bug reports.

Actual result:
--------------
See previous similar bug reports.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-01-14 22:07 UTC] tony2001@php.net 
Tested/used many times and works just perfectly on Linux.
Fix your system instead or give us more information about it.
Just complaining never helps.
 [2005-01-14 22:11 UTC] jed@php.net 
Dup of stale bug #24867

Breathe, it was only 'closed' because the submitter of the bug didn't respond for over a week ("No Feedback"). Provide us with more information, please. "See previous bug reports" does not help us at all.
 [2005-01-31 22:34 UTC] sniper@php.net 
Quoting Wez's comment from bug #24867:

"There is no bug here that PHP can fix; move along."
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Mon Dec 30 14:01:28 2024 UTC