[mpeg-OTspec] proposing DSIG update, again.

[Peter Constable]

Hin-Tak:

It is a deadline, but not the last deadline for the 4th edition. I would like to investigate this further before making any spec changes. It may be an option for us to fix mssipotf.dll, which might be a better approach than changing the spec after over a decade.


Peter

From: mpeg-OTspec at yahoogroups.com [mailto:mpeg-OTspec at yahoogroups.com] On Behalf Of Hin-Tak Leung htl10 at users.sourceforge.net [mpeg-OTspec]
Sent: Monday, January 9, 2017 1:49 PM
To: Basit Ali <alib at microsoft.com>; Greg Hitchcock <gregh at microsoft.com>; Typography Site Comments <mstwsite at microsoft.com>
Cc: VladimirLevantovsky <vladimir.levantovsky at monotype.com>; mpeg-OTspec at yahoogroups.com; OpenType List <opentype-list at indx.co.uk>; Cosimo Lupo <cosimo.lupo at daltonmaag.com>
Subject: [mpeg-OTspec] proposing DSIG update, again.



Hi all,

It is another deadline for RFC for OT spec 4th edition tomorrow. May I propose once again the following change be made:

Referring to:
http://www.microsoft.com/typography/otspec/dsig.htm

- Remove "4. Zero out the file checksum in the head table." and
- Renumbering "5. Add the usFlag (reserved, set at 1 for now) to the stream of bytes" to 4.

The reason for change is that, this is how we understand Microsoft's signing/verification module, the most widely used implementation, works.

I don't know who at Microsoft is supposed to be in charge of mssipotf.dll - the font signing/verfication wintrust module.
Ali seems to have access to the most current binaries, and Greg seems to be generally involved with font-related matter at the deep coding level. Could we at least identify somebody or the team at Microsoft who is "in charge of" mssipotf.dll (if there is indeed such a party) to corroborate the suggestion above?

Hin-Tak

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20170109/de95b47e/attachment.html>