US 5,881,287 AGrant
Method and Apparatus for Copy Protection of Images in a Computer System
Issue Date:1999-03-09
•58 Claims
•7 Drawing Sheets
Abstract
A method and apparatus for securing images from unlicensed appropriation on a computer system. Prior art graphics security measures, such as encryption, cease to protect the images once the images are deciphered and loaded into the video adapter memory. In the present invention, unlicensed transfers of image data from the video adapter to other storage means are substantially prevented by intercepting data transfer requests to the operating system and identifying whether the image is one to be protected. If the image is one that is marked for protection, the region of the data transfer incorporating the protected image is blacked out or replaced with a specified pattern or message. A preferred embodiment provides a library of software routines that are utilized by image display applications. These routines interface with the computer memory and the video display memory to block the copying of designated images by means of "hooks" into the operating system or operating environment. By means of these hooks and routines, the present invention identifies all regions on the video device that contain a protected image and exclude these regions from any operation that transfers data from the video display memory. Any attempts to transfer the designated regions result in an image containing "blacked out" regions in their place. The preferred embodiment includes an encryption scheme for image security prior to display.
Metadata
Inventor
- Michael B. Mast
Application Information
Application Number:US 8241392
Filing Date:1997-03-25
Priority Date:1994-08-12
Art Unit:272
Classifications
IPC:
G06F 1214H04L 900
Field of Search:
395380711345701;712;705;6533-5;9;25;23164;100133;326
Patent Drawings (7 sheets)
Description
Background of the Invention
1. Field of the Invention
The present invention relates to the field of computer image display, and in particular, to image protection.
2. Background Art
In the growing multimedia industry, a critical concern to image creators and image applications developers is image misappropriation, or piracy. Several pre-existing methods for protecting images from piracy have been developed, including watermarks, encryption and proprietary formats.
Watermarks are intentional imperfections in an image before or after it is converted to digital form. The resultant lack of quality in the image mitigates the desire to copy the image. However, watermarking is not satisfactory for imaging and multimedia products as it does not provide the high image quality required for marketable applications.
A more common method of image protection is encryption. Image encryption typically involves taking image data that exists in a standard format, such as GIF or BMP, and converting it into an unrecognizable data file through the use of a mathematical encryption algorithm. Prior to display, the encrypted image is passed through a deciphering process to regenerate the image data in a displayable format. The decrypted data is then placed in the video adapter's memory for use by the display unit.
Without encryption, image files in standard formats are recognized by a broad range of image processing applications. For this reason, unencrypted images can be copied and manipulated through unsanctioned applications. By encrypting computer files, use of the computer files can be restricted to only those applications provided with the deciphering scheme. Image files are therefore substantially protected from misappropriation up until the moment they are deciphered and placed in the video adapter's memory, where a video adapter is any device connected to the computer's data bus, including any local bus, that has its own memory or uses the computer's main memory to render images on a video display device. Once the image is present in the video memory in a standard display format, the image is again susceptible to piracy. Therefore, encryption is a necessary but incomplete protection scheme.
Proprietary formats are image data formats created for use in applications unique to the developer. These formats differ from an encryption scheme in that there often exists a one to one mapping between the source image file and the stored image file. Therefore, an expert may be able to recognize the nature of the data (i.e. that it is image data). In some cases, it is possible to reverse engineer the proprietary format and obtain the images. Further, some proprietary formats are available as part of developer tool kits. The format can be incorporated into a new application that is able to read or transfer proprietary image files.
Regardless of what encryption schemes or proprietary formats are used, an image file must eventually be translated into a standard image file format when it is supplied to the memory for the display unit. Once displayed, the image data sheds all security features. An end user can pirate the image by copying it from the video adapter's memory and storing it in any format. The pirated image data can then be distributed to other destinations.
For example, in the Windows.TM. operating environment sold by Microsoft Corporation, a user may pirate an image by pressing a "PRINT SCREEN" button on a computer keyboard and storing a bit-mapped image of the screen in a "clipboard." From the clipboard, the image can be "pasted" into an image processing application and stored for eventual unlicensed distribution. Therefore, though current encryption methods and proprietary formats are useful for securing image files, they are insufficient for protecting image files once they are provided to a video adapter's memory.
U.S. Pat. No. 4,241,415 to Masaki et al. discloses an apparatus for selectively masking portions of visual output. The apparatus contains a first memory for storing information code signals convertible into visible information and a second memory containing specific code signals in locations corresponding to the code signals in the first memory which selectively are not to be visualized. Signals from each memory are read simultaneously. When the device is in mask mode and a specific code signal is detected in the second memory, the corresponding information code signal in the first memory is masked, either by omission or replacement with a special mark. The Masaki patent does not suggest use of this apparatus in any security scheme.
U.S. Pat. No. 4,352,100 to O'Connell discloses an image formatting apparatus for use in changing image contrast or providing masked borders around selected images. The apparatus is not designed for security purposes. Further, it does not act to blank the selected image, but to blank the areas around it.
U.S. Pat. No. 4,554,584 to Elam et al. discloses an auxiliary circuit for remote control of television receiver blanking by digital code words transmitted as part of the video signal. The circuit allows the end user to determine what video signals to blank from the display unit.
U.S. Pat. No. 4,881,179 to Vincent discloses a method of controlling the unauthorized disclosure of classified data in a calendar application. Only those having a clearance code equivalent to or higher than the specified clearance code for the information can receive the calendar information. No apparatus is disclosed for preventing the copying of calendar images already present on the screen.
U.S. Pat. No. 4,932,053 to Fruhauf et al. discloses a safety device for preventing unauthorized detection of protected data in a memory chip by the use of current sensing approaches. Random current generators within the chip produce random current values on output pins of the chip to conceal actual current values that may indicate memory data values.
U.S. Pat. No. 5,036,537 to Jeffers et al. discloses a method for blocking out video signals in a television receiver. No means are disclosed to prevent copying of images that are allowed to reach the receiver.
U.S. Pat. No. 5,142,576 to Nadan discloses a key security system for selectively providing restricted information to video displays. An encoder transmits display update data and a key to a plurality of decoders. The decoder that matches the key receives the update data and places it in the picture store for a video display. No means are suggested for preventing the copying of images stored in the picture store of the video display.
U.S. Pat. No. 5,144,664 to Esserman et al. discloses a secure communication network serving a plurality of terminals grouped into different security categories. A headend device has several encryption algorithms stored. In addition, each terminal is coupled to a security element providing a decryption algorithm associated with one of the encryption algorithms stored in the headend. When security is breached, the headend switches to a new encryption algorithm and the security elements are replaced with new elements having a new decryption algorithm corresponding to the new encryption algorithm used in the headend. The object is to achieve inexpensive security system replacement in the event of a breach. The subject of copying images is not disclosed.
U.S. Pat. No. 5,208,857 to Lebrat discloses a method for scrambling and unscrambling image data by using the discrete cosine transform on blocks of data and by mixing these data blocks. The scrambled images must be unscrambled before being displayed in a video display unit.
U.S. Pat. No. 5,313,227 to Aoki et al. discloses a graphic display system capable of cutting out a partial image. The system includes image storage means, outline drawing means, mask data generator means, and partial image write means for writing into the image storage means only a portion of the source image which is not masked by the mask data. No means are described to prevent the copying of these stored images.
Summary of the Present Invention
The present invention provides a method and apparatus for securing images from unlicensed appropriation on a computer system. Prior art graphics security measures, such as encryption, cease to protect the images once the images are deciphered and loaded into the video adapter memory. In the present invention, unlicensed transfers of image data from the video adapter to other storage means are substantially prevented by intercepting data transfer requests and identifying whether the image data therein is to be protected. If the image data is marked for protection, the region of the data transfer incorporating the protected image is blacked out or replaced with a specified pattern or message.
A preferred embodiment provides a library of software routines that are utilized by image display applications. These routines interface with the computer memory and the video display memory to block the copying of designated images by means of "hooks" into the operating system or operating environment. By means of these hooks and routines, the present invention identifies all regions on the video device that contain a protected image and exclude these regions from any operation that transfers data from the video display memory. Any attempts to transfer the designated regions result in an image containing "blacked out" regions in their place.
An encryption scheme is associated with the preferred embodiment of the present invention. A virtual device driver and decryption server are described which perform the decryption of the image data. The encryption/decryption scheme provides security for the image data up until the data is decrypted and placed in the video memory, at which time the present invention provides security for the decrypted data in the video memory.
Brief Description of the Drawings
FIG. 1 is a block diagram of a read request processed in a sample Microsoft Windows.TM. environment.
FIG. 2 is a block diagram of a pre-installation procedure for a preferred embodiment of the present invention.
FIG. 3 is a block diagram of an installation procedure for enabling the Decryption Virtual Device Driver of the preferred embodiment of the present invention in the End User's system.
FIG. 4 is a block diagram of an encryption procedure utilized in the preferred embodiment of the present invention.
FIG. 5 is a block diagram of a read request processed in a sample Microsoft Windows.TM. environment incorporating the preferred embodiment of the image protection scheme of the present invention.
FIG. 6 is a flow diagram of the image blocking operation of the preferred embodiment of the present invention.
FIG. 7 is a flow diagram of the encryption installation procedure of the preferred embodiment of the present invention.
FIG. 8 is a graphic illustration of the image blocking operation of the present invention.
Detailed Description of the Present Invention
A method and apparatus for copy protection of displayed images in a computer system are described. In the following description, numerous specific details, such as operating system environments and encryption processes, are described in order to provide a more thorough description of the present invention. It will be apparent, however, to one skilled in the art, that the present invention may be practiced without these specific details. In other instances, well-known features have not been described in detail in order to not obscure the present invention unnecessarily.
FIG. 1 illustrates how a read request is processed in the prior art in a Microsoft Windows.TM. 3.1 environment (hereafter referred to as "Windows") in enhanced mode. The system is comprised of Virtual Machines VM1 and VM2, Virtual Machine Manager VMM, Windows executable program WIN386.EXE, and the operating system MS-DOS. Virtual Device Drivers VxD3 and VxD4 represent other drivers present but nonintegral to the Windows system. This system is shown for purposes of example only, and presents only one possible environment.
Virtual Machine VM1 contains Windows Applications 1-3 and associated Dynamic Link Libraries (DLLs) 1-3. A fourth application, WINOA386.MOD, does not call any DLLs. Other components of Virtual Machine VM1 are the core Windows modules: USER.EXE, KRNL386.EXE and GDI.EXE. These core modules make calls to the standard drivers, e.g. display adapter, printer and scanner drivers. The GDI.EXE program or Graphics Device Interface, contains many functions for displaying graphic output. WIN386.EXE contains many virtual device drivers (VxDs), including the DOSMGR device driver which interfaces with the Virtual Machine Manager and the MS-DOS operating system. Virtual device drivers are device specific, converting general commands into the precise actions required to implement the command on a specific device. MS-DOS does not handle application address space above one megabyte inherently. Therefore, DOSMGR assigns Windows applications address space below one megabyte and copies data from this lower address space to the upper address space in a manner that is transparent to the application. Other VxDs within WIN386.EXE are responsible for such items relative to Windows as a timer, math coprocessor, interrupt controller, etc.
In FIG. 1, Windows Application 1 is able to make calls to DLL1 and DLL2. Windows Application 2 is able to make calls into DLL2 and DLL3. Windows Application 3 can make calls only into DLL3. The first two applications make calls into two DLLs while at the same time sharing one of the DLLs. The third application makes calls only into one DLL, which is also shared by the second application. In addition, all Windows-based applications and DLLs make calls into USER.EXE, KRNL386.EXE, and GDI.EXE. When not in full screen mode, WINOA386.MOD provides Virtual Machine VM2, also commonly referred to as a "DOS box," with a captioned window from which various settings affecting the virtual machine may be set.
In enhanced mode, a major component of Windows is the Virtual Machine Manager. Two of the Virtual Machine Manager's more important roles are to provide the virtual machines necessary for running Windows and supporting any of Windows' virtual DOS sessions, and to coordinate the virtual device drivers which resolve resource contention issues among the various virtual machines.
FIG. 1 illustrates how a typical request to read data is handled. Windows Application 1 makes a request (step 1) of the operating system to read data from a file. It is assumed that the file exists and has been opened for reading. The DOSMGR device driver intercepts the request and passes the request (step 2) along to the MS-DOS operating system which performs the read, reading the data into an area which MS-DOS can address. DOSMGR then copies the read data into the Windows Application's data area and signals to Windows Application 1 that the read is complete (step 3). Windows Application 1 then continues processing (step 4).
If the read data was encrypted by an encryption program, the Windows application will not be able to correctly interpret the read data, which is still encrypted. The Windows application will either recognize that it cannot understand the data and produce an appropriate error message for the user to respond to, or it will fail. In either case, the user is not granted access to the image file.
The preferred embodiment of the present invention is described as applied to the Windows 3.1 environment as outlined in FIG. 1. The present invention can be similarly applied in other system environments for image protection. In the preferred embodiment, an encryption scheme is described for protection of images up to the point when the images are loaded into a graphics application. The present invention can be used with other encryption schemes as well.
The encryption scheme in the preferred embodiment begins with an operating system-based pre-installer and an encryption key. The developer of multi-media products (hereafter referred to as "the Developer") has one encryption key per product line. The pre-installer (PREINSTL.EXE) of the preferred embodiment reads the encryption key and the actual executable multi-media application that the Developer will be distributing. The pre-installer modifies two programs, ENCRYPT.EXE and UINSTALL.EXE, and one library, UINSTALL.DLL. The encryption key and the application's "signature" are recorded in ENCRYPT.EXE, UINSTALL.EXE and UINSTALL.DLL. The "signature" is a collection of information about a specific application. It is used to determine the authenticity of the program requesting access to the encrypted files.
FIG. 2 illustrates the pre-instaflation process. Block 200 is the encryption program without the encryption key installed. Block 201 represents the End User installation components, UINSTALL.EXE and UINSTALL.DLL, with no encryption key installed. Block 202 represents the Developer's assigned encryption key for the appropriate product line. Block 203 represents the Developer's executable application program, xxxxxxx.EXE. Block 204 represents the encryption program with the encryption key installed. Block 205 represents the End User installation components with encryption key and application signature installed. Block 206 represents the execution block of PREINSTL.EXE.
As outlined above, The elements of blocks 202 and 203 are read by the pre-installation program, PREINSTL.EXE, in block 206, and used to modify the programs and library contained in blocks 200 and 201. The output blocks 204 and 205 contain programs and a library personalized to the encryption key and signature of the individual product line.
The pre-installation procedure comprises several steps. First, PREINSTL.EXE creates a string of random data whose length is equal to or greater than the length of the Developer's encryption key and program "signature." According to predetermined criteria, some or all of this random data is then exclusive or'ed with the encryption key and "signature" producing an encrypted encryption key and "signature." The encrypted encryption key and "signature" are written to UINSTALL.EXE and UINSTALL.DLL along with the random data. The fact that random data, some of which may not participate in the exclusive or'ing of the encryption key and "signature," is added to UINSTALL.EXE and UINSTALL.DLL makes it almost impossible to determine where and how the encryption key and "signature" are stored in UINSTALL.EXE and UINSTALL.DLL.
UINSTALL.EXE is a Windows-based installer with an operating system-based version as its stub. UINSTALL.DLL is a Windows-based dynamic link library. The Developer uses only one of these files, the appropriate file depending on the procedure used to install the Developer's application on the End User's computer.
UINSTALL.EXE can be run as a Windows-based program or at the operating system level. When run as a Windows-based program, UINSTALL.EXE does not require a main window or dialog box of any kind. UINSTALL.EXE can therefore run without requiring the End User to be aware of it. If the Developer prefers, a Windows-based installer capable of making calls into a DLL can make calls into UINSTALL.DLL and thus perform the install operations.
Whichever option is chosen, UINSTALL.EXE or UINSTALL.DLL (already modified by PREINSTL.EXE) modifies a copy of a Decryption Virtual Device Driver installed on the End User's computer. As shown in FIG. 3, the Decryption VxD (block 301) is read by either UINSTALL.EXE or UINSTALL.DLL (block 302) and modified to include the encryption key and the application signature. The "installed" Decryption VxD (block 303) contains the Developer's encryption key and application signature in an internal "table" of encryption keys. This procedure allows the End User to have a variety of products which use the security system of the preferred embodiment installed on the End User's computer while only requiring one copy of the Decryption VxD. In such a situation, the Decryption VxD's internal table would hold multiple encryption keys.
The Decryption VxD in the preferred embodiment is a Windows-based virtual device driver. The Developer distributes the Decryption VxD along with the Developer's application. The parameters or script that are used by the Developer's installer are modified to include the Decryption VxD and an image protection DLL (BITBLOCK.DLL, see below), and also to run UINSTALL.EXE or make calls into UINSTALL.DLL. The Decryption VxD provides the Developer's application with the ability to read the encrypted files which the Developer has sold to the End User. The Decryption VxD provides the decryption functionality without requiring modifications to the Developer's source code, or additions or replacements in any object code. Therefore, the Developer's application can read encrypted files even if third party object code or DLLs are used to access image files stored on disk.
Similar to the pre-installation procedure, the UINSTALL process also creates a string of random data whose length is equal to or greater than the length of the total amount of data (including the encrypted encryption key, the program "signature" and the random data) written to UINSTALL.EXE and UINSTALL.DLL by the pre-installation process. According to predetermined criteria, some or all of this random data is then exclusive or'ed with the data that was written to UINSTALL.EXE and UINSTALL.DLL. The result of this exclusive or'ing of data along with the random data is written to the Decryption VxD. The fact that random data, some of which may not have participated in the exclusive or'ing of the data written to UINSTALL.EXE and UINSTALL.DLL, is added to the Decryption VxD makes it almost impossible to determine where and how the encryption key and "signature" has been stored in the Decryption VxD.
ENCRYPT.EXE is an operating system-based encrypter. This program is used by the Developer to encrypt the image files prior to their distribution to the End User. Once encrypted, the End User must have the Developer's product installed on their computer system in order to read the encrypted files which the End User has purchased. The Developer uses ENCRYPT.EXE to encrypt image files of any format (e.g. BMP, GIF, JPG, etc.). For example, IMAGE.BMP which the Developer has encrypted cannot be read by just any application capable of reading BMP files. This is true even if the other application also uses the same encryption method because a different key and signature will be associated with the other application.
FIG. 4 illustrates the encryption process. The unencrypted image file (block 400) is processed by the ENCRYPT.EXE program in block 401. The encryption program generates the encrypted image file (block 402) as an output file. The encrypted image file is then distributed to the End User for use with only the appropriate application.
FIG. 7 is a flow chart of the encryption installation steps of the preferred embodiment. Encryption is not necessary for the present invention to function. However, securing the image files with some form of encryption scheme protects the files from misappropriation prior to display. Encryption schemes other than the one described herein are usable as well.
In FIG. 7, the encryption installation procedure begins by assigning an encryption key to the Developer's product. The installation begins with the PREINSTL.EXE block 706 which comprises blocks 701-705. In block 701, the "signature" of the product is determined. In block 702, the encryption key is installed in the encryption program ENCRYPT.EXE. In blocks 703 and 704, the encryption key and product signature are first exclusive or'ed with random data and then, in block 705, the exclusive or'ed data and the random data, some of which was used in the exclusive or'ing operation, are installed in the user install elements, UINSTALL.EXE and UINSTALL.DLL.
After PREINSTL.EXE is completed, ENCRYPT.EXE can be used to encrypt image files for distribution to the End User as stated in block 707. In block 708, the End User begins installation of the product on his or her system, running UINSTALL.EXE or making calls to UINSTALL.DLL. Block 712 represents the UINSTALL.xxx operation, comprising blocks 709-711. In blocks 709 and 710, the data containing the encrypted encryption key, signature and random data is again exclusive or'ed with more random data and augmented with the random data, some or all of which was used in the exclusive or'ing process. In block 711, the twice-encrypted key and signature are installed in the Decryption Virtual Device Driver's "table."
FIG. 5 illustrates how a read request is performed in the system of the preferred embodiment. Unlike the system of FIG. 1, in FIG. 5, the Decryption VxD is introduced between the Virtual Machine Manager (VMM) and the operating system (MS-DOS). Also, a Decrypt Server VM3 runs in parallel with the other virtual machines. The increased image protection method of the present invention is provided by the BITBLOCK.DLL dynamic link library into which Windows Applications 1 and 2 make calls. BITBLOCK.DLL is also able to make calls into the enabled applications.
BITBLOCK.DLL performs it's functions by means of "hooks" into Windows (or other operating environment in a non-Windows embodiment). "Hooks" are resources that install filter functions. These filter functions process "hooked" function calls before the functions that were hooked are called. The three Windows modules (USER.EXE, KRNL386.EXE and GDI.EXE) make calls into the BITBLOCK.DLL by means of these hooks. As BITBLOCK.DLL is a Windows library, the Developer makes minor source code modifications to an enabled application and link edits the application along with BITBLOCK.DLL. BITBLOCK.DLL prevents the Developer's protected images from being copied to any destination (e.g. global memory, the Windows clipboard, etc.) by any application other than the Developer's product, including Windows itself.
Virtual Machine VM3 is the virtual machine in which the Decryption Server runs. This virtual machine is not a "DOS box" in the usual sense. While the Decryption Server is a DOS-based program, the virtual machine in which it runs is not associated with a WINOA386.MOD window. Hence, it is not visible to the End User. It also does not appear in the Task Manager's list of applications (TASKMAN.EXE, part of Windows).
A request by Windows Application 1 to read data proceeds as follows. The application makes a request (step 1) to the operating system to read a file (assuming the file is present and has been opened for reading). The Decryption VxD intercepts the request (step 2) by virtue of "hooks" in the Virtual Machine Manager and decides if it is the type of file in which it is interested. The Decryption VxD does this by tracking the opening of files and matching the file types, as determined by its extension (e.g. xxxx.GIF, xxxx.BMP or xxxx.HLP, etc.), against a list of file extensions which it obtains from the BITBLOCK.INI initialization file. If the extension is one that the Decryption VxD is not interested in, such as a .HLP file, the VxD allows the request to proceed. If the file is a file of interest, such as a .BMP "bitmap" file, the VxD checks to see if the file is encrypted in the ENCRYPT.EXE format by examining the first several bytes of the file for the expected encryption signature (encrypted files maintain the same extension as unencrypted files). If the file being read is not encrypted, or at least not encrypted in the expected format, the Decryption VxD passes the request on to the DOSMGR (step 3) and the request proceeds normally, as described with respect to FIG. 1.
If the file being read is encrypted, as determined by the first block of data written to the file, the Decryption VxD determines if the application is enabled to read the encrypted data. The VxD does this by comparing the Window Application 1's "signature" to that which is stored in the VxD's internal tables. If the application has not been enabled to read the encrypted data, the VxD issues an appropriate error message to the user and passes the request on to DOSMGR. An unenabled application will be unable to process the encrypted data.
If Windows Application 1 is enabled to read encrypted data, the VxD determines the key necessary to decrypt the data. The VxD then issues its own request to read the data (steps 2-4). The read data is then passed on to the Decryption Server (step 5). The Decryption Server takes the data and key supplied by the Decryption VxD and decrypts the data. Once decrypted, the Decryption Server notifies the Decryption VxD that it has completed decrypting the data (step 6) and the VxD copies the decrypted data into the Window Application's data area and signals the application that the read request has completed (step 7). The Windows Application then finds decrypted data in its read area and continues processing as though the data had never been encrypted (step 8).
These steps prevent all but enabled Windows Applications whose keys and "signatures" have been installed in the Decryption VxD from reading unencrypted data from files that have been encrypted using the application's key. Once the Windows Application has displayed the unencrypted image files on the screen, the BITBLOCK.DLL library becomes active in impeding the displayed data from being copied from the screen to some other area from which it may be written to a file in an unencrypted form.
Each enabled Windows Application registers with the BITBLOCK.DLL, specifying a callback procedure located within the application that is to be called by the DLL. The BITBLOCK.DLL dynamic link library maintains a list of these callback procedures. By means of hooks placed in the GDI.EXE program, specifically to the "BitBlt" function, BITBLOCK.DLL is able to monitor when requests are made for a transfer of data from the video memory. When BITBLOCK.DLL detects that an application (or one of the application's DLLs) is attempting to copy anything from the screen to any destination, BITBLOCK.DLL processes through the list of callback functions. If the list is empty, i.e. there are no callback functions, BITBLOCK.DLL permits the copy attempt to succeed, resulting in image data being copied from the screen (video adapter memory). If there are callback functions identified in the list, BITBLOCK.DLL calls each of the callback functions.
Each callback function returns to BITBLOCK.DLL either an object which identifies which region of the screen is to be protected or zero, indicating that there are no more regions requiring protection. A region represents the outline or border defining a portion of device memory. For example, a destination region represents the outline or border defining a portion of memory to which data is to be written. As each callback function returns a region of the device memory to be protected to BITBLOCK.DLL, BITBLOCK.DLL adds the region to a single region that represents all of the combined regions that have been returned. A copy of the original destination region is then saved. The combined region is then removed from the original destination region and the copy attempt is allowed to resume. Thus, all areas except the removed (protected) regions are copied from the video adapter memory. Those areas in the destination region that correspond to the source region from which no source data was copied are then filled with any pattern or distorted in some way to indicate that those regions correspond to protected images. In the preferred embodiment, solid black is used as the fill pattern. The destination region is then replaced with the saved original destination region. The preferred embodiment describes how the destination region is modified to prevent the protected data from being effectively transferred. An alternate embodiment may modify the source region in a similar manner to prevent the transfer of the protected data.
FIG. 6 is a flow diagram of a video memory transfer in the preferred embodiment. The flow begins when BITBLOCK.DLL detects a "BitBlt" function call via hooks to the Windows operating environment. "BitBlt" is a Windows function that copies a bitmap from the source device to the destination device. "hdcSrc" and "hdcDest" parameters specify the source and destination devices, respectively.
When BITBLOCK.DLL detects a BitBIt call, a check is made in block 600 to see if there are any callback functions installed, i.e. if any applications have registered any protected images. If there are no installed callback functions, the BitBlt function is allowed to continue (block 602). If there are installed callback functions, in block 601, BITBLOCK.DLL looks to see if a source device is designated. If no source is designated, the BitBlt function is allowed to continue (block 602).
If a source is designated in the BitBlt call, in block 603, an empty region is created and labeled "CombRgn." Next, in block 604, the first protected image region is received from the first callback function and assigned the label "CBRgn." In block 605, the union of CombRgn and CBRgn is assigned to CombRgn. In block 606, a check is made to see if there are more regions to get from this callback function. If there are more regions, the process returns to block 604, continuing to cycle through blocks 604-606 until there are no more regions specified by that callback function. The process then continues to block 607 wherein a check is made to determine if more callback functions are registered. If more callback functions are registered, the process returns to block 604 to continue with the next registered callback function. Thus, a region of protected images is pieced together as CombRgn.
When the list of callback functions is completed, in block 608, a copy of the original destination region is saved. In block 609, the region of protected images defined by CombRgn is subtracted from the specified destination region of the BitBlt call. In the following block, block 610, the BitBlt function is permitted to transfer the contents of the source device memory into the modified destination region within the destination device memory. Then in block 611, the destination region is reassigned with CombRgn, and in block 612, a fill pattern is BitBlt'ed to the destination region specified by the combined regions of the protected images. In block 612, the destination region is replaced with the saved original destination region.
FIG. 8 illustrates the steps shown in FIG. 6 as applied to an example display image. In FIG. 8, image 800A represents a display with two internal windows or image components, images 801 and 802A. Image 801 is not registered for protection with the system, but image 802A is. When a memory transfer is initiated, such as by pressing the "PRINT SCREEN" key, the region defining the protected image is determined from the registered callback functions to be region 802B. The screen transfer succeeds in transferring all unprotected image components, such as image 801, into destination 800B. The image residing in destination 800B is incomplete, lacking any information in region 802D, the region corresponding to the removal of region 802B from the destination. The present invention fills the region of 802B with a pattern or message indicating the image component is protected. This filled region is labeled 802C. The finished transfer is represented by image 800C, comprising copied image 801 and blocked-out image 802C. The present invention also contemplates the blocking out of selected portions of an image as well.
As only the Developer's application can read and decrypt the image files and no application except the Developer's application can copy the image from the screen, the images are substantially protected from theft.
Thus, a method and apparatus for copy protection of images in a computer system have been provided.
Attached hereto as Appendix 1 is a c-code listing of an example embodiment of the present invention. ##SPC1##
Claims
I claim:
1. A method of providing copy protection in a computer system comprising the steps of: program code executing in said computer system intercepting requests for transfer of data from a source region to a destination region; specifying within said source region a protection region defining protected data; said program code transferring data from said source region to said destination region, excluding said protection region.
2. The method of claim 1 wherein said step of intercepting requests for transfer of data is performed by means of hooks into an operating environment of said computer system.
3. The method of claim 1 wherein said step of determining a protection region comprises the steps of: processing a callback function from an application program; receiving via said callback function an object specifying an individual region to be protected; forming said protection region from said individual region.
4. The method of claim 1 wherein said step of determining a protection region comprises the steps of: processing a plurality of callback functions from at least one application program; receiving via said callback functions a plurality of objects specifying a plurality of individual regions to be protected; forming said protection region from said individual regions.
5. The method of claim 1 wherein said step of transferring data from said source region to said destination region, excluding said protection region, comprises the steps of: subtracting said protection region from said destination region to create a first modified destination region; copying data from said source region into said first modified destination region.
6. The method of claim 1 wherein said step of transferring data from said source region to said destination region, excluding said protection region, comprises the steps of: subtracting said protection region from said source region to create a modified source region; copying data from said modified source region into said destination region.
7. The method of claim 1 further comprising the steps of: replacing said destination region with said protection region to create a second modified destination region; writing said substitute data into said second modified destination region.
8. The method of claim 1 wherein said data comprises image data and said source region defines a portion of video adapter memory.
9. A method for protecting files within a computer system from misappropriation, said method comprising the steps of: encrypting files selected for protection; deciphering said encrypted files only for authorized applications; prohibiting copying of decrypted file data selected for protection from device memory, said prohibiting process implemented in program code executing in said computer system and comprising the steps of: intercepting data transfer requests; determining a protected region of said device memory comprising said decrypted file data selected for protection; copying into a destination memory only data from those portions of said device memory not within said protected region.
10. The method of claim 9 further comprising the step of filling said protected region within said destination memory with alternate data.
11. The method of claim 9 wherein said step of intercepting data transfer requests is performed by means of hooks into an operating environment of said computer system.
12. The method of claim 9 wherein said step of determining said protected region of said device memory comprises the steps of: processing through a callback function from an application program; receiving via said callback function an object specifying an individual region to be protected; forming said protected region from said individual region.
13. The method of claim 9 wherein said step of determining said protected region of said device memory comprises the steps of: processing through a plurality of callback functions from at least one application program; receiving via said callback functions a plurality of objects specifying a plurality of individual regions to be protected; forming said protected region from said individual regions.
14. A method of file protection for a computer system comprising the steps of: encrypting selected files using an encryption key; intercepting a read request from an application program; determining if a requested file is one of said selected files; allowing said read request to resume if said requested file is not one of said selected files; if said requested file is one of said selected files, finding said encryption key in a table by matching a registered application program signature with said application program and selecting a registered encryption key associated with said registered application program signature; deciphering said requested file using said registered encryption key; loading said decrypted file into a portion of memory assigned to said application program.
15. The method of claim 14 wherein said step of intercepting a read request is performed via hooks into an operating environment of said computer system.
16. The method of claim 14 wherein said step of deciphering said requested file occurs transparently to said application program.
17. The method of claim 16 wherein said step of deciphering said requested file comprises providing said registered encryption key and said encrypted file to a decryption program running separately from said application program, said decryption program returning said decrypted file.
18. The method of claim 14 wherein said step of determining if said requested file is one of said selected files is performed by searching a portion of said requested file for an encryption signature.
19. The method of claim 14 wherein said table is created within a virtual device driver during installation of a registered application program.
20. A method of providing copy protection of images in a computer system comprising the steps of: encrypting selected images using an encryption key; intercepting a request to read an image from an application program; determining if said requested image is one of said selected images; allowing said request to resume if said requested image is not one of said selected images; if said requested image is one of said selected images, finding said encryption key in a table by matching a registered application program signature with said application program and selecting a registered encryption key associated with said registered application program signature; deciphering said requested image using said registered encryption key; loading said decrypted image into a portion of memory assigned to said application program; prohibiting copying of said decrypted image selected for protection from device memory.
21. The method of claim 20 wherein said step of encrypting selected images using an encryption key comprises the steps of: reading said encryption key and an application; recording said encryption key and an application signature which is a collection of information about a specific application; installing said application signature and said encryption key in a decryption table.
22. The method of claim 20 wherein said step of intercepting a read request is performed via hooks into an operation environment of said computer system.
23. The method of claim 20 wherein said step of determining if a requested image is one of said selected images is performed by examining a file's extension.
24. The method of claim 20 wherein said step of prohibiting copying of said decrypted image selected for protection from device memory comprises the steps of: intercepting transfer requests for said decrypted file data recognizable for display on a display means; determining a protected region of said device memory comprising said decrypted image data selected for protection; copying into a destination memory only data from those portions of said device memory not within said protected region.
25. The method of claim 24 wherein said step of intercepting transfer requests for said decrypted file data is performed by means of hooks into an operating environment of said computer system.
26. An article of manufacture comprising: a computer usable medium having computer readable program code embodied therein for providing copy protection, the computer readable program code in said article of manufacture comprising: computer readable program code configured to cause a computer to intercept requests for transfer of data from a source region to a destination region; computer readable program code configured to cause said computer to specify within said source region a protection region defining protected data; and computer readable program code configured to cause said computer to transfer data from said source region to said destination region, excluding said protection region.
27. The article of manufacture of claim 26 wherein said program code configured to cause a computer to intercept requests for transfer of data comprises computer readable program code configured to cause said computer to hook into an operating environment of said computer system.
28. The article of manufacture of claim 26 wherein said program code configured to cause said computer to specify a protection region further comprises: computer readable program code configured to cause said computer to process a callback function from an application program; computer readable program code configured to cause said computer to receive via said callback function an object specifying an individual region to be protected; and computer readable program code configured to cause said computer to form said protection region from said individual region.
29. The article of manufacture of claim 26 wherein said program code configured to cause said computer to specify a protection region further comprises: computer readable program code configured to cause said computer to process a plurality of callback functions from at least one application program; computer readable program code configured to cause said computer to receive via said callback functions a plurality of objects specifying a plurality of individual regions to be protected; and computer readable program code configured to cause said computer to form said protection region from said individual region.
30. The article of manufacture of claim 26 wherein said program code configured to cause said computer to transfer data from said source region to said destination region, excluding said protection region further comprises: computer readable program code configured to cause said computer to subtract said protection region from said destination region to create a first modified destination region; and computer readable program code configured to cause said computer to copy data from said source region into said first modified destination region.
31. The article of manufacture of claim 26 wherein said program code configured to cause said computer to transfer data from said source region to said destination region, excluding said protection region further comprises: computer readable program code configured to cause said computer to subtract said protection region from said source region to create a modified source region; and computer readable program code configured to cause said computer to copy data from said modified source region into said destination region.
32. The article of manufacture of claim 26 further comprising: computer readable program code configured to cause said computer to replace said destination region with said protection region to create a second modified destination region; and computer readable program code configured to cause said computer to write said substitute data into said second modified destination region.
33. The article of manufacture of claim 26 wherein said data comprises image data and said source region defines a portion of video adapter memory.
34. An article of manufacture comprising: a computer usable medium having computer readable program code embodied therein for protecting files within a computer system from misappropriation, the computer readable program code in said article of manufacture comprising: computer readable program code configured to cause a computer to encrypt files selected for protection; computer readable program code configured to cause said computer to decipher said encrypted files only for authorized applications; computer readable program code configured to cause said computer to prohibit copying of decrypted file data selected for protection from device memory, said prohibiting program code further comprising: computer readable program code configured to cause said computer to intercept data transfer requests; computer readable program code configured to cause said computer to determine a protected region of said device memory comprising said decrypted file data selected for protection; computer readable program code configured to cause said computer to copy into a destination memory only data from those portions of said device memory not within said protected region.
35. The article of manufacture of claim 34 further comprising computer readable program code configured to cause said computer to fill said protected region within said destination memory with alternate data.
36. The article of manufacture of claim 34 wherein said program code configured to cause said computer to intercept data transfer requests comprises computer readable program code configured to cause said computer to hook into an operating environment of said computer system.
37. The article of manufacture of claim 34 wherein said program code configured to cause said computer to determine said protected region of said device memory comprises: computer readable program code configured to cause said computer to process through a callback function from an application program; computer readable program code configured to cause said computer to receive via said callback function an object specifying an individual region to be protected; computer readable program code configured to cause said computer to form said protected region from said individual region.
38. The article of manufacture of claim 34 wherein said program code configured to cause said computer to determine said protected region of said device memory comprises: computer readable program code configured to cause said computer to process through a plurality of callback functions from at least one application program; computer readable program code configured to cause said computer to receive via said callback functions a plurality of objects specifying a plurality of individual regions to be protected; and computer readable program code configured to cause said computer to form said protected region from said individual regions.
39. An article of manufacture comprising: a computer usable medium having computer readable program code embodied therein for file protection for a computer system, the computer readable program code in said article of manufacture comprising: computer readable program code configured to cause a computer to encrypt selected files using an encryption key; computer readable program code configured to cause said computer to intercept a read request from an application program; computer readable program code configured to cause said computer to determine if a requested file is one of said selected files; if said requested file is not one of said selected files, computer readable program code configured to cause said computer to allow said read request to resume; if said requested file is one of said selected files, computer readable program code configured to cause said computer to find said encryption key in a table by matching a registered application program signature with said application program and selecting a registered encryption key associated with said registered application program signature; computer readable program code configured to cause said computer to decipher said requested file using said registered encryption key; computer readable program code configured to cause said computer to load said decrypted file into a portion of memory assigned to said application program.
40. The article of manufacture of claim 39 wherein said program code configured to cause said computer to intercept a read request comprises computer readable program code configured to cause said computer to hook into an operating environment of said computer system.
41. The article of manufacture of claim 39 wherein said program code configured to cause said computer to decipher said requested file occurs transparently to said application program.
42. The article of manufacture of claim 41 wherein said program code configured to cause said computer to decipher said requested file comprises computer readable program code configured to cause said computer to provide said registered encryption key and said encrypted file to a decryption program running separately from said application program, said decryption program returning said decrypted file.
43. The article of manufacture of claim 39 wherein said program code configured to cause said computer to determine if said requested file is one of said selected files comprises computer readable program code configured to cause said computer to search a portion of said requested file for an encryption signature.
44. The article of manufacture of claim 39 wherein said table is created within a virtual device driver during installation of a registered application program.
45. An article of manufacture comprising: a computer usable medium having computer readable program code embodied therein for providing copy protection of images in a computer system, the computer readable program code in said article of manufacture comprising: computer readable program code configured to cause a computer to encrypt selected images using an encryption key; computer readable program code configured to cause said computer to intercept a request to read an image from an application program; computer readable program code configured to cause said computer to determine if said requested image is one of said selected images; computer readable program code configured to cause said computer to allow said request to resume if said requested image is not one of said selected images; if said requested image is one of said selected images, computer readable program code configured to cause said computer to finding said encryption key in a table by matching a registered application program signature with said application program and selecting a registered encryption key associated with said registered application program signature; computer readable program code configured to cause said computer to decipher said requested image using said registered encryption key; computer readable program code configured to cause said computer to load said decrypted image into a portion of memory assigned to said application program; computer readable program code configured to cause said computer to prohibit copying of said decrypted image selected for protection from device memory.
46. The article of manufacture of claim 45 wherein said program code configured to cause a computer to encrypt selected images using an encryption key further comprises: computer readable program code configured to cause said computer to read said encryption key and an application; computer readable program code configured to cause said computer to record said encryption key and an application signature which is a collection of information about a specific application; computer readable program code configured to cause said computer to install said application signature and said encryption key in a decryption table.
47. The article of manufacture of claim 45 wherein said computer readable program code configured to cause said computer to intercept a read request comprises computer readable program code configured to cause said computer to hook into an operation environment of said computer system.
48. The article of manufacture of claim 45 wherein said computer readable program code configured to cause said computer to determine if a requested image is one of said selected images comprises computer readable program code configured to cause said computer to examine a file's extension.
49. The article of manufacture of claim 45 wherein said program code configured to cause said computer to prohibit copying of said decrypted image selected for protection from device memory comprises: computer readable program code configured to cause said computer to intercept transfer requests for said decrypted file data recognizable for display on a display means; computer readable program code configured to cause said computer to determine a protected region of said device memory comprising said decrypted image data selected for protection; computer readable program code configured to cause said computer to copy into a destination memory only data from those portions of said device memory not within said protected region.
50. The article of manufacture of claim 49 wherein said program code configured to cause said computer to intercept transfer requests for said decrypted file data comprises computer readable program code configured to cause said computer to hook into an operating environment of said computer system.
51. An article of manufacture comprising: a computer usable medium having computer readable program code embodied therein for providing copy protection in a computer system, the computer readable program code in said article of manufacture comprising: computer readable program code configured to cause a computer to intercept requests for transfer of data that is displayed on a display means from a source region to a destination region; computer readable program code configured to cause said computer to specify within said source region a protection region defining protected data; and computer readable program code configured to cause said computer to transfer data from said source region to said destination region, excluding said protection region.
52. The article of manufacture of claim 51 wherein said program code configured to cause a computer to intercept requests for transfer of data comprises computer readable program code configured to cause said computer to hook into an operating environment of said computer system.
53. The article of manufacture of claim 51 wherein said program code configured to cause said computer to specify a protection region comprises: computer readable program code configured to cause said computer to process a callback function from an application program; computer readable program code configured to cause said computer to receive via said callback function an object specifying an individual region to be protected; and computer readable program code configured to cause said computer to form said protection region from said individual region.
54. The article of manufacture of claim 51 wherein said program code configured to cause said computer to specify a protection region comprises the steps of: computer readable program code configured to cause said computer to process a plurality of callback functions from at least one application program; computer readable program code configured to cause said computer to receive via said callback functions a plurality of objects specifying a plurality of individual regions to be protected; and computer readable program code configured to cause said computer to form said protection region from said individual regions.
55. The article of manufacture of claim 51 wherein said program code configured to cause said computer to transfer data from said source region to said destination region, excluding said protection region, comprises: computer readable program code configured to cause said computer to subtract said protection region from said destination region to create a first modified destination region; and computer readable program code configured to cause said computer to copy data from said source region into said first modified destination region.
56. The article of manufacture of claim 51 wherein said program code configured to cause said computer to transfer data from said source region to said destination region, excluding said protection region, comprises: computer readable program code configured to cause said computer to subtract said protection region from said source region to create a modified source region; and computer readable program code configured to cause said computer to copy data from said modified source region into said destination region.
57. The article of manufacture of claim 51 further comprising: computer readable program code configured to cause said computer to replace said destination region with said protection region to create a second modified destination region; and computer readable program code configured to cause said computer to write said substitute data into said second modified destination region.
58. The article of manufacture of claim 51 wherein said data comprises image data and said source region defines a portion of video adapter memory.
Patent Citations (7)
Non-Patent Literature (3)
- Farrow, R. "Unix System Security", 1991, pp. 26-28.
- "Microsoft Windows Software Development Kit", Programmer's Reference, vol. 2: Functions, 1991, pp. 535-539, 625,626, 894-899, 956-958.
- "Programming Windows 3.1", by Charles Petzold, 1992, pp. 175-193, 907-929.