<HTML>
<HEAD>
<TITLE>Re: [mpeg-OTspec] MD5 is no more considered secure</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
And a large part of the utility of MD5 hashes is to detect corruption from file system or file transmission, a faculty left intact even if security is not. Still, would it not be prudent to provide for stronger security? (Particularly since font viruses have already been demonstrated!) For example, any font with a more secure hashing scheme would also be required to supply the MD5 DSIG. This leaves existing implementations functional, since unknown SFNT tables generally get ignored.<BR>
<BR>
The problem here is that (legitimate) software that modifies fonts but is not aware of the more secure hashing scheme would then end up writing a font with incompatible strong and weak hashes because the strong hash would not have got updated to reflect the changes in the font. But software that leaves in places tables it does not understand when modifying fonts is just asking for trouble anyway, since the unknown table could refer to information in tables that got modified.<BR>
<BR>
Regards,<BR>
<BR>
— daan Strebe<BR>
Senior Computer Scientist<BR>
Adobe Systems Incorporated<BR>
<BR>
<BR>
On 09/12/17 13:09, "Levantovsky, Vladimir" <<a href="vladimir.levantovsky@monotypeimaging.com">vladimir.levantovsky@monotypeimaging.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
<BR>
<BR>
<BR>
<BR>
DSIG is an optional table in the OT/OFF font, the primary reason for its inclusion is to provide a certain level of assurance that the font file has not been tampered with. Even though MD5 may no longer be considered secure, I am not sure if the security in its strict sense would be required and/or necessary here. However, any changes to this part may (and probably will) affect many existing implementations.<BR>
<BR>
Regards,<BR>
Vlad<BR>
<BR>
> -----Original Message-----<BR>
> From: <a href="mpeg-OTspec@yahoogroups.com">mpeg-OTspec@yahoogroups.com</a> <<a href="mailto:mpeg-OTspec%40yahoogroups.com">mailto:mpeg-OTspec%40yahoogroups.com</a>> [<a href="mailto:mpeg-OTspec@yahoogroups.com">mailto:mpeg-OTspec@yahoogroups.com</a> <<a href="mailto:mpeg-OTspec%40yahoogroups.com">mailto:mpeg-OTspec%40yahoogroups.com</a>> ]<BR>
> On Behalf Of Manlio Perillo<BR>
> Sent: Thursday, December 17, 2009 11:47 AM<BR>
> To: <a href="mpeg-OTspec@yahoogroups.com">mpeg-OTspec@yahoogroups.com</a> <<a href="mailto:mpeg-OTspec%40yahoogroups.com">mailto:mpeg-OTspec%40yahoogroups.com</a>> <BR>
> Cc: <a href="opentype-migration-list@indx.co.uk">opentype-migration-list@indx.co.uk</a> <<a href="mailto:opentype-migration-list%40indx.co.uk">mailto:opentype-migration-list%40indx.co.uk</a>> <BR>
> Subject: [mpeg-OTspec] MD5 is no more considered secure<BR>
> <BR>
> -----BEGIN PGP SIGNED MESSAGE-----<BR>
> Hash: SHA1<BR>
> <BR>
> Hi.<BR>
> <BR>
> In the specification for the DSIG table, page 90 in the Open Font<BR>
> Format<BR>
> specification, there is this item:<BR>
> <BR>
> 2. Hash the full stream of bytes using a secure one-way hash (such as<BR>
> MD5) to create the content dig<BR>
> <BR>
> <BR>
> Well, MD5 is *no more* considered secure:<BR>
> <a href="http://en.wikipedia.org/wiki/MD5">http://en.wikipedia.org/wiki/MD5</a><BR>
> <BR>
> <BR>
> Although MD5 is used just as an example, I propose that the text of the<BR>
> specification should be changed, and another hash algorithm used.<BR>
> <BR>
> <BR>
> Regards Manlio<BR>
> -----BEGIN PGP SIGNATURE-----<BR>
> Version: GnuPG v1.4.10 (GNU/Linux)<BR>
> Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org">http://enigmail.mozdev.org</a><BR>
> <BR>
> iEYEARECAAYFAksqYGcACgkQscQJ24LbaUTOCACcDoKRAOv1jXdUkv6Q9jKDFy+F<BR>
> fcoAoJhLY9OhkAXZ0+U5zBtFEHceD5sI<BR>
> =bqdx<BR>
> -----END PGP SIGNATURE-----<BR>
> <BR>
> <BR>
> ------------------------------------<BR>
> <BR>
> Yahoo! Groups Links<BR>
> <BR>
> <BR>
> <BR>
<BR>
<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>