Olof Fairbrook says git config --blob and other readers of config from memory get each byte from config_buf_fgetc(), which returns a plain "char". Where char is signed, as on x86, a 0xff byte comes back as -1, which is EOF, and any byte from 0x80 up is negative.
The parser therefore stops at a 0xff byte and silently ignores the rest of the blob. His example is a config file whose first comment contains \377. git config --blob=<oid> --list prints nothing for it.
A blob starting with a UTF-8 byte order mark fails with "bad config line 1", because the code that skips the mark compares with unsigned bytes. Config files read from disk are unaffected, since getc() returns unsigned bytes. The excerpt says .gitmodules read from a blob is also affected, but it is cut off before the details.
The patch is at v1 and has no replies yet.