1. Technical Field This disclosure relates to an information processing apparatus, a software update method, and an image processing apparatus, and more specifically to an information processing apparatus or an image processing apparatus having a primary module and a backup module, and a software update method of the information processing apparatus or the image processing apparatus.
2. Description of the Related Art
As security becomes increasingly critical, information processing apparatuses such as personal computers and image processing apparatuses such as Multi Function Peripherals (MFP) capable of encrypting information stored in the apparatuses to avoid wiretapping have become available lately. For example, Patent Document 1 describes a PC adopting the specifications of Trusted Computing Platform Alliance (TCPA) in which information is encrypted using a Trusted Platform Module (TPM). The TPM is realized in a chip directly mounted on, for example, a motherboard.
On the other hand, to respond to a failure, for example, a duplexing system has been employed in information processing apparatuses such as personal computers and image processing apparatuses such as MFPs. Furthermore, to respond to a bug, a security hole, addition or modification of functions, the programs have also been updated in information processing apparatuses such as personal computers and image processing apparatuses such as MFPs (see, for example, Patent Document 2).
Herein, a conventional method of encrypting and decrypting information using the TPM, and a program update (hereinafter referred to as “ROM update”) are briefly described.
The BIOS ROM 2 stores a Basic Input/Output System (BIOS) 10 module. The disk 3 stores a loader 11, a kernel 12, and a root file system (Rootfs) 13 modules. The NVRAM 4 stores plain text data 14 that users use.
The root file system 13 manages a boot program 21, a ROM update flag control program 22, a blob decryption section 23, and an application 24 that are stored in the disk 3. It should be noted that each of the BIOS 10, the loader 11, the kernel 12, the root file system 13 modules and the like is loaded into the main memory 5 to be executed. In the following, the BIOS 10, the loader 11, the kernel 12, the root file system 13 modules and the like are described as processing subjects.
A boot sequence of the information processing apparatus in
In step S6, the kernel 12 boots the boot program 21 in the root file system 13. In step S7, the boot program 21 boots the application 24 in the root file system 13. In step S8, the application 24 is now capable of writing data into the NVRAM 4 and reading, for example, plain data 14 in the NVRAM 4.
Next, a mechanism of the TPM is briefly described. In the following, an example where the loader 11 boots the kernel 12 is described.
In this manner, when the TPM 7 boots, for example, the BIOS 10, the loader 11, the kernel 12 and the root file system 13 modules, the TPM 7 stores hash values calculated from the modules in the PCRs.
In the Blob A 41, a value “0x3a” is stored in the “PCR3”. In the Blob B 42, values “0xe9”, “0x12”, “0x3b”, and “0x06” are stored in the “PCR1” through the “PCR4”, respectively. In the TPM7, values “0xe9”, “0x12”, “0x3a”, and “0x06” are stored in its “PCR1” through the “PCR4”, respectively.
In case of Blob A 41, the same hash value is in the “PCR3” of the Blob A 41 and the “PCR3” of the TPM 7. Therefore, the TPM 7 permits taking the information from the Blob A 41. In case of Blob B 42, a hash value in the “PCR3” of the Blob A 41 is different from that in the “PCR3” of the TPM 7. Therefore, the TPM 7 does not permit taking the information from the Blob A 41. It should be noted that when “no setting” may be stored in, for example, the “PCR1”, the “PCR2”, and the “PCR4” in the Blob A 41, the TPM 7 does not use the register to determine whether to permit taking the information.
The configuration of the information processing apparatus in
The NVRAM 4 stores encrypted data 15 in addition to the plain text data 14. The HDD 8 stores encrypted data 16. The same reference numerals are used in the figure to describe those components that are identical to the components of
A boot sequence of the information processing apparatus in
In step S24, the loader 11 loads the kernel 12. In step S25, a hash value of the kernel 12 is stored in a PCR of the TPM 7. In step S26, the loader 11 loads the root file system 13. In step 27, a hash value of the root file system is stored in a PCR of the TPM 7.
In step S28, the loader 11 boots the kernel 12 and the root file system 13. In step S29, the kernel 12 boots the boot program 21 in the root file system 13. In steps 30 and 31, the boot program 21 boots the blob decryption section 23 and the application 24 in the root file system 13.
In step S32, the blob decryption section 23 acquires the encryption key 51 for the NVRAM 4 from inside the Blob 43. In step S33 by using the encryption key, the application is now capable of writing encrypted data into the NVRAM 4 and reading encrypted data 14 stored in the NVRAM 4.
Patent Document 1: Japanese Patent Application Publication No. 2004-282391
Patent Document 2: Japanese Patent Application Publication No. 2005-196745
However, in an information processing apparatus having a configuration as shown in
Unfortunately, in a conventional information processing apparatus, when an update process from the Blob A 43 to the Blob A 43a is interrupted due to some reason, the hash value stored in the “PCR1” of the TPM 7 may become different from the hash value stored in the “PCR1” of the Blob A 43a. A problem arises that when the hash value stored in the “PCR1” of the TPM 7 becomes different from the hash value stored in the “PCR1” of the Blob A 43a, in that the encryption key 51 for the NVRAM 4 cannot be taken from the Blob 43a, resulting in that the encrypted data stored in the NVRAM 4 cannot be decrypted.
This problem illustrated in
It should be noted that the BIOS 10, the loader 11, the kernel 12, and the root file system 13 are included in primary modules, and the BIOS 10b, the loader 11b, the kernel 12b, and the root file system 13b are included in backup modules.
Typically, an information processing apparatus is booted sequentially in an order of the BIOS 10, the loader 11, the kernel 12, and the root file system 13. Hereinafter, a procedure of booting like this is referred to as a “boot path”. In the example of
That is, in an information processing apparatus having the backup system 82, when a module of the primary system has a problem, the same kind of module in the backup system 82 can usually be booted.
A booth path can be changed by, for example, a ROM update flag control program.
Because of this structure, there is a problem that the same number of Blobs which is equal to the number of booth paths defined by the combination of the modules in the primary system 81 and the modules in the backup system 82 are required to be provide.
Further, there is another problem in an information processing apparatus having a configuration as shown in
As described, when a conventional system is arranged to employ a duplex system having both a primary system and a backup system, have a ROM update capability, and improve the security by adding both an encryption and a decryption capability of information by using the TPM 7, it takes a lot of effort to manage the Blobs 73.
In an aspect of this disclosure, there is provided an information processing apparatus, a method of software update, and an image processing apparatus capable of encrypting and decrypting information using values uniquely calculated from a booted primary module and a booted backup module with much ease.
In another aspect, there is provided an information processing apparatus including one or more kinds of primary modules necessary to boot the apparatus and one or more kinds of backup modules to be used when the primary modules fail, so that the information processing apparatus is booted in a manner that when any kind of the primary modules fails, the same kind of backup module is used. The information. processing apparatus includes a value storage unit storing values uniquely calculated from the one or more kinds of the primary modules or the backup modules used when the apparatus is booted, an encryption information storage unit storing information unique to the each kind of the primary or the backup modules, the information being encrypted based on a value calculated from the each kind of the primary modules or the backup modules, an information decryption unit decrypting the information unique to the each kind of the primary modules or the backup modules using the values in the value storage unit, the information being stored in the encryption information storage unit, and an encryption information update unit, when any of the primary modules or the backup modules is updated, encrypting the information unique to the each kind of the primary modules or the backup modules based on a value calculated from the each kind of the primary modules or the backup modules after the update, the information being stored in the encryption information storage unit.
Further, in yet another aspect, there is provided an image processing apparatus including one or more kinds of primary modules necessary to boot the apparatus, one or more kinds of backup modules to be used when the primary modules fail, a plotter section and scanner section so that the plotter and the scanner sections are booted in a manner that when any kind of the primary modules fails, the same kind of backup module is used. The image processing apparatus includes a value storage unit storing values uniquely calculated from the one or more kinds of the primary modules or the backup modules used when the apparatus is booted, an encryption information storage unit storing information unique to the each kind of the primary or the backup modules, the information being encrypted based on a value calculated from the each kind of the primary modules or the backup modules, an information decryption unit decrypting the information unique to the each kind of the primary modules or the backup modules using the values in the value storage unit, the information being stored in the encryption information storage unit, and an encryption information update unit, when any of the primary modules or the backup modules is updated, encrypting the information unique to the each kind of the primary modules or the backup modules based on a value calculated from the each kind of the primary modules or the backup modules after the update, the information being stored in the encryption information storage unit.
It should be noted that a method, apparatus, system, computer program, recording medium, data structure including a constitutional element, an expression, or a combination of the aforementioned aspects and/or features may be included in any of various exemplary embodiments of the present invention.
According to an exemplary embodiment, there may be provided an information processing apparatus, a method of software update, and/or an image processing apparatus capable of encrypting and decrypting information using values uniquely calculated from a booted primary module and a booted backup module with less efforts.
The aforementioned and other aspects, features, and advantages would be better understood from the following detailed description when read in conjunction with the accompanying drawings, in which:
Next, best modes for carrying out the invention are described with reference to exemplary embodiments of the present invention and accompanying drawings. In the embodiments, an information processing apparatus such as a personal computer is described. However, the embodiment is not limited to such an information processing apparatus, and may be carried out in, for example, an image processing apparatus such as a Multi Function Peripheral (MFP).
[Embodiment 1 ]
The BIOS ROM 2 includes a BIOS 10 as a primary module and a BIOS 10b as a backup module. The NVRAM 4 stores plain text data 14 and encrypted data 15 that a user uses. The HDD 8 stores encrypted data 16.
The Blob 60a includes an encrypted key “A”. The Blob 60b includes an encrypted key “B”. The Blob 60c includes an encrypted key “C”. The Blob 60d includes an encrypted key “D”. The Blob 60e includes an encrypted key “A”. The Blob 60f includes an encrypted key “B”. The Blob 60g includes an encrypted key “C”. The Blob 60h includes an encrypted key “D”.
As a result, the Blob 60a and the Blob 60e have the same key “A”, the Blob 60b and the Blob 60f have the same key “B”, the Blob 60c and the Blob 60g have the same key “C”, and the Blob 60d and the Blob 60h have the same key “D”.
Further, hash values calculated based on a calculation method of generating a fixed-length pseudo random number from the BIOS 10 and 10b are stored into each “PCR1” of the Blobs 60a and 60e, respectively. In the same manner, the hash values calculated from the loader 11 and 11b are stored into each “PCR2” of the Blobs 60b and 60f, respectively. The hash values calculated from the kernel 12 and 12b are stored into each “PCR3” of the Blobs 60c and 60g, respectively. The hash values calculated from the root file system 13 and 13b are stored into each “PCR4” of the Blobs 60d and 60h, respectively.
With the configuration where Blobs 60a through 60h are provided as shown in
The root file system 13 manages a boot program 21, a ROM update flag control program 22, a blob decryption section 23, an application 24, a blob update program 25, and an encryption key update program 26 that are stored in the disk 3.
The boot program 21 boots the application 24 in the root file system 13. The ROM update flag control program 22 controls the boot path defining a boot flow. The blob decryption section 23 acquires the keys “A” through “D” from the Blobs 60a through 60h using the TPM 7. The blob update program 25 controls the update of the Blobs 60a through 60h. The encryption key update program 26 controls the update of the encryption key 62 for the NVRAM 4.
Referring back to
That is, the hash value calculated from the BIOS 10 or 10b is stored in the “PCR1” of the TPM 7; the hash value calculated from the loader 11 or 11b is stored in the “PCR2” of the TPM 7; the hash value calculated from the kernel 12 or 12b is stored in the “PCR3” of the TPM 7; and the hash value calculated from the root file system 13 or 13b is stored in the “PCR4” of the TPM 7.
The modules including the BIOS 10 and 10b, the loader 11 and 11b, the kernel 12 and 12b, and the root file system 13 and 13b are loaded into the main memory by the CPU 1 and executed. In the following descriptions, the modules including the BIOS 10 and 10b, the loader 11 and 11b, the kernel 12 and 12b, and the root file system 13 and 13b are described as processing subjects, for explanation purposes.
Next, a boot sequence of the information processing apparatus in
In step S41, BIOS loads the loader 11. In step S42, the hash value of the loader 11 is stored in the “PCR2” of the TPM 7. In step S43, the BIOS boots the loader 11.
In step S44, the loader 11 loads the kernel 12. In step S45, the hash value of the kernel 12 is stored in the “PCR3” of the TPM 7. In step S46, the loader loads the root file system 13. In step S47, the hash value of the root file system 13 is stored in the “PCR4” of the TPM 7.
In step S48, the loader 11 boots the kernel 12 and the root file system 13. In step S49, the kernel 12 boots the boot program 21 in the root file system 13. In steps S50 and S51, the boot program 21 boots the blob decryption section 23 and the application 24, respectively, in the root file system 13.
In step S52, the blob decryption section 23 acquires the keys “A” through “D” from the blobs 60a through 60d, respectively, using the TPM 7. In step S53, the blob decryption section 23 decrypts the encrypted encryption key 62 for the NVRAM 4 using the acquired keys “A” through “D”. In step S54, the application is now capable of writing encrypted data 15 into the NVRAM 4 and reading encrypted data in the NVRAM 4 using the decrypted encryption key 62.
In the following, a specific process of ROM update and encryption key update in the information processing apparatus in
(ROM Update)
In step S61, the kernel 12 is replaced by the new kernel 12b. In step S62, the blob decryption section 23 acquires the key “C” from the Blob 60c using the TPM 7 in the same manner as described above.
In step S63, the blob update program 25 generates a hash value calculated from the new kernel 12a. In step S64, the blob update program 25 generates a new Blob 60i including the generated hash value. In step S65, the blob update program 25 replaces the Blob 60c by the generated Blob 60i. Then, the ROM update flag control program 22 restores the boot path to BIOS 10→loader 11→kernel 12→root file system 13.
During the process of the ROM update shown in
(Encryption Key Update)
In step S74, the blob decryption section 23 decrypts the encrypted encryption key 62 using the keys “A” through “D”, and acquires the decrypted encryption key 62. In step S75, the encryption key update program 26 decrypts the encrypted data 15 stored in the NVRAM 4 using the decrypted encryption key 62. In step S76, the encryption key update program 26 encrypts the decrypted encrypted data 15 again using the new encryption key 62a for the NVRAM 4.
In step S77, the encryption key update program 26 deletes the encrypted data 15 stored in the disk 3 as a backup copy in step S71. In step S78, the encryption key update program 26 further deletes the encrypted encryption key 62 for the NVRAM 4 stored in the disk 3.
During the above process of the encryption key update shown in
(Another Configuration of the Disk 3)
The Blob 60a includes the encrypted key “A”.
The Blob 60b includes the encrypted key “B”. The Blob 60c includes the encrypted key “C”. The Blob 60e includes the encrypted key “A”. The Blob 60f includes the encrypted key “B”. The Blob 60g includes the encrypted key “C”. The Blob 60j includes the encrypted encryption key 62 for the NVRAM4, the encryption key 62 being encrypted using the keys “A” through “C”. The Blob 60k includes the encrypted encryption key 62 for the NVRAM4, the encryption key 62 being encrypted using the keys “A” through “C”.
That is, the module configuration in
[Embodiment 2]
In the information processing apparatus in above embodiment, should the disk 3 crash, since the encryption key 62 for the NVRAM 4 is to be lost, the encrypted data 15 in the NVRAM 4 can no longer be decrypted. To solve this problem, in an information processing apparatus according to this embodiment 2, a mechanism may be provided that permits decrypting the encrypted data 15 in the NVRAM 4 even when the disk 3 crashes.
In the information processing apparatus in this embodiment 2, the module configuration of the disk 3 and the information stored in the NVRAM 4 and the HDD 8 are different from those in embodiment 1.
The Blob 60a includes the encrypted key “A”. The Blob 60b includes the encrypted key “B”. The Blob 60c includes the encrypted key “C”. The Blob 60d includes the encrypted key “D”. The Blob 601 includes the encrypted encryption key 62 for the NVRAM 4.
In this configuration, the encryption key 62 for the NVRAM 4 can be decrypted and obtained using the keys “A” through “D” from the Blobs 60a through 60d, respectively, and can be obtained from the Blob 601 corresponding to the boot path of BIOS 10b→loader 11b→kernel 12b→root file system 13b.
Further, in the information processing apparatus in this embodiment 2, the Blob 601 is stored in the NVRAM 4 and the HDD 8 as shown in
In step S82, the ROM update flag control program 22 turns ON a backup flag 71 in the encrypted data 15 in the NVRAM 4. In step S83, the information processing apparatus reboots in a backup mode.
In step S84, the information processing apparatus boots the loader 11b, the kernel 12b, the root file system 13b (backup mode). In step S85, the blob update program 25 creates a copy of the Blob 601 stored in the NVRAM 4 and stores the created copy in the disk 3. In step S86, the blob update program creates new keys “A” through “D”.
In step S87, the blob update program 25 creates Blobs 80a through 80d including the keys “A” through “D”, respectively. In step S88, the blob update program 25 stores the created blobs 80a through 80d in the disk 3. In step S89, the blob decryption section 23 acquires the encryption key 62 from the Blob 601 stored in the NVRAM 4.
In step S90, the encryption key update program 26 encrypts the encryption key 62 using the keys “A” through “D” and stores the encrypted encryption key 62 in the disk 3. In step S91, the ROM update flag control program 22 turns OFF the backup flag 71 in the encrypted data 15 in the NVRAM 4.
In the process shown in
The present invention is not limited to the above-mentioned embodiments, and variations and modifications may be made without departing from the scope of the present invention.
It should be noted that the terms “value storage unit”, “encryption information storage units”, “information decryption unit”, and “encryption information update unit” described in claims herein correspond to the TPM 7, the Blobs 60a through 60l, the blob decryption section 23, and the blob update program 25, respectively.
The present application is based on and claims the benefit of priority of Japanese Patent Application No. 2007-067250, filed on Mar. 15, 2007, the entire contents of which are hereby incorporated by reference.
Number | Date | Country | Kind |
---|---|---|---|
2007-067250 | Mar 2007 | JP | national |
Number | Name | Date | Kind |
---|---|---|---|
6185678 | Arbaugh et al. | Feb 2001 | B1 |
6378072 | Collins et al. | Apr 2002 | B1 |
7194092 | England et al. | Mar 2007 | B1 |
7467328 | Roth et al. | Dec 2008 | B2 |
20020073316 | Collins et al. | Jun 2002 | A1 |
20030046524 | Zimmer et al. | Mar 2003 | A1 |
20030194094 | Lampson et al. | Oct 2003 | A1 |
20030196085 | Lampson et al. | Oct 2003 | A1 |
20030196099 | Lampson et al. | Oct 2003 | A1 |
20030196110 | Lampson et al. | Oct 2003 | A1 |
20030200454 | Foster et al. | Oct 2003 | A1 |
20050131990 | Jewell | Jun 2005 | A1 |
20050149746 | Lu et al. | Jul 2005 | A1 |
20050268115 | Barde et al. | Dec 2005 | A1 |
20060005252 | Chu et al. | Jan 2006 | A1 |
20060021064 | England et al. | Jan 2006 | A1 |
20060041572 | Maruyama | Feb 2006 | A1 |
20060129520 | Lang | Jun 2006 | A1 |
20060174240 | Flynn | Aug 2006 | A1 |
20060200663 | Thornton | Sep 2006 | A1 |
20060248162 | Kawasaki | Nov 2006 | A1 |
20060265562 | Nishiguchi et al. | Nov 2006 | A1 |
20070043972 | Graham et al. | Feb 2007 | A1 |
20070083759 | Drew et al. | Apr 2007 | A1 |
20070094719 | Scarlata | Apr 2007 | A1 |
20070169098 | Kikuchi | Jul 2007 | A1 |
20070239774 | Bodily et al. | Oct 2007 | A1 |
20070250673 | Eidswick | Oct 2007 | A1 |
20070260775 | Bita et al. | Nov 2007 | A1 |
20070268818 | Sugihara | Nov 2007 | A1 |
20080060662 | Oh et al. | Mar 2008 | A1 |
20080208923 | Watanabe et al. | Aug 2008 | A1 |
Number | Date | Country |
---|---|---|
2004-282391 | Oct 2004 | JP |
2005-196745 | Jul 2005 | JP |
9939475 | Aug 1999 | WO |
Entry |
---|
Sep. 25, 2008 search report in connection with a counterpart European patent application No. 08 15 2627. |
Number | Date | Country | |
---|---|---|---|
20080229114 A1 | Sep 2008 | US |