sure!
On 2019-09-23 09:43, Daniel Stenberg wrote:
> On Mon, 23 Sep 2019, Paul Dreik via curl-library wrote:
>
>> https://github.com/curl/curl/blob/41db01a39f88d05f43344d0ea1d1b588b3441403/lib/doh.c#L242
>>
>>
>> the timeout_ms can become negative, and in that case I believe the doh
>> should retu
On Mon, 23 Sep 2019, Paul Dreik via curl-library wrote:
https://github.com/curl/curl/blob/41db01a39f88d05f43344d0ea1d1b588b3441403/lib/doh.c#L242
the timeout_ms can become negative, and in that case I believe the doh
should return an error (perhaps CURLE_OPERATION_TIMEDOUT?)
It should indeed
Thanks!
While you are at that place in the code, could you elaborate on the
timing issue?
At here:
https://github.com/curl/curl/blob/41db01a39f88d05f43344d0ea1d1b588b3441403/lib/doh.c#L242
the timeout_ms can become negative, and in that case I believe the doh
should return an error (perhaps CURLE
On Mon, 23 Sep 2019, Paul Dreik via curl-library wrote:
The decoded contents of the test data means this is what happens:
- set hostname to "A"
- set doh url to "pop3:/tA"
- start transferring
Ah, this a bug but a pretty harmless one:
The code:
https://github.com/curl/curl/blob/41db01a39f88d
Hi,
I am using the existing fuzzers in https://github.com/curl/curl-fuzzer.
When working with the http fuzzer, I found to my surprise that the
fuzzing enters the pop3_done() function.
The http fuzzer sets the allowed protocols to HTTP before starting any
transfers. (line 74 in curl_fuzzer.cc, see
