Changes to the profile reader behavior (previously the behavior is bugged when encountering such scenario);
- For extbinary format, when reading a second name table, the previous one is cleared (previously causes array out of bound)
- Check if profile mixes MD5 and nonMD5 functions
What is the bogus End used for? Defend against call site that didn't check error and tries to continue reading?