oh my god. now the detection of tricky fonts is becoming something like a discussion for anti-virus software... Do we need the bytecode level finger printing? The embedding producer can spend longer time for bytecode interpretation and size optimization, but the reader of embedded font would not want to spend similar time to detect the tricky fonts...
Behdad Esfahbod wrote: > On 16-01-17 06:58 AM, Werner LEMBERG wrote: >> I think it *is* possible. The method, as implemented by Toshiya-san, >> compares various SFNT table checksums. Among them is the `cvs ' >> table, and modifying this table is essentially impossible without >> interpreting and changing the bytecode. Ditto for `fpgm'. I dare to >> say that even a subsetted font with a single glyph contains the >> original `cvs ' and `fpgm' tables unmodified, which should enable >> FreeType to discover its trickyness. > > Note that this will eventually change ;). > > https://github.com/behdad/fonttools/issues/446 > > behdad > > _______________________________________________ > Freetype-devel mailing list > Freetype-devel@nongnu.org > https://lists.nongnu.org/mailman/listinfo/freetype-devel _______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
