If we've found the End-of-Stream (EoS) page, we should continue to scan past it and decide if any future pages belong to this stream and return an error if so. This will take time and isn't ideal, but if we don't it lets badly formatted Ogg files smuggle in hidden data that isn't visible to tools written or read with this library but which may be visible to other Ogg implementations, leading to odd outcomes and possibly security issues.
How exactly we handle this (keep reading as if the EoS marker was the mistake, return an error but allow the user to read past it, etc.) I'm not sure yet.
If we've found the End-of-Stream (EoS) page, we should continue to scan past it and decide if any future pages belong to this stream and return an error if so. This will take time and isn't ideal, but if we don't it lets badly formatted Ogg files smuggle in hidden data that isn't visible to tools written or read with this library but which may be visible to other Ogg implementations, leading to odd outcomes and possibly security issues.
How exactly we handle this (keep reading as if the EoS marker was the mistake, return an error but allow the user to read past it, etc.) I'm not sure yet.