On Mon, Jun 17, 2013 at 10:19 PM, Jeff King <p...@peff.net> wrote:
> On Mon, Jun 17, 2013 at 07:00:40PM -0700, Brandon Casey wrote:
>> Curl requires that we manage any strings that we pass to it as pointers.
>> So, we should not be overwriting this strbuf after we've passed it to
> My understanding of curl's pointer requirements are:
> 1. Older versions of curl (and I do not recall which version off-hand,
> but it is not important) stored just the pointer. Calling code was
> required to manage the string lifetime itself.
Daniel mentions that the change happened in libcurl 7.17. RHEL 4.X
(yes, ancient, dead, I realize) provides 7.12 and RHEL 5.X (yes,
ancient, but still widely in use) provides 7.15. Just pointing it
> 2. Newer versions of curl will strdup the string in curl_easy_setopt.
> So we do not have to worry about newer versions, as they do not care
> about our pointer after curl_easy_setopt returns.
I was probably reading the docs on one of these older platforms when I
wrote this. I've actually had this patch sitting around for a while.
> For older versions, if we were to grow the strbuf, we might free() the
> pointer provided to an earlier call to curl_easy_setopt. But since we
> are about to call curl_easy_setopt with the new value, I would assume
> that curl will never actually look at the old one (i.e., when replacing
> an old pointer, it would not dereference it, but simply overwrite it
> with the new value).
> So for a single curl handle, I don't think it is a problem.
> It could be a problem when we have multiple handles in play
> simultaneously (we invalidate the pointer that another simultaneous
> handle is using, but do not immediately reset its pointer).
Don't we have multiple handles in play at the same time? What's going
on in get_active_slot() when USE_CURL_MULTI is defined? It appears to
be maintaining a list of "slot" 's, each with its own curl handle
initialized either by curl_easy_duphandle() or get_curl_handle().
So, yeah, this is what I was referring to when I mentioned
"potentially dangerous". Since the current code does not change the
size of the string, the pointer will never change, so we won't ever
invalidate a pointer that another handle is using.
The other thing I thought was potentially dangerous, was just
truncating the string. Again, if there are multiple curl handles in
use (which I thought was a possibility), then merely truncating the
string that contains the username/password could potentially cause a
problem for another handle that could be in the middle of
authenticating using the string. But, I don't know if there is any
multi-processing happening within the curl library.
Snip the remaining comments about allowing the user to specify
multiple passwords since I'm not sure they're relevant if we are
indeed using multiple curl handles.
If we _don't_ ever use multiple curl handles, and/or if there is no
threading going on in the background within libcurl, then I don't
think there is really any danger in what the current code does. It
would just be an issue of needlessly rewriting the same string over
and over again, which is probably not a big deal depending on how
often that happens.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html