Conversation:

Notices

1. MMN-o ✅⃠ (mmn)'s status on Monday, 10-Jul-2017 15:21:59 EDT MMN-o ✅⃠

   Remote profile options...

   • headcrack
   @headcrack This is the important bits: readLine, using fgets, socket timeout set explicitly: http://status.hackerposse.com/url/15692 stream_set_timeout when data is sent to fwrite (writing data over HTTP/HTTPS): http://status.hackerposse.com/url/15693 Both of these act _entirely_ individually from iomaster.php and should both trigger if 'fwrite' and its timeout works …
   • MMN-o ✅⃠ (mmn)'s status on Monday, 10-Jul-2017 14:35:47 EDT MMN-o ✅⃠

     Remote profile options...

     • Sebastian
     • headcrack
     @sen @headcrack I'm not sure what you're trying to say here. The lib/iomaster.php doesn't handle HTTP/HTTPS at all, its job is to handle daemons that run locally. So, afaik, only pipes to local processes.
   • MMN-o ✅⃠ (mmn)'s status on Monday, 10-Jul-2017 14:53:49 EDT MMN-o ✅⃠

     Remote profile options...

     • Sebastian
     • headcrack
     @sen @headcrack Unless I'm horribly mistaken, that's an entirely separate timeout. I.e. for the daemon->subprocess. The subprocess on its own has its entirely own timeouts for each individual instruction it runs. Also, if this is supposed to relate to the http://status.hackerposse.com/url/15696 ordeal, it doesn't explain why CURL as a backend handles it perfectly fine…
   • MMN-o ✅⃠ (mmn)'s status on Monday, 10-Jul-2017 15:24:53 EDT MMN-o ✅⃠

     Remote profile options...

     • headcrack
     @headcrack and the stream_set_timeout uses the value of 'max($this->deadline - time(), 1)' which of course is the value in seconds remaining, with 1 as the minimum value.