AU2013200551B2 - System and method for authenticating a gaming device - Google Patents

Abstract

SYSTEM AND METHOD FOR AUTHENTICATING A GAMING DEVICE A method for securing content to be used by a device (200) is provided. The method comprises preparing and encrypted image by encrypting at least a portion of said content such that said portion can be recovered by decrypting said encrypted image using a key; storing said encrypted image on said device and obtaining information unique to said device. The method further comprises generating a signature using said information unique to said device to bind said encrypted image to said device, said signature encrypting said key such that said key is recoverable from said signature using said information unique to said device; and storing said signature on said device to enable said device to recover said key from said signature by determining said information unique to said device and providing said information unique to said device as an input to a signature verification function, wherein an output of said signature verification function corresponds to said key thereby enabling said device to decrypt said encrypted image to obtain said portion.

Description

-1 SYSTEM AND METHOD FOR AUTHENTICATING A GAMING DEVICE This application is a divisional application of Australian Patent Application No. 2007276673, a national phase entry of International Application No. PCT/CA2007/001264, which ultimately claims priority from US Patent Application Nos. 60/831,472 and 60/885,073. Australian Patent Application No. 2007276673, International Patent Application No. PCT/CA2007/001264 and US Patent Application Nos. 60.831,472 and 60/885,073 are incorporated herein by reference in their entirety. FIELD OF THE INVENTION [00011 The present invention relates to systems and methods for authenticating data stored on a device and has particular utility in authenticating such content at run time. DESCRIPTION OF THE PRIOR ART 100021 Companies that develop, manufacture and sell personal computer (PC) based devices that run software programs and/or receive, play and/or distribute various types of multimedia content, but due to the physical limitations of the device and/or inability to force users to employ strong passwords at boot-up, wake-up etc., can face significant security challenges not only during use, but also during the device's entire lifecycle. [00031 In many cases, the devices are destined for a consumer market where the devices become susceptible to hacking from various potential attackers both expert and unsophisticated. Companies are generally very concerned with security but it can be difficult to blame adequate security with usability and cost requirements. For example, high security measures during use that are not transparent to the user can be detrimental to usability. Also, high security during the manufacturing stage, e.g., keeping all manufacturing in-house, can be detrimental to the overall cost of producing the product. [00041 In general, there are three stages in the life of the device in which security should be of greatest concern: i) the manufacturing process; ii) the general operation of the device by its owner; and iii) the maintenance and repair of the device by technicians. It shall be noted that the user of the device may not necessarily be the owner of the content being handled by the device, e.g., a music file played on a satellite radio player. [00051 Often, the production of the device is handled by one or more third parties. For example, a motherboard/microprocessor module designed by the company is manufactured and - la pre-programmed by a third party supplier. The end-product produced using the motherboard may itself be assembled at the company's facility or at the facility of another third part contractor. The assembly process is typically where operating systems, software applications and configuration data are programmed into the device before final testing and are vulnerable to cloning and other security breaches.

1 [00061 Data that is particularly sensitive is content security middleware that is used to 2 enforce content security policies, e.g., digital rights management (DRM), at a later time, 3 when the device is in operation. The security middleware and the device itself are vulnerable 4 at all times, but especially so while the device is being manufactured, while it is deployed but 5 turned off, and while it is being serviced by a knowledgeable technician. In many cases, the 6 content security middleware can be changed or altered during these times and thus the 7 safeguards protecting the content are vulnerable to being circumvented which places the 8 content and/or software applications of the device at a security risk. 9 [0007] There exists security tools and applications that attempt to protect a device when 10 the device is booting up, and that address user authentication and disk encryption, however, 11 these tools are typically not suitable for the applications described above due to their reliance 12 on user-interaction at certain important points in the authentication process. Moreover, many 13 of these security tools require or rely on the presence of a Smart Card, which is often too 14 costly of a component for companies to include with the-device. Therefore, as noted above, 15 security and usability can be competing objectives. An important factor in the success of 16 high-volume consumer electronic devices is that they are easy to use.. As such, vendors of 17 these devices wish to have security measures that are adopted by the device be transparent to 18 the user. 19 10008] Implementation issues have traditionally been a concern to companies, and, the 20 protection of a device while booting up, encrypting file systems and implementing DRM 21 policy engines to protect the device and the content used by the device are known. However, 22 the established techniques often rely on the use of multiple complex software layers that need 23 to co-exist and interoperate at multiple layers of the device, BIOS, O/S Kernel, O/S, drivers 24 and application layers. The operation at multiple layers can be difficult to implement, is 25 prone to the introduction of errors into the operation of the device, and can require a' 26 significant amount of additional code. Moreover, it is of paramount importance to companies 27 that utilize these security measures that should a single device be compromised, the entire 28 system is not susceptible to failure. 29 [0009] The above disadvantages are particularly prevalent in the gaming industry. 30 Gaming machines such as slot machines include hardware and software for running the 31 games, determining winners and controlling payouts. The software and hardware are prone -2- -3 to attacks whereby the software or hardware is swapped or modified to operate in a manner that is favourable to the attacker. As such, it is paramount that the integrity of the machine be maintained and the operation thereof be protected. [0010] A need exists to obviate or mitigate the above disadvantages. SUMMARY OF THE INVENTION [0011] A system and method is provided for securing content included in a device and authenticating the content at run time. [0011a] In one aspect, a method is provided for securing content to be used by a device comprising: preparing an encrypted image by encrypting at least a portion of said content such that said portion can be recovered by decrypting said encrypted image using a key; storing said encrypted image on said device; obtaining information unique to said device; generating a signature using said information unique to said device to bind said encrypted image to said device, said signature encrypting said key such that said key is recoverable from said signature using said information unique to said device; and storing said signature on said device to enable said device to recover said key from said signature by determining said information unique to said device and providing said information unique to said device as an input to a signature verification function, wherein an output of said signature verification function corresponds to said key thereby enabling said device to decrypt said encrypted image to obtain said portion. [0011b] In another aspect, a method is provided for authenticating content to be used for operating a device, the method comprising: obtaining a signature stored on said device, said signature encrypting a key that can be recovered therefrom; obtaining information unique to said device; recovering said key from said first signature component by providing said information unique to said device as an input to a signature verification function, wherein said key is an output to said signature verification function; using said key to decrypt an encrypted image of at least a portion of said content to recover said portion, said encrypted image having been stored on said device; and using said portion in operating said device, wherein if said portion is operable, said content is implicitly authenticated. [0011c] In yet another aspect, a computer readable medium comprising computer executable instructions for performing the method according to any one of the above aspects is provided.

-3a [0011d] In yet another aspect, a device comprising a processor and a memory, said processor operable to perform the method according to any one of the above aspects is provided. Paragraphs [0012]-[0014] deleted. [[Next Page is page 4]] -4 1 [0015] In yet another aspect, a method for authenticating content to be used by a 2 device is provided comprising obtaining a signature comprising an encrypted first portion of 3 the content and a plaintext second portion of the content as components thereof; utilizing the 4 signature to recover a plaintext first portion from the encrypted first portion; and 5 authenticating the content according to the plaintext first portion recovered from the 6 signature. 7 [0016] In yet another aspect, a method for securing content to be used by a device is 8 provided comprising designating a plurality of portions of the content; storing a first value 9 on the device; generating a first signature on a first portion of the content, the first signature 0 comprising a component which encrypts a second value such that the second value can be 1 recovered using the first value; generating a second signature on a second portion of the 2 content, the second signature comprising a component which encrypts a third value such that 3 the third value can be recovered using the second value; and if more than two portions 4 generating other signatures that each include a component which encrypts a next value to be 5 used by a next portion such that the next value can be recovered using a previous value 6 recovered from a signature on a previous portion; wherein the first value can be used to 7 recover the second value from the first signature, the second value can be used to recover the 8 third value from the second signature and, if necessary, the next values are recoverable using 9 the previous values, such that a final value recovered from a respective signature on a last of 0 the portions can be compared with the first value to authenticate the plurality of portions !1 simultaneously. 22 [0017] In yet another aspect, a method for authenticating content to be used by a device 23 is provided comprising obtaining a first value stored on the device; obtaining a first signature 24 on a first of a plurality of portions of the content, the first signature comprising a component 25 which encrypts a second value; recovering the second value using the first value; obtaining a 26 second signature on a second of the plurality of portions of the content, the second signature 27 comprising a component which encrypts a third value; recovering the third value using the 28 second value recovered from the first signature; if more than two portions, obtaining other 29 signatures that each include a component which encrypts a next value and recovering the next I value using a previous value recovered from a signature on a previous portion; and 2 comparing a final value recovered from a signature on a last of the plurality of portions with 3 the first value to authenticate all the plurality of portions simultaneously. 4 [00181 In yet another aspect, a method for downloading a new module for content to be 5 used by a device is provided, the method comprising obtaining a signature on an entry 6 module for a component of the content, the component comprising a plurality of modules, 7 each comprising a signature, one of the plurality of modules being the entry module and one 8 of the plurality of modules being an end module, the signature on the entry module 9 comprising a signature component which encrypts an intermediate value such that the 10 intermediate value can be recovered using a value stored on the device, the signature on the 11 end module comprising a signature component which encrypts a next value such that the next 12 value can be recovered using the intermediate value, and if morelthan=two modules exist in 13 addition to the entry and end modules, other modules of the component having a signature 14 which comprises a signature component which encrypts the intermediate value such that the 15 intermediate value can be recovered using the intermediate value recovered from a respective 16 signature on a previous module; recovering the intermediate value from the signature on the 17 entry module; obtaining a signature on the new module, the signature on the new module 18 comprising a signature component which encrypts the intermediate value such that the 19 intermediate value can be recovered using the intermediate value; using the intermediate 20 value recovered from the signature on the entry module to recover the intermediate value 21 from the signature on the new module; obtaining the signature on the end module and using 22 the intermediate value recovered from the signature on the new module to obtain the next 23 value; using the next value as a key for a keyed hash function and applying the keyed bash 24 function to another component of the content to obtain an authentication code; and comparing 25 the authentication code to a stored authentication code previously generated on the another 26 component to authenticate the new module and the content. 27 100191 In yet another aspect, a method for securing data on a gaming machine is 28 provided, the method comprising encrypting a portion of the data and storing an ECPV 29 signature on the gaming machine, wherein verification of the ECPV signature enables the 30 portion to be decrypted and used by the gaming machine. -5- 1 100201 In yet another aspect, a method for securing data to be used by a device is 2 provided, the method comprising signing each of a plurality of components of the data to 3 generate a plurality of ECPV signatures having a visible portion and a hidden portion, 4 wherein the visible portion is the respective component of the data, and the hidden portion is 5 a value that, when recovered, is used to recover a respective value in the next signature, and 6 wherein a final value recovered from the respective signature on a final one of the plurality of 7 components may be compared to an input value used to recover the respective value from a 8 first one of the plurality of components to authenticate the data. 9 100211 The above methods are particularly suitable where the device is a. gaming 10 machine. 11 BRIEF DESCRIPTION OF THE DRAWINGS 12 [00221 An embodiment of the invention will now be described by way of example only 13 with reference to the appended drawings wherein: 14 10023] Figure 1 is a perspective view of a gaming machine including a protected 15 hardware board. 16 100241 Figure 2 is a schematic diagram of a secure binding system including the 17 hardware board of Figure 1. 18 100251 Figure 3 is a flow diagram illustrating a secure binding procedure. 19 100261 Figure 4 is a flow diagram illustrating a BIOS loading procedure. 20 100271 Figure 5 is a flow diagram illustrating the generation of secure boot credentials 21 using the Elliptic Curve Pinstov-Vanstone Signature Scheme. 22 10028] Figure 6 is a flow diagram illustrating the verification of secure boot credentials 23 using the Elliptic Curve Pinstov-Vanstone Signature Scheme. 24 100291 Figure 7 is a flow diagram illustrating a user authentication sequence. 25 [00301 Figure 8 is a flow diagram illustrating a user PIN entry process. -6- 1 100311 Figure 9a is schematic block diagram of an unbound hardware board. 2 10032] Figure 9b is a schematic block diagram of a bound hardware board. 3 100331 Figure 10 is a flow diagram illustrating a service technician authentication 4 sequence. 5 100341 Figure 11 is a flow diagram illustrating a secure software upgrade process. 6 100351 Figure 12 is a flow diagram illustrating a secure boot authentication process. 7 100361 Figure 13 is a schematic block diagram of a system layout for an authenticated 8 gaming device. 9 10037] Figure 14 is a flow diagram illustrating verification of the hard disk of Figure 13 10 using the Elliptic Curve Pinstov-Vanstone Signature Scheme. 11 100381 Figure 15 is a schematic block diagram of another system layout for an 12 authenticated gaming device. 13 10039] Figure 16 is a schematic block diagram of yet another system layout for an 14 authenticated gaming device. 15 [00401 Figure 17 is a schematic diagram showing Elliptic Curve Pinstov-Vanstone 16 signature generation for the embodiment of Figure 13. 17 100411 Figure 18 is a schematic diagram of a gaming machine having a protected 18 hardware board and a network connection for downloading a game file. 19 100421 Figure 19 is a schematic diagram of the hardware board of Figure 18 showing a 20 chained signature verification procedure. 21 [00431 Figure 20 is a schematic diagram of the hardware board of Figure 19 showing a 22 verification procedure when downloading a new game file. 23 10044] Figures 21(a) - 21(b) are flow diagrams illustrating signature generation for the 24 game component modules of Figure 19. -7- 1 10045) Figure 22 is a flow diagram illustrating signature generation for the jurisdiction 2 module of Figure 19. 3 [0046 Figures 23(a) - 23(b) are flow diagrams illustrating signature generation for the 4 platform component modules of Figure 19. 5 10047] Figure 24 is a flow diagram illustrating signature verification for the game 6 component modules. 7 [00481 Figure 25 is a flow diagram illustrating signature verification for the jurisdiction 8 component module and use of an output therefrom for verifying a keyed hash. 9 [00491 Figure 26 is a flow diagram illustrating signature verification for the platform 10 component modules. 11 10050] Figure 27 is a flow diagram illustrating signature verification for a newly 12 downloaded game file. 13 100511 Figure 28 is a flow diagram showing a chained signature verification procedure 14 for an arbitrary file system. 15 DETAILED DESCRIPTION OF THE INVENTION 16 100521 Referring to Figure 1, a gaming machine 10 includes a display 11 for displaying 17 game play using an application 15. The machine 10 also includes an input 13 for interacting 18 with the game play according to what is displayed. A hardware (H/W) board 12 controls the 19 game play on the display 11 according to user interaction with the input 13. 20 100531 In order to protect valuable content, such as game code on the H/W board 12, the 21 content is bound to the specific H/W board 12 at the time that it is manufactured. 22 10054] An unbound H/W board 12 is shown in Figure 9a. The H/W board 12 has an a 23 basic-input output system (BIOS) 14 that is initially flashed with an unbound version of 24 customized BIOS code (UBI) 16 to prevent the theft of unbound boards that are used to 25 execute arbitrary code, especially during a repair scenario. The H/W board 12 stores a pre 26 computed hash (PBBAH) of a pre-boot binding application (PBBA) in region 17. The PBBA 27 is pre-stored in a pre-boot section 23 of a hard disk drive (HDD) 20. The dashed lines in -8- I Figure 9a delineate the portions of the H/W board 12 that are re-written during the binding 2 process that will be explained in detail below. 3 [00551 The HDD 20 is split into three fundamental sections, namely the pre-boot section 4 23, an application partition 27 (e.g. Drive C) and a data partition 34 (e.g. Drive D). The data 5 partition 34 includes a data portion 36 for storing data. The pre-boot section 23 stores the 6 PBBA in region 25. The PBBA handles the binding of the H/W board 12. The application 7 partition 27 stores H/W testing operating system (OS) and system files 28 and H/W testing 8 applications 32. The HDD 20 also includes a plaintext master boot record (MBR) 22. 9 Preferably, the MBR 22 is not standard to prevent the HDD 20 from executing in any 10 standard PC platform with a standard BIOS image 14. The MBR 22 includes an unaltered 11 partition table 21 since the OS typically requires that this table 21 be in a recognizable format 12 when it reads it from the HDD 20. As such, the partition table 21 is not encrypted. The boot 13 loader (not shown) that resides in the MBR 22 reads the partition table 21 and jumps to the 14 first bootable location on the HDD 20. The boot loader can be modified to prevent it from 15 being executed by a standard BIOS image 14. 16 100561 Separation of the three sections helps to speed up the binding operations since the 17 sections 23 and 27 will take up much less space on the HDD 20 than the data partition 34 and 18 thus generating an image of the sections 23 and 27 is generally faster than generating an 19 image of the entire HDD 20. The separation of the sections 23, 27 and 34 may also help to 20 simplify data recovery operations since data can be extracted directly from the data partition 21 34 rather than having the possibility that the data 36 is mixed with the applications 32 in the 22 application partition 27. 23 100571 A bound H/W board 12 is shown in Figure 9b wherein modified elements are 24 given like numerals to Figure 9a with the suffix "a". After the binding process, the H/W 25 board 12 will contain a bound BIOS image (BB)]. 4a and a fully protected HDD 20a. 26 100581 The bound HDD 20a includes an unencrypted MBR 22 and partition table 21 as in 27 Figure 9a; and an encrypted pre-boot section 23'a, which includes an encrypted secure boot 28 authenticator (SBA), an elliptic curve public key (ECPK) and an image key file (11(F). 29 Preferably, the encrypted SBA is stored in a known (and fixed) location on all systems so that 30 the customized BIOS code 1 6a knows where to find it. The ECPK and the IKF are used by -9- I the SBA to verify the BIOS credentials and execute the OS. The IKF is a file that stores the 2 image key (IK) that is recovered during the secure boot process as will be explained below. 3 The HDD 20a also includes an unencrypted pre-boot section 23b that stores recovery PBBA 4 code in a known and fixed location 25a. The RPBBA is plaintext code that allows the system 5 to rebind the bound HDD image 24a to a new hardware board. There is no need to protect 6 the RPBBA as it will not contain any sensitive information that could jeopardize the system. 7 [0059] The application partition 27a is encrypted when the H/W board 12 is bound and 8 contains the OS and system files 28a, the applications 32a and a region 31 containing a logon 9 agent (LA) and a user boot PIN mask (UBPM) used to validate a personal identification 10 number (PIN) entered by a user. In one embodiment, the LA is referred to as GINAC, which 11 is a customized version of an existing graphical identification and authentication DLL 12 (GINA). The entire application partition 27a is encrypted with the IK. 13 100601 It will be appreciated that if the data partition 36 is already protected by another 14 mechanism, e.g., digital rights management (DRM), the data partition 36 may not be 15 encrypted and may thus be plaintext. However, in this example, full disk encryption is 16 utilized such that only the MBR 22 and pre-boot section 23b are in plaintext. 17 100611 The BBI 14a includes a bound version of the customized BIOS code 16a and 18 region 17a is modified such that it contains a number of items in addition to the PBBAH. 19 These additional items include unique authentication credentials, in this embodiment referred 20 to as secure boot credentials (SBCs) that are added to the BIOS image 14 firmware image at 21 the manufacturing stage; a secure boot authenticator decrypt key (SBAK) that is used to 22 encrypt and decrypt the SBA; a hash of the SBA (SBAH); and a hash of the RPBBA 23 (RPBBAH). 24 [0062] The image 24a is cryptographically bound to the BIOS image 14a and other 25 hardware components on the H/W board 12 by adding the SBC, preferably to the BIOS 26 firmware image, during the manufacturing process. It is desirable to have binding occur after 27 hardware testing has occurred, since, in a practical sense, there is no need to secure a broken 28 or otherwise dysfunctional H/W board 12. 29 100631 As shown in Figure 2, the H/W board 12 is bound using the interaction of several 30 components preferably while it is in the testing jig. The binding is performed directly by a -10- 1 hardware binding machine (HBM) 50 that is preferably connected directly to the H/W board 2 12 via a universal serial bus (USB) connection 52. The binding process is accomplished 3 indirectly using a key injection system (KIS) 70 that communicates with the HBM 50 via a 4 secure network connection 62. 5 [0064] The KIS 70 comprises a controller 72 connected to a server 74 via another secure 6 network connection 76, and key agent software 75 included in a hardware binding application 7 (HBA) on the HBM 50. The key agent (KA) 75 establishes the secure connection 62 8 between the HBM 50 and the server 74. 9 100651 The hardware binding application (HBA) 52 performs the binding operation and 10 uses the KA 75 to establish a secure connection 62 with the controller 72. Typically, the 11 HBM 50 includes a display 54 for providing an application program interface (API) 56 to 12 enable a user to operate the HBM 50, e.g., using a laptop computer. In a practical sense, it is 13 beneficial to avoid running other CPU-intensive applications during the binding procedure. 14 The HBM 50 also stores an encrypted copy 53 of the image 24 in a data storage device 55. In 15 one embodiment, the image 24 is encrypted with a key know only to the server 74. The HBA 16 52 obtains the key when securely connected to the server 74 and will re-encrypt the image 24 17 before sending to the H/W board 12. The HBM 50 is also responsible for returning the 18 results of the binding operation to the server 74 so that the server 74 can return logging data 19 to the controller. Preferably, there are two types of HBMs, one used by manufacturers for 20 performing the binding procedure, and one used by technicians for repairing and upgrading 21 the H/W board 12. The key shared between the server 74 and each manufacturer will 22 preferably be the same and each technician will preferably use a different key. 23 [00661 The KIS 70 is a system that is used to remotely monitor device registration and to 24 meter the injection of unique and immutable information into the device. A complete 25 description of the KIS 70 is provided in co-pending U.S. patent application No. 11/450,418 26 filed on June 12, 2006, the contents of which are incorporated herein by reference. In the 27 present example, the controller 72 is a computer system that is remote to the 28 manufacturer/testing facility and is preferably located at the company that produces the 29 device and the server 74 is located at an outside manufacturer that has been contracted by the 30 producer to manufacture, test and bind the H/W board 12. The producer may be a gaming - 11 - I company that produces and sells gaming machines 10 but contracts the manufacture of at 2 least the H/W module to a third party. 3 100671 The server 74 and the HBM 50 may or may not be at the same location and, if 4 they are within the same physical location, the secure connection 62 may be established over 5 a local network. As will be described in greater detail below, the HBM 50 is used to not only 6 for the binding process but also used by technicians for repairs, maintenance and upgrades. 7 As such, the HBM 50 may be connected to the H/W board 12 while it is in a gaming machine 8 10 on location at, e.g., a casino. Therefore, the relative physical locations of the server 74 9 and the HBM 50 can change so long as the secure connection 62. can be established enabling 10 communication between the HBM 50 and the server 74. 11 100681 The controller 72 comprises a hardware security module (HSM) 78, which is a 12 protected device used by the controller 72 to perform cryptographically secure operations 13 such as encryption, decryption and signing. A set of system security vectors (SSVs) is stored 14 in a data storage device 83. Each SSV contains a set of values that will be unique to each 15 bound H/W board 12. The set of values includes an SSV identifier (SSVID), a master boot 16 PIN (MBP), an initial user PIN (IUP), the image key (IK) for the particular board 12, a 17 system unlock code (SUC), and the SBAK. With the exception of the SSVID, all of the 18 values are randomly generated. The SSVID is an integer value used to identify the SSV, 19 which preferably increments by one for each SSV that is generated by the controller 72. The 20 MBP is the PIN that is used to access the module when the user has forgotten their PIN. The 21 IUP is the PIN that the user enters when they first power up the system if a pass-code 22 protection (PCP) option has been enabled prior to being shipped (or other user-password 23 authentication scheme). If PCP has been disabled, the IUP is redundant as the user will be 24 asked to enter a new PIN as discussed in greater detail below. As noted above, the IK is used 25 to protect the image 24a, the SUC is used to protect the 1K itself, and the SBAK is the key 26 used by the BIOS 14a to protect the SBA process. 27 100691 Blocks of SSVs are pre-computed by the controller 72 and sent securely to the 28 server 74 on an as-needed basis. The server 74 caches a sufficient (configurable) number of 29 SSVs to ensure that the server 74 does not need to communicate with the controller 72 during 30 a production run, and to ensure that the server 74 does not run out of data during a run 31 according to the principles described in co-pending application no. 11/450,418. The -12- 1 controller 72 can periodically poll the server 74 to determine if its cache of SSVs is low and 2 automatically top-up the cache as necessary. The controller 72 can also gather logging 3 information from the server 74 concerning the binding process. The controller 72 also 4 comprises a graphical user interface (GUI) 81 to enable a user to interact with the controller 5 72. 6 [00701 In one embodiment, the controller 72 is a Win32-based Windows service that 7 executes continuously on a PC-based server machine, which contains the HSM and secure 8 firmware. Requests made over the secure connection 76 can be established using a secure 9 socket connection (SSL) wherein GUI 81 is an Apache Tomcat Java Servlet GUI. The 10 interface allows for remote viewing of logging data from servers 74, as well as enabling an 11 operator to set configuration settings in the KIS 70. The controller 72 also preferably 12 includes provisions for loading keying data into the database 83 for later (or immediate) 13 delivery to the server 74. 14 100711 The server 74 comprises an HSM 84 that stores a credit pool 86 which dictates 15 how many MBPs the server 74 has cached at any given time, an elliptic curve private key 16 (ECPRK) 80 and a corresponding elliptic curve public key (ECPUK) 82. The server 74 17 stores the cache of SSVs in a data storage device 88. In one embodiment, the server 74 is a 18 Linux-based daemon application that executes continuously on a PC-based server machine 19 containing the HSM 84 and secure firmware. The server 74 receives SSL requests from the 20 controller 72 to receive keying data and receives requests from the key agents 75 to securely 21 deliver keying data for writing to devices. The server 74 contains access control measures to 22 prevent unauthorized access to the system, e.g. a password or PIN code, but should also 23 require minimal operator interaction once the system is deployed. The server 74 handles two 24 types of requests, namely: 1) Requests from both types of HBMs to decrypt a new SSV from 25 the cache 88; and 2) Requests from technician HBMs to retrieve an old SVV from the 26 controller's database 83. 27 10072] A flow diagram illustrating the steps in the binding process is shown in Figure 3. 28 As described above, the controller 72 performs a pre-production poll with the server 74 and 29 top-up of SSVs, to ensure that the server 74 has a sufficient quantity of SSVs for that 30 particular run. The controller 74 also performs post production log retrievals to gather - 13- I information concerning the binding process. The log reporting procedures used by the KIS 2 70 are described in detail in co-pending application no. 11/450,418. 3 100731 Following the H/W testing process, preferably, the H/W board first gathers H/W 4 information at step I that is used to further bind the pre-boot authentication process to the 5 specific hardware such that the image 24 can only run on the hardware on which it was 6 originally installed. This helps to prevent a legitimate image 24 from running on mimicked 7 or cloned H/W and vice versa. The H/W information may include any combination of 8 hardware specific, verifiable identifiers such as the HDD serial number, the H/W board serial 9 number, the media access control (MAC) addresses of the network interface cards (NICs), the 10 BIOS serial number etc. Collectively, the H/W information is herein referred to as a HWSN. 11 The H/W information can be combined and/or related to each other in any suitable manner to 12 create the HWSN. For example, the identifiers can be concatenated and the resultant value 13 hashed to produce the HWSN. 14 [00741 At step 2, the H/W board 12 connects to the HBM 50 via the USB connection 52 15 (or other direct-connect interface such as a dedicated cross-over Ethernet (COE) connection) 16 and sends the H/W information to the HBM 50. The HBA 52 then establishes the secure 17 connection 62 with the server 74 at step 3 using the key agent 75 (e.g. SSL) and sends a 18 ciedentials request to the server 74 along with the H/W information at step 4. At step 5 the 19 server 74 generates a number of values that are to be sent back to the HBA 52 over the 20 connection 62 at step 6. 21 [00751 At step 5 the server 74 first retrieves an SSV from the cache 88. From the SSV, 22 the MBP is obtained and the server 74 calculates a hash of the MBP to create a master boot 23 pin hash (MBPH). The server 74 also obtains the IUP from the SSV and calculates a mask of 24 the IUP (IUPM). The server 74 also calculates the SBC using the HWSN and the SUC 25 recovered from the SSV. Referring also to Figure 5, the SUC is used by the server to 26 calculate the SBC for the particular H/W board 12 that is undergoing the binding process. In 27 the server's HSM 84, the SUC, the private key ECPRK and the hardware information HWSN 28 are input into an Elliptic Curve Pinstov-Vanstone Signature (ECPVS) signing function. 29 100761 A first signature component e is computed by encrypting the SUC with the private 30 key ECPRK using a transformation T. An intermediate signature component d is computed -14- I by hashing the first signature component e, an identity of the server 74, and the HWSN; and a 2 second signature component s is then computed using d. An ECPVS signature having 3 components (e, s, HWSN) is generated which corresponds to the SBC. 4 [06771 At step 6, the SBC, SUC, IK, SBAK, MBPH and the 1UPM are sent over 5 connection 62 to the HBA 52 and the server 74 and key agent 75 are then disconnected from 6 each other at step 7. At step 8,/the HBA 52 will first obtain and decrypt a stored copy 53 of 7 the image 24 and obtain and decrypt a copy of the SBA using keys previously supplied by the 8 server 74. The HBA 52 will then re-encrypt the image 24 (and MBPH and 1UPM) with the 9 IK, and re-encrypt the SBA with the SBAK. The HBA 52 then generates the image 24a of 10 both the encrypted SBA and the encrypted image 24. Finally, the HBA 52 then generates a 11 BBI 16a that contains the newly created SBCs and the SBAK. At step 9, the HBM 50 sends 12 the encrypted image 24a and the BBI 14a to the H/W board 12. The PBBA already executing 13 on the H/W board 12 at step 10 flashes the BIOS 14 with the BBI 14a and writes the image 14 24a directly to the HDD 20. Finally, the ECPUK is compiled with and is thus part of the 15 SBA code. 16 [0078] At step 11, the PBBA 26 returns a binding status message to the HBM 50 and the 17 HBM 50 and the H/W board 12 are disconnected from each other at step 12. The HBM 50 18 then uses the key agent 75 to re-establish a connection with the server 74 at step 13 and 19 prepare and send a log report pertaining to the binding operation (e.g. including SSVID) to 20 the server 74 at step 14. The server 74 will then store the log report at step 15 for reporting to 21 the controller 72, preferably at a later time (i.e. post production), and the server 74 and the 22 key agent 75 are then disconnected from each other at step 16. The controller 72 23 communicates with database 83 to store all SSVs that have been sent to the server 74. When 24 log reports are retrieved from the server 74 (e.g. by polling), the SSVID is recovered from the 25 report to correlate the logging data back to a specific SSV in the database 83. The logs can 26 also be adapted to include other information deemed necessary for auditing purposes, e.g., the 27 HWSN provided in the request and the SBC generated in step 5. 28 [0079] It shall be noted that since the above described binding procedure involves the 29 collection and use of specific information from various parts on the H/W board 12, 30 preferably, binding should occur after all components have been assembled. As a further - 15 - I preference, the BIOS 14 should be programmed with a standard unbound BIOS image (UBI) 2 after the H/W board 12 is populated and before hardware testing. 3 100801 When the unbound H/W board is booted, the UBI will recognize itself as being 4 unbound and attempt to execute the PBBA code from a know location on the HDD. The UBI 5 14 first calculates a hash of a known portion of the HDD that should include the PBBA code 6 (if bound) and compares this with the PBBAH stored in the BIOS. If the hashes do not match 7 the UBI will not allow the PBBA to execute. 8 [0081] Referring now to Figure 4, the secure boot procedure begins at step 100 following 9 the normal power-up self tests (POST). The BBI code 16a calculates a hash of the first N 10 blocks (where N is the minimum byte size of the {PBBA, ESBA)) of the HDD 20 starting at 11 the encrypted pre-boot sector 23a at step 101. The hash calculated at step 101 is compared to 12 the PBBAH stored in region 17a at step 102. If the hash is equivalent to the stored PBBAH 13 then the BBI 14a determines that the binding should take place, namely that the HDD image 14 24 is that of the PBBA and then executes the PBBA at step 103. If the hash does not match 15 the PBBAH, BBI 14a then determines if the hash matches the SBAH stored in region 17a at 16 step 104. If the hash is equivalent to the SBAH then the system is bound and the SBA is 17 decrypted at step 105 using the SBAK also stored in region 17a and executes the SBA at step 18 106. If the hash does not match either the PBBAH or the SBAH, then the BBI 14a then looks 19 in a known location 25a for the RPBBA and calculates a hash of that section at step 107. If 20 this hash matches the RPBBAH stored in region 17a in step 108, the BBI 14a then executes 21 the RPBBA code at step 109. If none of the hashes match, the system halts at step 110. 22 [00821 Step 106 is shown in greater detail in Figure 6. At step 111, the SBA is booted 23 from the BBI 14a. The SBA then retrieves the public key ECPU1K 82 and gathers the HWSN 24 and SBC at step 112. If the SBC cannot be found at step 113, the system is halted at step 25 114. If the SBCs are found, the SBA attempts to validate the H/W board 12 at step 115 and 26 recover the SUC. 27 10083] Referring also to Figure 6, the SBA uses an ECPVS verification function to 28 validate the H/W board 12 by first combining signature component e (included in SBC) with 29 the HWSN to produce an intermediate value X. The verification function then uses the 30 public key ECPUK 82 to recover SUC from X: If this fails, the system halts at step 114. If -16- I the SUC is recovered, the SUC is used to unlock the IK from the IKF, wherein if the image 2 24a is successfully decrypted at step 116, the OS will boot at step 118 and thus the H/W 3 board 12 is implicitly verified. The IK is placed in memory at step 117. If the decryption at 4 step 116 fails, i.e. the resultant image is useless, then the system shuts down at step 114. 5 Therefore, if the hardware is original but the BIOS 14 has been swapped and credentials not 6 bound to the hardware are used then the SBA will not be able to properly decrypt the image 7 24a. The same is true if the hardware has been swapped but not the BIOS since the proper 8 HWSN is required to obtain the correct SUC to unlock the IK. 9 100841 The image 24a is encrypted and decrypted using an image encryption/decryption 10 driver (IEDD) inserted in a crypto interface layer in the OS low-level disk access routines. II The IEDD uses a strong, symmetric key algorithm for cryptographic protection of the image 12 24 (e.g. the 128-bit ABS standard). The IEDD has access to the I while it is stored in 13 memory. 14 100851 Referring now to Figure 7, when the OS 28 boots, it will enter its own 15 authentication sequence at steps 200 and 202 to identify and authenticate an operator of the 16 system using the LA, e.g. by running GINAC. The mechanism that enforces the 17 identification and authentication is typically either winlogon.exe or minlogon.exe (a stripped 18 down version of winlogon.exe), depending on the configuration of the OS. The winlogon.exe 19 version of the LA can be customized by replacing the GINA DLL as discussed above to 20 obtain GINAC also discussed above. However, if the minlogon.exe is used, since it contains 21 no GINA DLL, the system should be designed such that the LA is executed immediately 22 upon shell execution or at another appropriate instance that ensures that the LA is not 23 circumvented. 24 [00861 After the LA is initialized at step 202, the LA determines at step 214 whether or 25 not PCP is enabled. If PCP is not enabled then the user is logged on and the system enters a 26 logged-on-state at step 218. However, if the gaming machine 10 is PCP enabled, the LA 27 determines if the power supply has been removed from the machine 10 within a certain 28 duration of time (e.g. 15 minutes) at step 116. If the power supply has not been disconnected 29 during the specified time period then the user logged-on-state 218 is initiated. If the power 30 supply has been disconnected within the specified time period a user PIN entry process is 31 initiated at step 220. Either at the time of logging in or while the user is logged on, the PIN - 17- 1 can be changed by entering the MBP at step 222. During the user mode at step 218, the PCP 2 can be enabled or disabled by the user at anytime at step 224 or the system shut down at step 3 212. 4 [0087] It will be appreciated that the use of a PCP scheme for user authentication is only 5 one exemplary scheme. For example, a normal user-password or challenge-response could 6 also be used whereby multiple users each having their own username and password can be 7 authorized to enter the system through the LA. 8 [00881 The user PIN entry performed at step 220 is shown in greater detail in Figure 8. 9 After step 220 initiates, the user is requested to enter their PIN at step 300. When a PIN is 10 assigned, a user boot PIN mask (UBPM) is stored such that the following is satisfied: 11 MBP= PIN ® UBMP. When XORing the entered PIN with the stored UBPM, the 12 resulting MBP is hashed and compared with the stored MBPH value received from the server 13 74 during binding. When the user changes their PIN at step 222, UBPM is changed so that 14 the original MBP does not need to be changed. 15 [00891 The UBPM 31 is derived from the IUPM sent in the SSV from the controller 72. 16 The IUP is communicated to the user when they purchase the gaming machine 10. 17 Preferably, when the gaming machine 10 is powered up, the PCP is enabled by default so that 18 the user must enter their PIN in order to run the gaming machine 10, to change the assigned 19 PIN, or to disable PCP. If the user disables PCP at step 224 then the gaming machine 10 20 does not require the user to undergo step 220 in order to enter the user mode at step 218 as 21 explained above. 22 100901 If the PIN is correct at step 304, the user will enter the user-logged-on state 218. 23 If the PIN is incorrect, a failure counter is incremented by one at step 306 and the PCP 24 determines whether or not this was the first failed attempt. If so, a timer, e.g. 3-hour timer is 25 started at step 310 to provide a limited window for the user to attempt entering the PIN. If 26 not, the PCP determines whether or not it was the fifth failed attempt. If not then the user can 27 enter the PIN again within the time allotted. If it is the fifth failed attempt then the user 28 cannot enter the PIN again until the timer expires during step 314 whereby the failure counter 29 is reset at step 316 and returns to step 300. - 18- 1 10091] When the user-logged-on state is initiated and a service mode selection is made at 2 step 208, preferably at the same time, a technician challenge-response procedure is initiated 3 at step 210. When a technician is operating on the machine 10, a technician HBM 50a is 4 connected via a USB connection 52a to the H/W Board 12. The H/W Board includes a 5 challenge response client (CRC) 92 that is used to control the challenge-response procedure 6 in conjunction with a challenge response server (CRS) 90 at the server 74. 7 [0092] Preferably, the technician selects a menu item in the operating unit (e.g. gaming 8 machine 10) to enter the service mode. When the mode is selected, the LA will initiate a 9 challenge-response as exemplified below. 10 10093] In the example shown in Figure 10, the LA will first generate a challenge (CHAL) 11 using a random number at step 1. The LA then sends the CHAL and a system identifier 12 (SIN) to the CRS 90 at step 2 after establishing a secure connection 62a with the CRS 90 at 13 the server 74 (e.g. via a webpage) and sends the CHAL and SIN at step 3. The CRS 90 14 inputs the CHAL, the SIN and the private key ECPRK to the ECPVS signing function to 15 obtain a response value RESP which is then provided to the technician. The response is 16 produced at step 4 by computing a first signature component by encrypting the CHAL with 17 the private key ECPRK, computing an intermediate signature component by hashing a 18 combination of the first component, an identity of the server and the SIN, and computing a 19 second signature component using the intermediate signature component, wherein the two 20 components plus the SIN is the signature which is used as the response RESP. 21 10094] The CRS 90 sends the RESP to the CRC 92 at step 5 (e.g. for display) and the 22 server 74 is disconnected from the CRC 92 at step 6. The LA then verifies the RESP at step 23 7. It will be appreciated that the connection between the CRC 92 and the CRS 90 may also 24 be accomplished using the HBM 50 if the technician is already connected to the H/W board 25 12. 26 100951 The LA uses the ECPVS verification function to combine the first signature 27 component with the SIN to obtain a value X. The CHAL is then recovered from X using the 28 public key ECPUK that is retrieved from the SBA. The LA then compares the recovered 29 CHAL to that which it originally created to verify that the CHAL was signed by the server 74 -19- 1 only. If the challenge response verifies then the system enters a service mode at step 210 2 until the service is complete and the system shuts down at step 212. 3 100961 There are several possible scenarios where a technician needs to gain access to the 4 H/W board 12. In one scenario, the HDD is damaged and needs to be replaced. The 5 technician in this case would reprogram the BIOS to the standard, unbound BIOS image that 6 would exist before the binding process described above is implemented. The technician 7 installs a new HDD with a standard production image into the board. When the system is re 8 booted, it will attempt to contact the HBM 50 to perform cryptographic binding. For this to 9 occur, the HBM 50 will communicate with the server 74. The HBM application can exist on 10 the same device that establishes this communication, e.g. key agent 75 or HBA 52. Once the 11 binding completes successfully, the system will have new credentials and a newly encrypted 12 image 24. Alternatively, the technician can replace the system with a pre-bound H/W board 13 HDD pair. 14 100971 - In another scenario, the BIOS 14 is damaged and thus the H/W board 12 will most 15 likely need to be replaced. Similar to the scenario above, if the technician replaces the H/W 16 board 12 and inserts the user's HDD 20, the secure boot authentication process will assume 17 that the hardware is unbound since it will be unable to locate the SBCs and enter the binding 18 process. 19 10098] In yet another scenario, both the H/W board 12 and the HDD 20 are damaged and 20 the user requires a completely new system. If the technician is able to connect to the server 21 74, then they can install a new H/W board and HDD and using the binding procedure 22 described in the first scenario described above. If it is not possible to perform the binding 23 operation on-site because the technician cannot connect to the server 74, then a pre-bound 24 H/W board 12 and HDD 20 can be installed similar to the alternative discussed above. To 25 inhibit the illegitimate used of the pre-bound system, the user PIN can be unknown to the 26 service technician. When the new system is first powered up, the technician will have to 27 enter the service mode (described above) to perform testing on the bound system. The user 28 will then obtain the new PIN from the manufacturer or producer in order to authenticate and 29 operate the machine 10. -20- 1 [0099] In yet another scenario, the software in the image 24 is corrupted in some way. 2 When a service technician needs to access the H/W board 12 to repair the software, they will 3 enter the service mode wherein the service mode provides a toolkit for the technician to 4 perform various software recovery or re-installation applications. If the OS 28 or the 5 application software 32 has become corrupt beyond the ability to repair it using the service 6 mode, the technician can follow the above steps to replace a damaged HDD 20 or replace 7 both the H/W board 12 and the HDD 20 with a pre-bound pair as also described above. 8 [001001 Authorization of a particular technician to perform the challenge response can be 9 controlled by an authentication procedure that is used to log the technician into 10 manufacturer's or producer's network. Other mechanisms could also be used to ensure that a 11 particular system is allowed to be serviced, such as providing an enabling feature to the CRS 12 90. For example, an owner of the gaming machine 10 can contact the producer in any 13 suitable manner and request to have the machine 10 serviced. An operator authorizes 14 servicing for that particular gaming machine 10 (or system of gaming machines) by setting a 15 flag in a customer database. At some time later when a technician logs onto the producer's 16 network and connects to the CRS 90, the CRS 90 contacts the server 74 in order to look up 17 the SIN in the customer database to verify that servicing is authorized.. The technician may 18 then proceed with the challenge response. 19 [001011 The H/W board 12 may at some point require a secure software upgrade. 20 Software upgrade security can be accomplished using a file-point system. Referring to 21 Figure 11, a file-point client (FPC) 96 located on the product (e.g. gaming machine 10) uses 22 existing application binaries to generate a cryptographic request at step 1 to send to a file 23 point server (FPS) 94 located at the server 74 at step 2. As such, the machine 10 can request 24 software upgrades (e.g. at periodic intervals of time) without the need for a technician as 25 shown in Figure 11. The FPS 94 searches through a database 95 of all previous versions of 26 the application binaries at step 3 and verifies which version of the application the technician 27 is upgrading and whether the technician is authorized to perform the upgrade at step 4. The 28 FPS 94 derives a session encryption key at step 5 and encrypts the upgrade binary at step 6, 29 then returns the encrypted upgrade to the FPC 96 at step 7. The FPC 96 also derives the 30 session key at step 8 in order to decrypt the upgrade at step 9. The algorithm used to perform -21- 1 these steps is designed to ensure that only the requesting FPC with a valid application binary 2 is able to derive this key to load the upgrade at step 10. 3 [00102] In a specific example, the file point system uses a proprietary key establishment 4 algorithm to ensure that application binaries are protected in transit. When the FPC 96 5 requests an upgrade, it uses the data within the object to be upgraded (OU) to generate an 6 ephemeral key (EK). It then creates a request datagram that includes information about the 7 OU, the system ID and the EK. This data is then sent to the FPS 94, which uses the SID to 8 lookup and verify the identity of the FPC 96 (and possibly validate that the system is 9 authorized to perform the upgrade) and to obtain a-hash of the system's SBC. It then uses the 10 OU information within the request to look up the version of the OU in its upgrade object 11 database 95. The FPS 94 then generates the EK, calculates an ECPVS signature of EK, using 12 the hash of the secure boot credentials (SBCH) as validation, and returns it to the FPC 96 as a 13 response datagram. 14 1001031 The FPS 94 then derives a session key (SK) from the two EKs and uses this SK to 15 encrypt the upgrade object (U3O). The FPS 94 then sends the encrypted UO to the FPC 96. 16 When the FPC 96 receives the response datagram, it calculates the hash of its SBC 18 and 17 verifies the ECPVS signature using the ECPUK and the SBCH, which authenticates FPS 94, 18 which recovers FPS's EK. The FPC 96 then derives the SK from the two EKs and uses it to 19 decrypt the UO. 20 100104) The signature generation can be performed using ECPVS as follows: 21 ECPVSECRK (SBCH,EK) => RESP; and the response is verified using ECPVS as follows: 22 ECPVSECPUK (SBCH, RESP) => EK. 23 [00105] In one example, the API 56 includes a single function call FPC_getUpgrade(sid, 24 appID, curVerID, appFilename, fpsIPAddr, timeout), where sid is the system identifier, 25 appID is the application identifier, curVerlD is the current version identifier of the 26 application, appFilename is the filename of the application binary, fpsIPAddr is the IP 27 address of the FPS 94, and timeout is the length of time to wait for a response from the server 28 74. This function first constructs the cryptographic request datagram and then connects to the 29 FPS 94 to deliver the request. The function then waits for the designated timeout period for a -22- 1 response. When the response is received, the function validates the response datagram, then 2 decrypts and stores the new application binary as described above. 3 1001061 In the same example, the server API (not shown) includes a single function call 4 FPSwaitUpgradeRequest(dbAddr, portNo), where dbAddr is an address identifier to contact 5 the upgrade database 95. The server 74 waits for a request on the port identifier by portNo 6 for incoming socket connection requests from any FPC 96. When a request is received, the 7 function contacts the database 95 to obtain the necessary information to generate the response 8 datagram and to encrypt the binary image to be upgraded. The FPS 94 then sends the 9 response datagram and encrypted image back to the calling FPC 96. Once this is complete, 10 the FPS 94 generates a log of the communication. 11 [00107] Due to the open and relatively insecure characteristics of the standard platform, 12 the security of the system described above is maintained through the separation of the 13 cryptographic identity between the BIOS 14 and HDD 20. The following describes possible 14 attacks to the system and the effective security enforced by the system to thwart such attacks. 15 1001081 One attack includes where the attacker attempts to flash their own BIOS to the 16 H/W board 12 in an attempt to circumvent the secure boot process. This attack is prevented 17 because the re-flashing will destroy the SBC necessary in the secure boot process. An 18 attacker will not be able to decrypt the image key (SUC), and thus will not be able to decrypt 19 the image 24. 20 1001091 Another attack involves an attacker removing the HDD and attempting to recover 21 the encrypted image via brute-force cryptoanalysis (e.g., known-plaintext, chosen-plaintext, 22 adaptive chosen-plaintext, adaptive chosen ciphertext, related key etc). This attack becomes 23 infeasible because a strong standards based encryption algorithm (e.g. AES) with appropriate 24 cipher-strength can be used in the system to thwart such an attack. For example, using a 25 distributed computing network, the brute force attack on an 80-bit AES key can take years 26 approximately one decade and adding bits to the key length increases this time exponentially. 27 In the gaming environment this type of attack is clearly infeasible for an attacker to pursue. 28 1001101 It is therefore seen that by binding hardware-specific data to credentials stored in 29 the BIOS and using ECPVS signature generation and verification, an implicit verification Of 30 an image 24a can be performed. Moreover, the use of a KIS 70 enables the distribution and - 23 metering of keying data (e.g. SSVs) in conjunction with a specialized HBM. Binding the H/W board 12 during manufacturing using a KIS 70 inhibits grey or black market activity and ensures that the content being loaded onto the machine 10 is not compromised by a third party contractor. Similarly, the use of an HBM during repairs protects the image 24a from being tampered with by a technician. 1001111 In yet another embodiment, shown in Figures 13-17, a gaming device 400 used in gaming machine 10, is authenticated using a one time programmable (OTP) read only memory (ROM) BIOS 402. The BIOS 402 is trusted because by nature it cannot be modified (i.e. "read only"), and is used in this embodiment instead of a flash BIOS, which by nature can be modified. 1001121 Referring first to Figure 13, the gaming device 400 generally comprises the OTP ROM BIOS 402, a hard disk, and system random access memory (RAM) 406. The BIOS 402 stores a system initialization module 408, which is loaded into RAM 406 during a boot operation; and an ECPV authenticator module 410, which is used to perform an ECPV verification or authentication of the contents of the hard disk 404. The ECPV authenticator module 410 stores an ECPV public key 412 and an ECPV signature component s, which are used during ECPV verification. [001131 The hard disk comprises a boot loader 414, which sets up an operating system 416, which in turn loads and executes an application 418. In this example, the application 418 is gaming data that is run, displayed, and played by a user on the gaming machine 10. As shown in Figure 13, in this embodiment, the boot loader 414 and operating system (O/S) 416 are encrypted on the hard disk, and the application 418 is plaintext or "in the clear" or otherwise decrypted or not encrypted. 1001141 The ECPV authentication module 410 is executed at the boot up operation to simultaneously validate the application 418 and the O/S 416 prior to execution of the application 418. The verification is performed according to the principles of ECPV signature verification. [001151 Referring now to Figure 14, the following acronyms are used: PubKey = ECPV Public Key 412 6326233_1 - 24 - PAC = plaintext application code (e.g. application 418) EBLC = encrypted boot loader code (e.g. boot loader 414) EOSC = encrypted operating system code (e.g. O/S 416) PBLC = plaintext boot loader code (e.g. decrypted boot loader 414') POSC = plaintext operation system code (e.g. decrypted O/S 416') 1001161 In this example, the ECPV signature comprises the components (EBLC+EOSC, s, PAC), where PAC is the visible portion, e.g. plaintext application 418, EBLC+EOSC is signature component e, and s is the other ECPV signature component. The signature components, along with the ECPV public key 412, are input into an ECPV verification function 420 by the ECPV authentication module 410. The signature components e and s are computed according to the principles of ECPV, e.g. during a binding or manufacturing process as discussed above, and the necessary components written to the unalterable BIOS 402. [001171 For example, as shown in Figure 17, the hard disk 404 in its original, fully unencrypted form, may be split into a visible portion V and a hidden portion H, where the visible portion V comprises the application 418, and the hidden portion H comprises the unencrypted boot loader 414', the unencrypted 0/5 416' and a certain amount of redundancy that is added if necessary. In this case, the redundancy is added to the unencrypted boot loader 414' and/or the /5 416', which constitute the hidden portion H. The amount of redundancy should be stored by a gaming authority for later payout verifications during run time, as will be explained in greater detail below. 1001181 The hidden portion H is encrypted using PubKey to generate the signature component e, which is equivalent to EBLC+EOSC. PubKey is generated from a random number k computed by the signing entity (not shown). The signing entity also has a signing private key a as shown in Figure 17. Component e is concatenated with the visible portion V (equivalent to PAC), and hashed to create an intermediate component d. The signature component s is then computed using the intermediate component d, the private key a, and the random number k. The signature component s may be written to the authenticator module 410 along with the ECPV public key 412, or may be stored in a suitable location onl the hard 6326233_1 -25 disk 404. The resultant signature is (e, s, V) or equivalently (EBLC+EOSC, s, PAC) in this example. [001191 Turning back to Figure 14, the ECPV verification function 420 computes a representation d' of intermediate component d by combining signature component e (e.g. EBLC+EOSC) with visible portion V (e.g. PAC), e.g. via concatenation. A decryption key Z is then derived by first computing X = sP, where P is a point on an elliptic curve; then computing Y = e-PubKey; and finally subtracting Y from X. The decryption key Z is then used to decrypt PBLC+POSC from EBLC+EOSC. [001201 During a boot up sequence, the system initialization module 408 is first loaded into system RAM 406 and executed. The system initialization module 408 executes a power on self test (POST) but since the BIOS 402 is unalterable, does not need to perform a self integrity check. The system initialization module 408 then loads and executes the ECPV authenticator module 410. The authenticator module 410 then accesses the ECPV public key 412 and signature component s stored therein, obtains copies of the encrypted boot loader 414 and encrypted OS 416 (EBLC+EOSC), and the plaintext application 418, which are temporarily stored in system RAM 406, and inputs them into the ECPV verification function 400. As described above and shown in Figure 17, the ECPV verification process recovers the plaintext boot loader 414' (PBLC) and plaintext OS 416' (POSC). The PBLC and POSC are then loaded into system RAM 406, and execution is passed to the PBLC. The PBLC then executes POSC, which in turn loads and executes the application 418 already loaded in the system RAM 406 during ECPV verification. 1001211 Since the PAC is used in the ECPV verification, if the application 418 has been tampered with, e.g. code added etc., the application 418 will not run properly, since an incorrect boot loader 414' and/or OS 416' will be recovered. Therefore, authentication at boot up is implicit. [001221 When verifying code at run-time, e.g. to verify a win output from the gaming device 400, the application code 418, and EBLC and EOSC (already stored in system RAM 406 from the boot up sequence), are used to perform another ECPV verification. To verify the win, a gaming authority may be called to the machine 400, and a peripheral device (not shown) plugged in, e.g. via a USB connection (not shown). The peripheral device should be 6326233_1 -26 trusted by virtue of it being under the supervision of the gaming authority. The application code 418, EBLC and EOSC, PubKey, and signature component s are input into an ECPV verification function 420 stored on the peripheral device and the plaintext PBLC+POSC recovered, which is the hidden portion H. As discussed above, H has or is given a particular amount of redundancy, e.g. a predetermined number of zeros. The peripheral device, may then check the redundancy of H and if it matches the expected redundancy, then the application code 418 has not been tampered with and is verified. 1001231 For the purposes of verifying a win output from the gaming machine 10, the cash or credit may then be paid out by the gaming authority if the run-time code is verified. The run-time verification enables the gaming authority to ensure that the application code (PAC) that signalled the win, wasn't tampered with between the boot up sequence and the win. The boot up sequence is used primarily to verify that the gaming machine has not been tampered with while powered down. Since the boot up verification is implicit, any tampering will result in bad code that will not run properly. 100124] Referring now to Figures 15 and 16, alternative system layouts may be used. 1001251 In the first alternative shown in Figure 15, only the boot loader 414 is encrypted, and the OS 416' and application 418 are in plaintext. For this embodiment, the hidden portion H is PBLC, the visible portion is PAC+POSC, and the ECPV signature is (EBLC, s, PAC+POSC) computed using the above-described principles while inputting the alternative values for H and V. ECPV verification would therefore check the redundancy of the boot loader 414' when verifying at run time and implicitly verify at boot up as before. The embodiment shown in Figure 15 simplifies decryption and memory requirements since the boot loader 414 is a smaller piece of software than the OS 416'. 1001261 Turning now to Figure 16, where the application 418 is relatively small (according to available memory), the application 418 may be encrypted and an encrypted application 418' stored on the hard disk 404. The plaintext version of the application 418 is in this embodiment the hidden portion H, where the signature component e is now the encrypted application EAC. The visible portion would then be the plaintext boot loader PBLC and the plaintext OS POSC, and the ECPV signature would be (EAC, s, PBLC+POSC). ECPV verification therefore either checks the redundancy of the plaintext application 418 when 6326233 1 - 27 verifying at run time and implicitly verifies at boot up as before. By encrypting the application code 418, some protection against theft of the application code 418' may be given, provided that the ECPV public key 412 is protected. If an adversary was able to steal the hard disk 404, unless they have knowledge of the ECPV public key 412, they would not be able to recover the plaintext application code 418. [001271 It may therefore be seen that the embodiments shown in Figures 13 to 17 enable both the OS 416 and application code 418 to be verified simultaneously using ECPV signature verification. The unalterable OTP ROM BIOS 402 can be trusted as it cannot be modified and thus the BIOS 402 does not need to be verified on boot up and can proceed directly to authenticating the OS 416 and application 418. ECPV signature verification can be used to verify both the boot up sequence and at run time, e.g. to verify a win. Such verifications may be used to satisfy a gaming authority that the application code 418 has not been tampered with when the gaming machine 400 is powered down, and during execution thereof. [001281 Yet another embodiment for authenticating a gaming machine 500 is shown in Figures 18-27. Similar to the embodiments above, the gaming machine 500 includes a display 502 and input mechanism 504 to enable a player to interact with the gaming machine 500 and play one or more games loaded thereon. The gaming machine 500 also includes a protected hardware board (H/W) 506. In this embodiment, the hardware board 506 is connected to a network 510 over a data connection 508 to enable the gaming machine 500 to download (or have uploaded to) new game files 512. It will be appreciated that the network 510 may be an internal or local network or may be an external network such as the Internet, depending on the location of the gaming machine 500. For example, if the gaming machine 500 is in a casino, there may be several machines connected to the same local network 510, which may have a server (not shown) to control distribution of game content and monitoring of the gaming machines etc. In another example, the gaming machine 500 may be a stand alone unit in a public location wherein the gaming machine 500 connects to an external entity or server (not shown) over a network connection. [00129] The hardware board 506 shown in Figure 18, has a BIOS OTP ROM 514, a memory 516 for storing data during operation of the machine 500 and/or for persistent storage as needed, a game component 518 for running game files 512, a jurisdiction 6326233_1 -28component 520 for storing jurisdiction related data such as gaming regulations, payout odds etc., and a platform or OS component 522 (i.e. portions of the content used by the gaming machine 500). [00130] Turning now to Figure 19, the components of the hardware board 506 are shown in greater detail. The ROM 514 includes a system initialization module 524 (similar to that described above), a verification agent 526 for booting up the gaming machine 500, and an input value to be used to begin a chained signature verification procedure, in this example, a public key KPUB-A. The value KPUWA is used as an input to the first of the chained key or value recovery steps in such a procedure, the general flow of which is also illustrated in Figure 19. Each of the game component 518, the jurisdiction component 520 and the platform component 522 includes an entry module 533, one or more other modules 532, and an end module 534. Each module 532, 533 and 534 is a portion of code, a file, a collection of files or other segment of data that, when combined with the other modules 532, 533, 534 in the same component, make up the complete set of data for that component. In this example, the game component 518 includes a Game Entry Module, an arbitrary N number of other game modules 532, which will be hereinafter referred to as Game Module 1, Game Module 2, ..., Game Module N; and an Game End Module. [00131] The jurisdiction component 520 includes only one module 532 in this example, namely a Jurisdiction Module and thus does not require either an entry module 533 or an end module 534. The platform component 522, similar to the game component 518, includes a Platform Entry Module, an arbitrary number of other platform modules 532, in this example M modules hereinafter referred to as Platform Module 1, Platform Module 2, ... , Platform Module M; and a Platform End Module. [001321 With the configuration shown in Figure 19, in both the game module 518 and the platform module 522, the modules 532 may be removed, inserted, replaced, shifted, reordered etc. without reprogramning the signature verification sequence. In this example, as will be explained below, the entry modules 533 are always operated on first as they are signed using the output from the end module 534 of the previous component, or using KPUB-A in the case of the game component 518. The order in which the other modules 532 are operated on to recover the next value needed in the chain, is determined by referencing a component manifest 531 stored in memory 516. 6326233_1 -29 - 1001331 Each module 532, 533, 534 is signed before it is loaded into the respective component on the hardware board 506, and a value stored in the signature is recovered using a recovery function 528. The recovery function 528 operates on a set of signature components, one set being associated with each module 532, 533, 534, to recover a piece of data encrypted therein. The recovery function 528 is related to a corresponding signature generation function that encrypts or hides a portion of data that is recovered at each sub-step during the chained verification procedure. The recovered data is then used as an input to the next execution of the recovery function 528 performed in the chain. As such, the modules 1532, 533, 534 are not authenticated individually at each execution of the function 528, but instead authenticated implicitly and at the same time by comparing a final output recovered from the signature on the end module 534 of the last component, with the original input to the chain. In this way, the entire contents of the hardware board 506 can be authenticated at the same time. Preferably, the recovery function 528 is related to signature generation and verification functions, preferably an ECPVS scheme, the details of which are explained above. As illustrated in Figure 19, execution of the recovery function 528 for each module 532 in the same component recovers the same value or key, which enables these game modules or platform modules (i.e. those that aren't the entry or end modules) to be removed, replaced, added etc. without having to reconfigure the entire system. 1001341 When a new module is added, the chain is lengthened in that another verification step is required at boot up, however, since the output is the same as the other modules 532, the respective inputs and outputs required to be passed between such components would not be affected. If the component manifest 531 is relied upon for determining the order in which modules are to be verified, then it should be updated as new games are added. 1001351 Figure 20 illustrates where a new game file 512 is downloaded from the network 510. A new game module corresponding to the new game file 512, named Game Module N+1, is added to the end of the set of modules 532 in the game component 518. The chained structure shown in Figure 19 enables the new game module to be verified as it is downloaded without having to re-boot the entire gaming machine 500. By enabling new game modules to be added without re-booting the system, a significant amount of time can be saved and such new games can be added while the gaming machine 500 is in operation. 6326233_1 -30- 1001361 The memory 516 also stores an authentication code, e.g. an HMAC, which comprises a keyed-hash of the contents of the platform or OS component 522 generated using a keyed hash function 531. In this example, the key used to generate the HMAC is generated using an intermediate value (KPUB-C) that is recovered during the chained verification sequence at boot up. 1001371 As noted above, each module 532, 533, 534 is signed, preferably using an ECPVS scheme, such that the recoverable or hidden portion H from each module is used as an input (e.g. the public key) for the next execution of the recovery function 528 in the chain. The values used to sign the modules 532, 533, 534 are private keys, which have corresponding public keys. Although considered 'public', the public keys used herein should not be stored on the gaming machine 500 except for the value KPUB-A (stored in ROM and needed to start the chain) since these keys can be used to recover inputs needed for authenticating the gaming machine 500. The corresponding private keys can be generated and stored securely at an appropriate authority such as the gaming machine 500 manufacturer and/or a gaming authority (regulator, casino management etc.). In this way, a trusted party is responsible for signing the game modules and platform modules prior to installing the gaming machine 500 and responsible for signing new game modules. In the example described herein, five key pairs are used, namely KpUB-A/KPRlv-A, KpUB-x/KPRIv-x,

KPUB

B/KPRIv-B, KpUB-C/KPRIv-C, and KPUB-Z/KPRIv-z. It will be appreciated that greater or fewer key pairs may exist if there are greater or fewer modules/components in the gaming machine 500. Since the key pair KpUB-c/KPRIv-c is used to sign the Jurisdiction Module, which contains gaming regulations and the like, that key pair should be held by and/or generated by the gaming authority and be unique to the Jurisdiction Module. As will be explained below, this also enables the gaming authority to retain a copy of the HMAC for conducting its own authentication of the platform module 522, e.g. during a payout. 1001381 Figures 21(a) to (c) illustrate signature generation steps used to sign the game component modules using ECPVS. In diagram (a), the Game Entry Module is signed using KPRIv-A and the hidden or recoverable portion, i.e. the value to be encrypted in the signature, is KPUB-x. A first signature component eGENT is generated by encrypting KPUB-X using a key Z, which is derived from a randomly generated, ephemeral public/private key pair at step 250. At step 251, the intermediate component d is computed by hashing a combination (e.g. 6326233_1 -31 concatenation) of the component eGENT and the contents of the Game Entry Module. A second signature component SGENT is then generated at step 252, as a function of intermediate component d using the private key KPRIv-A and the ephemeral private key. Similar to the other embodiments above, the component 's' in ECPVS can be generated, e.g., using the Schnorr signature algorithm. The resultant signature provided at step 253 is comprised of the components eGENT and SGENT and the Game Entry Module, which can be obtained directly from the game component 518 at the time of executing the verification function on for the corresponding module. [001391 In Figure 21(b) a generic procedure for signing the other game modules, i.e. from 1 to N is shown. It can be seen that each of the remaining modules 532 (from 1 to N) is signed using the same inputs Z and KPRIvx, and each will encrypt or hide the same value. In this way, the other modules 532 can be verified in any order, since they each require the same input and produce the same output (when the modules are authentic) for use in the next execution of the signature recovery function 528 in the chain. In step 254, KPUB-X is encrypted using a key Z, derived from a randomly generated ephemeral key pair, as an input in generating the first signature component eGltoN, which is then concatenated with the respective game module Game Module ltoN and hashed at step 255 to generate the intermediate component d. The second signature component is then generated as a function of d using the private key KpRIv-x and the ephemeral private key in step 256 and the resultant signature is obtained at step 257. [001401 In Figure 21(c), a procedure for signing the Game End Module is shown in steps 258 to 261. It can be seen that the signature is generated in a similar fashion to that shown in Figures 21(a) and (b), however, a value Z is used in this case to encrypt another value, KPUB B, which is to be used in the verification of the jurisdiction component 520. As such, the details of steps 258 to 261 need not be explained further. 100141] Turning now to Figure 22, a procedure for signing the Jurisdiction Module is shown. The Jurisdiction Module uses the value KPUB-B as an input during verification, and this value is recovered from the signature on the Game End Module. The signature for the Jurisdiction Module is created, in part, by encrypting another value KPUB-C with a key Z at step 262, to generate the first signature component eJm, and using the private key KPRIV-B to generate the second signature component sJM. The value KPUB-c may then be recovered from 6326233_1 -32the signature on the Jurisdiction Module. The value KPUB-c, once recovered, is then used as the input to the chain of recovery functions 528 executed on the signatures on the platform component modules. At step 263, the intermediate component d is generated by hashing a concatenation of the first signature component ejm and the Jurisdiction Module, and at step 264, the second signature component sjm is generated as a function of the intermediate component d (and using the key KPRIVB). The resultant signature provided at step 265 is the first and second signature components eJm and sJm, and the Jurisdiction Module. 1001421 Turning now to Figures 23(a) to (c), flow diagrams are shown for signing the modules 532, 533, 534 of the platform component 522. It may be noted that modules 532, 533, 534 of the platform component 522 are signed in the same way as the corresponding modules 532, 533, 534 of the gaming component 518 with the Platform Entry Module using the value KPUB-C as an input. Each application of the recovery function 528 on Platform Modules 1 to M recovers the same value KPUB-Z, which is ultimately used as an input for recovering KPUBA from the signature on the Platform End Module as can also be seen in Figure 19. For the platform component 522: KPUB-Z is encrypted using an ephemeral Z and KPRIV-C is used to generate the signature on the Platform Entry Module; KPUB-Z is encrypted using an ephemeral key Z and KPRIV-Z is used to generate the signatures on the subsequent modules; and KPUB-A is encrypted using an ephemeral key Z and KPRIV-Z is used to generate the signature on the Platform End Module. Steps 266-269 in Figure 23(a) illustrate a procedure for signing the Platform Entry Module, steps 270-273 in Figure 23(b) illustrate a procedure for signing Platforrm Modules 1-M, and steps 274-277 in Figure 23(c) illustrate a procedure for signing the Platform End Module. It can be seen in Figure 23 that the signatures on the platform modules are generated in a similar fashion to those generated on the game modules, and thus further detail need not be provided. 1001431 Referring now to Figures 24-26 and Figure 19 described above, a procedure for executing the chained signature verification during a boot-up sequence of the gaming machine 500 will now be discussed. 1001441 Prior to execution of the chained signature verification procedure, and once the gaming machine 500 has been booted or powered up etc., during the boot sequence, the verification agent 526 is initiated, reads or otherwise obtains a copy of the value KPUB-A burned on the ROM 514, and accesses the component manifest 531, to determine the order in 6326233_1 _- 33 which the other gaming modules 532 are to be operated on. As noted above, the Game Entry Module is operated on first, and thus the verification agent 526 then obtains the signature components eGENT and SGENT and the data for the Game Entry Module (i.e. the 'signature' for Game Entry Module) at step 278 (see Figure 24). [001451 According to the steps in ECPVS signature verification, at step 279, an intermediate component d' is generated in the same way as done during signature generation, i.e. using the first signature component eGENT and the Game Entry Module (e.g. by concatenating the two pieces of data and hashing the result). At step 280, a decryption key Z is obtained using the second signature component SGENT, the intermediate component d', and the value KPUB-A. The decryption key Z is then used in step 281 to decrypt or 'recover' the value KPUB-X from the first signature component eGENT. The recovered value KPUB-X is then output at step 282 so that it may serve as an input to the first execution of the recovery function 528 performed on the remaining Game Modules 1 to N and ultimately the Game End Module. Steps 283 to 287 are repeated for each remaining Game Module 1 to N (i.e. until i = N in step 288) wherein a copy of the value KPUB-x that is recovered at each instance of step 286 is fed into the next operation of the function 528. At the end of the chaining sequence for the remaining modules 532, the version of KPUB-x recovered from the signature on Game Module N is then used to recover the next key hidden in the signature on the Game End Module in steps 289 to 293. KPUB-X is used to recover the value KPUB-B at step 292, which is then output at step 293 for use as an input to recover another value from the signature on the Jurisdiction Module as shown in Figure 25. 1001461 It can be appreciated that since ECPVS enables one to control what is encrypted or 'hidden' in the signature, an ECPVS can be used to recover a predictable output, which then can be used as a predictable input to the next step in the chain. In other words, the hidden portion H of the message is the output required to be input to the next module. Therefore, the signature can be performed using the game code as the visible portion and the required input for the next stage as the hidden portion. The recovery steps during verification of the signature using the game code and the input will recover the hidden value provided the code and/or input has not been compromised. Each execution of the recovery function 528 produces an un-authenticated input to the next stage, however, if any of the modules are compromised, the result at the end of the chain will not provide the correct output that 6326233_1 -34permits authentication of the entire content. In this way, the proper output must be recovered in each execution of the recovery function 528 to ensure that an incorrect value does not propagate through the chain. This enables the gaming machine 500 to authenticate the entire content of the hardware board 506 implicitly using the result recovered in the final application of the recovery function 528. [001471 Steps 294-299 in Figure 25 illustrate the recovery of the value KPUB-C using the signature on the Jurisdiction Module and the value KPUB-B, which was recovered from the Game End Module. The value KPUB-C is provided both as an input to the chain of recovery operations for the platform component 522, and to generate the HMAC at step 300 where the HMAC is stored at step 302 for later authenticating the platform module 522 when new game modules are downloaded. The HMAC is generated by hashing the contents of the platform module 522 with a keyed hash function 531 that uses a value derived from KPUB-C as the key (e.g. key =J(KPUBC)). The HMAC may be generated in parallel with the verification chain for the platform component 522 (as shown), may be generated before proceeding with the chain for the platform component 522, or may be done at the end of the boot authentication procedure. 1001481 If game code included in the game component 518 has been tampered with, the wrong key KPUB-C would have been recovered during the chain of recovery operations on the modules of the game component 518 illustrated and described above. Similarly, if the contents of the platform component 522 have been tampered with, even if the correct value KPUB-c is recovered, the HMAC will not be the same as a similar HMAC that is typically kept by the appropriate gaming authority when installing and upgrading the gaming machine 500. However, if the remaining steps in the chain do not produce an authentic output (indicating an authentic hardware board 506) the HMAC would be incorrect but would not be needed in any event since the gaming machine 500 would have to be shut down to correct the problem in such a scenario. 100149] Referring now to Figure 26, the recovered value KPUB-C is then used to recover KPUB-Z from the Platform Entry Module in steps 305 to 309. This is done by obtaining the signature components ePENT and SPENT and the contents of the Platform Entry Module. The value KpUB-z is recovered from the component ePENT at step 308 and output at step 309 for use in the next verification in the sequence. In steps 310 to 315, the value KPUB-z is used to 6326233_1 - 35 recover the next KpUB-z for use in the chain. When all of the other modules 532 have been operated on, the final version of KPUB-Z that is recovered from the signature on Platform Module M is fed into the recovery function 528 to enable recovery of the value KPUB-A using steps 316 to 320. The output KPUB-A is then compared to the KPUB-A stored in the BIOS OTP ROM 514 at step 321 to authenticate the hardware board 506. If the values match, then the boot sequence has been successful, and the games can be played and normal runtime operations may commence at step 303. If the output KPUB-A does not match the value stored in ROM 514, then this indicates that one or more of the modules in one or more of the components has been compromised, tampered with or corrupted in some way. This may then initiate an error or disable function at step 304 to cease operation of the gaming machine 500. [001501 As noted above, in this embodiment, during runtime, new game files 512 can be downloaded to the gaming machine 500. When a new game file 512 is downloaded, a new game module 532 is inserted and is verified before proceeding with allowing such a game to be played. [001511 Figure 27 shows a procedure for authenticating a new game file 512 once it has been downloaded at step 322. It will be appreciated that the new game module, if authentic, would include a signature with the game and thus the new game file 512 should already be signed at 323. Although the gaming machine 500 may be programmed to be responsible for signing each new game as it arrives, typical gaming regulations would not permit this and would require a trusted third party (e.g. the gaming authority or a CA therefor) to sign and make the new game file 512 available to the gaming machines 500. [00152] At step 301, the value KPUB-A is read from the ROM 516 and used with the signature for the Game Entry Module to recover KPUB-X according to steps 278-282 described above. The other modules 532 may be skipped and the value KPUB-X used to immediately recover KPUB-X from the new Game Module N±1. [00153] The value KPUB-X recovered from the Game Entry Module is used with the signature components for the New Game Module N+1 obtained at step 324, to generate the intermediate component d' at step 325. Steps 326-328 are then performed to recover KPUB-X, which is then used at step 328 to recover KPUB.C from the Game End Module according to steps 289-293. 6326233_1 36 [001541 Now that KPUBC has been re-recovered from the Jurisdiction Module, it can then be used to compute a hash verify value HMAC' at step 330. As when generating the HMAC at boot up, the value KPUB.C is used to derive the key for the keyed hash function 530 that is applied to the contents of the platform module 522 as it currently exists and then removed from memory after the HMAC has been created. At step 331, the values HMAC' and the stored HMAC are compared. If there is a match, the gaming machine 500 can continue operation at step 303. If there is not a match, then either the New Game Module is corrupt or the contents of the platform module 522 have been tampered with since the boot up sequence. This indicates a problem with the gaming machine 500 and an error or disable function is executed at step 304. [001551 Accordingly, new game files 151 can be downloaded and added to the game component 518 without rebooting the system and without reconfiguring the chain of signatures. Only the entry and end modules 533 and 534 of the game component 518 need to be operated on again and the other modules 532 can be skipped. By storing the HMAC at boot up, the chain sequence for the platform component 522 does not need to be performed in order to authenticate the entire contents of the hardware board 506 when new games are added. This is also possible since the HMAC is computed using an intermediate key and only the recovery of the intermediate key is needed to create the value HMAC'. In this example, the signature on the Jurisdiction Module is used to recover the intermediate key KPUB-C and to obtain the input for this operation, the encrypted portion of the signature for the Game End Module needs to be recovered. [001561 An alternative to the verification chain shown in Figures 24-26 would be to use the value KPUB-A as the input for each and every module other than the end module 534. This would avoid having to target a specific entry module 533 but would not link the inputs and outputs for each module 532 in the same way. As such, although each module 532 can be signed using KpUB.A, the example described herein is preferable as corruption of any module would propagate through the chain resulting in the output not authenticating. [001571 There are several alternatives to the download verification procedure shown in Figure 27, the choice of which could be used would depend on the nature of the application. The procedure shown herein skips recovery of the values KPUB-X from the signatures on the other modules 532 and skips recovery of the values KPUB-B, KPUB-Z and KPUB-A from the 6326233_1 - 37 signatures on the platform modules, by storing the HMAC and recovering KpUB-C to authenticate the HMAC stored in memory 516. This avoids a complete reboot of the gaming machine 500. In a gaming environment, rebooting every time a new game is downloaded is undesirable, especially where a generic gaming machine 500 downloads new games nearly every time it is run. In other applications where a reboot is not as undesirable, the verification agent 526 could forego generating the HMAC at boot up and simply re authenticate the entire content of the hardware board 506 (with the new Game Module N+1 inserted after the Game Module N) each and every time a new game is added. Other alternatives include skipping the other game modules 532 as shown in Figure 27 but not using the HMAC and simply continuing with recovery of the values for the remainder of the chain, or skipping the other game modules 532 while still using the HMAC to later authenticate the platform component 522. 1001581 A general embodiment is shown in Figure 28 for authenticating one or more code blocks 344 in a computer-based system comprising data that is to be secured and then authenticated at some other time, according to the principles discussed above. Each of the one or more portions of content or code blocks 344 has an entry module 345, end module 348 and one or more other modules 346, or, similar to the Jurisdiction Module, may have only one module therein. It will be appreciated that any of the code blocks 344 may also have two modules and thus only an entry and end module 345, 348. A chained verification sequence may be employed to authenticate the contents of the entire system implicitly and at the same time, by feeding the output of one component into an input to the next component and comparing an output to the original input when the entire chain sequence has been performed. 1001591 The system shown in Figure 28 includes a ROM 340 which contains a verification agent 342 for performing the chained verification sequence, and the Input. As can be seen, the Input is used to recover a value A from the Entry Module in Code Block 1 by operating the recovery function 228 (for performing a message recovery operation - e.g. using ECPVS), which is then used to recover A from every other module 346. The value A is then used to recover B from the End Module, which is then used in the chain for the next component, Code Block 2. The value B is used to recover a value C from the Entry Module in Code Block 2, which is then used to recover C from each and every other module 346. The value C is then used to recover a value D from the End Module. The value D is then fed 6326233_1 -38into the next code block 344 and ultimately, a value D' is used in the final Code Block M to recover a value E. Value E is used to recover value E from every other module 346 in Code Block M, and then to recover the output from the End Module in Code Block M. [001601 It can be seen that, in the general embodiment, the use of a recovery function 528 that permits one to specify the recoverable portion, which then enables one to predictably sign each module such that they can be linked to each other in a chain where the final Output is used to authenticate the entire system. The Output will be incorrect and not match the Input if any of the modules are compromised since the proper value will only be recovered if the proper inputs are used. By chaining the modules, any compromised code will cause incorrect values to propagate through the chain and the Output will be rejected. The chained verification described herein thus implicitly authenticates every code block 344 and every module therein based on the comparison of the Output to the Input at the end of the chain. This also enables all code blocks 344 to be authenticated at the same time. [001611 It will be appreciated that the generic embodiment shown in Figure 28 can also utilize a keyed hash (e.g. HMAC) to enable the efficiencies exemplified in the example for authenticating the gaming machine 500. It will also be appreciated that the general embodiment may utilize the same principles on a plurality of code blocks 344 that each include only a single module wherein the value recovered from a signature for that one module is used as an input for recovering another value from the next module in the next code block. It can therefore be seen that the chained signature verification procedures shown herein can be adapted to suit numerous file structures and data storage schemes such that the recovered value from a signature on one code block is used as an input to a verification function on the signature of the next code block, to recover another value. The chain is built to include every code block that is desired to be protected and the final recovered output should be the same as the input for an authentic set of data. [001621 Although the has above examples have been described with reference to certain specific embodiments, various modifications thereof will be apparent to those skilled in the art. 6326233_1 -39-

Claims (11)

1. A method for securing content to be used by a device comprising: preparing an encrypted image by encrypting at least a portion of said content such that said portion can be recovered by decrypting said encrypted image using a key; storing said encrypted image on said device; obtaining information unique to said device; generating a signature using said information unique to said device to bind said encrypted image to said device, said signature encrypting said key such that said key is recoverable from said signature using said information unique to said device; and storing said signature on said device to enable said device to recover said key from said signature by determining said information unique to said device and providing said information unique to said device as an input to a signature verification function, wherein an output of said signature verification function corresponds to said key thereby enabling said device to decrypt said encrypted image to obtain said portion.

2. The method according to claim 1 wherein said signature is an elliptic curve Pintsov-Vanstone (ECPV) signature with said information unique to said device corresponding to a visible message and said key being recoverable using a first signature component and said information unique to said device to generate a decryption key for decrypting said first signature component.

3. The method according to claim 1, said device comprising a hardware board storing said content, said hardware board comprising a basic input output system (BIOS) and said content comprising a boot portion, an application portion and a data portion, and wherein said signature is stored on said BIOS and accessed during a boot up sequence of said boot portion to recover said key. 9228994 1 -41

4. The method according to claim 3 wherein said encrypted image and said signature are added to said hardware board using a binding machine during a binding operation for said hardware board, said binding machine obtaining said information unique to said device and providing said information to a trusted third party to enable said trusted third party to prepare said signature; said binding machine receiving said signature, preparing said encrypted image, writing said encrypted image to said hardware board, and flashing said BIOS to include said signature.

5. A method for authenticating content to be used for operating a device, the method comprising: obtaining a signature stored on said device, said signature encrypting a key that can be recovered therefrom; obtaining information unique to said device; recovering said key from said signature by providing said information unique to said device as an input to a signature verification function, wherein said key is an output to said signature verification function; using said key to decrypt an encrypted image of at least a portion of said content to recover said portion, said encrypted image having been stored on said device; and using said portion in operating said device, wherein if said portion is operable, said content is implicitly authenticated.

6. The method according to claim 5 wherein said signature is an ECPV signature with said information unique to said device corresponding to a visible message and said key being recovered using a first signature component and said information unique to said device to generate a decryption key and decrypting said first signature component to obtain said key using said decryption key.

7. The method according to claim 5, said device comprising a hardware board storing said content, said hardware board comprising a BIOS and said content comprising a boot portion, an application portion and a data portion, and wherein said 9228994 1 -42 signature is stored in, and obtained from said BIOS and accessed during a boot up sequence of said boot portion to recover said key.

8. The method according to claim 1 or 5 wherein said information unique to said device comprises at least one hardware serial number to bind said signature to said hardware board.

9. The method according to claim 1 or 5 wherein said device is a gaming machine.

10. A computer readable medium comprising computer executable instructions for performing the method according to any one of claims 1 to 9.

11. A device comprising a processor and a memory, said processor operable to perform the method according to any one of claims 1 to 9. Certicom Corp. Patent Attorneys for the Applicant SPRUSON & FERGUSON 9228994 1