User:Chris.sherlock/sandbox

Windows Metafile (WMF) is an image file format originally designed for Microsoft Windows in the 1990s. The original Windows Metafile format was not device-independent (though could be made more so with placement headers) and may contain both vector graphics and bitmap components. It acts in a similar manner to SVG files. WMF files were later superseded by Enhanced Metafiles (EMF files) which did provide for device-independence. EMF files were then themselves enhanced via EMF+ files.

Essentially, a metafile stores a list of records consisting of drawing commands, property definitions and graphics objects to display an image on screen. There are three major types of metafiles - a WMF is a 16-bit format introduced in Windows 3.0. It is the native vector format for Microsoft Office applications such as Word, PowerPoint, and Publisher. revision 14 of the Windows Metafile Format specification is available for online reading or download as PDF. EMF files, which replaced WMF files, work on the same principle only it is a 32-bit file format that also allows for the embedding of private data within "comment" records. EMF+ is an extension to EMF files and embedded in these comment records, allowing for images and text using commands, objects and properties that are similar to Windows GDI+.

History
The original 16 bit WMF file format was fully specified in volume 4 of the 1992 Windows 3.1 SDK documentation (at least if combined with the descriptions of the individual functions and structures in the other volumes), but that specification was vague about a few details. These manuals were published as printed books available in bookstores with no click through EULA or other unusual licensing restrictions (just a general warning that if purchased as part of a software bundle, the software would be subject to one).

Over time the existence of that historic specification was largely forgotten and some alternative implementations resorted to reverse engineering to figure out the file format from existing WMF files, which was difficult and error prone. In September 2006, Microsoft again published the WMF file format specification in a more complete form in the context of the Microsoft Open Specification Promise, promising to not assert patent rights to file format implementors.

Microsoft later deprecated WMF files in favour of 32-bit EMF files as WMF files had real issues with device independence, despite the use of a "placeable" file header which provided basic device independence. Microsoft found that developers who use the format were "[embedding] application, location, or scaling comments in the metafiles... Others added headers to the metafile that provided various application-specific information", causing major compatibility issues. Thus, in 1992 with Windows NT 3.1, Microsoft introduced the Enhanced Metafile format (EMF) &mdash; a format which was based on the Win32 API and with which they built-in in device independence. &mdash; these were also known as NT metafiles. With the release of Windows XP and GDI+, the set of records had to be significantly increased and so Microsoft released EMF+ as an extension to the existing EMF file format.

Metafile structure
WMF, EMF and EMF+ files all consist of a series of records that are played back to produce graphical output. Some records define objects which can specify graphical objects used to determine how graphics should be drawn (e.g. pens specify the color and width of lines). Each of these objects are stored in metafiles and are placed into an object table, which tracks the usage of graphic objects while processing the metafile. The object table is an associative array of indexes to graphical object structures defined within the metafile.

WMF and EMF files handle object processing differently to EMF+ records in EMF files. As a WMF and EMF file is being processed, the records are read into an object table once an object is defined. If an object is deleted then the object is released from the table and the identifier can be reused. Notably an object will not be used until it is specifically selected during record playback. This differs for EMF+ files, which also use an associative array via a hashmap which records the object along with an object identifier. However, unlike WMF and EMF files which can delete an object, when a new object is created that has the same index as an existing object, the entry in the table is replaced with the new object. An EMF file also does not need to specifically select an object before it is used.

WMF


WMF files were not originally designed to be device independent, meaning that you could not playback the file on output devices that differed from the original device on which the file was recorded. A partial solution to this issue was invented by Aldus Corporation, who added an additional "placeable" header, called the "APM header", which added a bounding rectable, a metafile version, metafile size, number of objects in the metafile and the size of the largest single record in the metafile. This was later incorporated into the WMF format by Microsoft, starting in Windows 2000.

WMF files are structured by a series of records, starting with a number of control records: the header record, the aforementioned optional placeable record, and finished by an end of file record.

Encapsulated by the control records are the records that make up the image itself. These records work within what is known as the playback device context, which is the collection of properties and objects that make up a device's graphical environment as the metafile is being "played back" onto this output device.

Records other than control records can be largely grouped into bitmap records, drawing records, object records, state records and escape records.

Bitmap records
Bitmap records manage and output bitmap images.

Drawing records
Drawing records produce graphics output.

Object records
Object records create and manage graphics objects. In WMF files there are two broad categories of objects - graphics objects and structure objects. Structure objects are not explicitly created or deleted in a WMF, they are instead of complex structures. For example, the BitmapCoreHeader contains information about the dimensions and color format of a device-independent bitmap, which is itself part of a DeviceIndependentBitmap object. A graphics object, however, specifies parameters for graphics output and during playback of the WMF it sets up the playback device context.

Graphics objects can be brushes (defines the style, color and pattern of a brush which defines how to paint an area of the graphic), fonts (defines properties that affect how text is displayed), palettes (specifies colors as device-independent values, defined by an application), pens (specifies the graphical attributes of a line), and regions (which specify line and curve segments that define a shape).

State records
State records manage the graphics properties of the playback device context.

Escape records
Escape records are a means to extend metafile functionality via records that are not otherwise defined as a WMF record type. Each escape record contains a record function, an escape function and potentially escape data.

The following escape records make up a WMF file.

There was a major vulnerability found in escape records around the Abort escape record, which stores the abort procedure code within the record itself. This affected Windows systems (see ) and the Wine project (see ). According to Secunia, "The vulnerability is caused due to an error in the handling of Windows Metafile files ('.wmf') containing specially crafted  'Escape' records. Such records allow arbitrary user-defined function to be executed when the rendering of a WMF file fails." According to the Windows 3.1 SDK documentation, the  escape was obsoleted and replaced by the function of the same name in Windows 3.1, long before the WMF vulnerability was discovered. However the obsoleted escape code was retained for compatibility with 16 bit programs written for (or at least backwards compatible with) Windows 3.0. This change happened at approximately the same time as Microsoft was creating the 32 bit reimplementation of GDI for Windows NT, and it is likely that the vulnerability occurred during this effort.

After Steve Gibson from Gibson Research Corporation accused Microsoft of deliberately implementing a backdoor into their code, Mark Russinovich provided a rebuttal, and stated that:

"...things were different when the format was architected. In the Windows 3.1 “large” memory model code is inherently location-independent and Windows was never patched, so both Windows and an application could simply copy an application function into the WMF file and assume it would work when played back by the same application in a later run session. In any case, its not clear that the developers envisioned applications creating on-disk metafiles with abort procedures. Also, as Microsoft’s Stephen Toulouse pointed out in Microsoft’s rebuttal to Steve’s claims, the security landscape in the early 1990’s was very different than today and all code, including that stored in a WMF file, was inherently trusted."

Peter Ferrie of Symantec Security Response, USA also disagreed with Gibson, noting that:

"Gibson claimed that a thread is created to run the SetAbortProc handler. In fact, no thread is created to run the handler – it is a callback, which is called by the parser, and the parser has to wait until the callback returns, otherwise the whole point of the function (to abort the printing) is lost. By his own admission, Gibson did not read the documentation (in fact, he claimed that he couldn’t find it, although it is freely available on Microsoft’s Web site), and he claimed that the device context is not available to the function handler. Of course the device context is available to the function handler &mdash; it is one of the two parameters that is passed to it (see above), and it is required in order to abort the printing. Finally, Gibson claimed that the control flow could not return to Windows. It is simply a matter of the function returning and discarding the parameters that were passed on the stack. If the record is well formed, Windows will continue to parse the file, as before. ... Gibson admits that he was guessing about a number of things. Unfortunately, he guessed poorly. I guess we know better now."

EMF
Like WMF files, EMF files use a series of records to draw images that are rendered onto a playback device context. However, EMF files are device-independent, which is accomplished via a header that can define the pixel format and allow accurate measurement of distances on device surfaces. Furthermore, EMF files use coordinate spaces and transformations to stretch, rotate, squeeze, rotate, shear, reflect and translate graphics output on a Cartesian plane.

Like WMF files, records can be classified by function, however there are more record types in EMF files than there are in WMF files. Records can be classified as control, bitmap, clipping, comment, drawing, escape, object creation, object manipulation, OpenGL, path bracket, state and transform records.

Coordinate systems
Working in coordinate spaces allows EMF files to map to the four Windows GDI spaces, which are defined as world space, page space, device space, and physical device space. In practice, graphical objects are either first mapped from the world space if set (which must first specify a two-dimensional linear transformation between world space and page space for the specified device context) or page space if not. For a graphical object to be painted, it must be processed through a coordinate transformation pipeline:


 * 1) If the world space has been set, then the graphics will exist in a world coordinate system. The world space is 2$32$ units high and 2$32$ units wide.
 * 2) A graphical object will be next transformed into the page space if the world space is set, otherwise the coordinate system starts from the page space. This space uses a logical (device-independent) coordinate system. Graphical objects use a world space to page space transformation to support scaling, translation, rotation, shearing, and reflection.
 * 3) Graphics in page spaces are mapped to a device space. The page space is commonly referred to as the window and the device space is referred to as the viewport. The window and viewport each have an origin and an extent consisting of the width and height. Each unit of the page space maps to a unit in the device space via one of six predefined mapping modes (MM_HIENGLISH, MM_LOENGLISH, MM_HIMETRIC, MM_LOMETRIC, MM_TEXT, and MM_TWIPS) or by one of two user-defined mapping modes (MM_ISOTROPIC and MM_ANISOTROPIC). Using the origin and extents of the window and viewports, a translation is performed to convert the graphical object from page space to device space.
 * 4) The final step is to convert to the physical device space, or the client area of the physical output device. Examples of this are the area of a computer window that is displaying, the desktop, or the physical dimensions of a page of paper that is being printed on.

Control records
Control records consist of and one of three EMF headers and an end of file marker followed by an optional palette.

EMF files have three possible versions of headers. The original headers is just a container for images, the second and third version encapsulates the original header and contains a pixel format record and support for OpenGL records, and the third version encapsulates the second header extension and increases EMF accuracy and scalability of EMFs as it adds the ability to measure distances of device surfaces using the metric system.

Each EMF header starts with an  record, and records the relevant properties of the device on which the metafile image was recorded. The original EMF header has an 80 byte header and an optional variable length description string. Other metafiles contain extension fields, which encapsulate the original header. is a record that is inserted directly after the original EMF header, specifies whether there is a pixel format descriptor and the offset to the descriptor object within the header, as well as a field that specifies if OpenGL records exist in the metafile. The pixel format descriptor specifies the capabilities of the drawing surface and whether a pixel is encoded in RGBA or is an index into a color table. is a record that is inserted directly after the  record, and it contains two fields with the X and Y values to measure the device surface in micrometers.

Clipping records
EMF files have a class of record that deal with clipping. The following record types perform clipping operations:

Comments records
Comment records allow private data to be included in EMF files. When EMF files are read, comments records are skipped by applications that cannot read them. Whilst you can include arbitrary private data, the most notable usage of comment records are EMF+ files, which are actually records contained in an EMF comment and such files can be considered EMF+ only or EMF+ dual format &mdash; the former means that you can just use EMF+ records to draw the image fully, the later means the file contains both EMF and EMF+ records; you must only one type to draw the image. However, Microsoft also takes advantage of comment records to also produce EMFSPOOL files, which store portable definitions of print jobs that output graphical images.

Another type of comment record in an EMF is called a public comment record. Public records can group drawing records via an and   records. Public comments can also contain images in multiple graphics formats. This includes EPS data and interestingly can also contain embedded EMF images within the EMF image itself. WMF files can also be embedded in EMF files via a non-multiformat comment type named the  comment record.

EMF+
With the release of Windows XP, the Enhanced Metafile Format Plus Extensions (EMF+) format was introduced. EMF+ provides a way to serialize calls to the GDI+ API in the same way that WMF/EMF stores calls to GDI.

There are also compressed versions of Windows Metafiles known as Compressed Windows Metafile (WMZ) and Compressed Windows Enhanced Metafile (EMZ), which are basically gzip compressed WMF and EMF files correspondingly.

Clipping records
EMF files have a class of record that deal with clipping. The following record types perform clipping operations: