On Fri, Sep 06, 2019 at 05:05:11PM +0200, René Scharfe wrote: > > This approach seems to pretty reasonable. As somebody who's been > > thinking about this, I'd be curious to hear your thoughts on: > > > > https://public-inbox.org/git/20190906065606.gc5...@sigill.intra.peff.net/ > > > > which _in theory_ means tag->tagged would never be NULL (we'd catch it > > at the parsing stage and consider that an error). But we'd still > > potentially want to protect ourselves as you do here for code paths > > which don't necessarily check the parse result. > > A tag referencing an unknown object sounds strange to me. I imagine we > might get such a thing when the referenced object is lost (broken repo) > or purpose-built from an attacker. Could such a tag still be used for > anything? Are there other possible causes? I suspect the answer to > both questions is "no", and then it makes sense to reject it as early > as possible.
I don't think there's really a valid case. Keep in mind that this isn't checking for the object on-disk at all. It's only checking: - were we able to parse the tag at all (i.e., is it syntactically valid) - does it have a type we know about - were we able to create an in-memory struct, meaning we did not see the same oid with a different type elsewhere in the same process The first and middle imply a corruption or malicious attack. The second could mean forward-compatibility is a concern, but I think this is the tip of the iceberg. You really need a Git that understands the object types you're working with, or basically everything is going to fail. So I'm not too concerned with tightening this code. The question to me is whether to do it in parse_tag(), or when accessing tag->tagged, or both. > But I may be missing something. In particular I'm confused by these > patches from February 2008, which seem to suggest that such tags should > not be reported in all cases, but sometimes just silently ignored: > > 9684afd967 revision.c: handle tag->tagged == NULL > cc36934791 process_tag: handle tag->tagged == NULL > 24e8a3c946 deref_tag: handle tag->tagged = NULL > > So is there perhaps a use case for them after all? There's not much discussion on the list from that thread, but searching for messages from Martin around that the main goal was protecting against corruptions. So I think these NULL checks were attempting to do the same thing we're doing here, just in a less centralized way. > Leaving that aside: The parsed flag means we saw and checked the object > already. That is true also for broken objects. Clearing the flag can > cause the same error to be reported multiple times. How about setting > it at the start as before, but returning -1 from parse_tag_buffer() if > .parsed == 1 && .tagged == NULL? That wouldn't cover all of the other reasons that we might have seen a parse failure (so it fixes "tagged == NULL", but means that a subsequent parse_tag() will silently return success). I think the multiple error messages may be OK given that this is explicitly covering a corrupt situation. But the more robust way is adding an extra bit to say "I parsed this already, and it was corrupt" to cause parse_tag() to return an error reliably. -Peff