mirror of
https://github.com/curl/curl.git
synced 2026-08-25 03:33:30 +03:00
multi: forbid curl_easy_pause from within multi socket callback
- there is a risk for a nasty recursive situation - we avoid certain risks that the pause call changes things so that when returning from the callback, the state of some internals is undefined and we need to reload which is easy to miss - we can't think of legitiate use cases for doing this. This is basically just the new favorite point for AI and security researchers to find hypothetical problems Closes #22179
This commit is contained in:
parent
d8f9f0a912
commit
a6af50c484
7 changed files with 33 additions and 21 deletions
|
|
@ -28,8 +28,8 @@ CURLcode curl_easy_pause(CURL *handle, int action);
|
|||
|
||||
Using this function, you can explicitly mark a running connection to get
|
||||
paused, and you can unpause a connection that was previously paused. Unlike
|
||||
most other libcurl functions, curl_easy_pause(3) can be used from within
|
||||
callbacks.
|
||||
most other libcurl functions, curl_easy_pause(3) can be used from within all
|
||||
callbacks except the socket callback set with CURLMOPT_SOCKETFUNCTION(3).
|
||||
|
||||
A connection can be paused by using this function or by letting the read or
|
||||
the write callbacks return the proper return code (*CURL_READFUNC_PAUSE* and
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue