search for: 34bytes

...d to the payload (1/1000th is a very good ratio). If 32-bits is used as a fixed number, an offset of 0 to 124 (or 128 w/ wrap) could be provided in one byte-field, followed by up to, say, 100 page hashes and still keep the message size under 500 bytes total, the rest of the message being about 34bytes plus the length of the local media path (max 64 bytes). Note that, even if an attacker found an alternative set of data which matched the same identical hash, that page would ALSO need to not only have a valid Ogg header but match the CRC32 checksum contained within the page itself, any of the...