US20060031665A1 - Authentications integrated into a boot code image - Google Patents
Authentications integrated into a boot code image Download PDFInfo
- Publication number
- US20060031665A1 US20060031665A1 US11/200,468 US20046805A US2006031665A1 US 20060031665 A1 US20060031665 A1 US 20060031665A1 US 20046805 A US20046805 A US 20046805A US 2006031665 A1 US2006031665 A1 US 2006031665A1
- Authority
- US
- United States
- Prior art keywords
- boot code
- authentication
- terminals
- binary executable
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 claims abstract description 28
- 238000004590 computer program Methods 0.000 claims abstract description 18
- 238000009434 installation Methods 0.000 claims description 8
- FTGYKWAHGPIJIT-UHFFFAOYSA-N hydron;1-[2-[(2-hydroxy-3-phenoxypropyl)-methylamino]ethyl-methylamino]-3-phenoxypropan-2-ol;dichloride Chemical compound Cl.Cl.C=1C=CC=CC=1OCC(O)CN(C)CCN(C)CC(O)COC1=CC=CC=C1 FTGYKWAHGPIJIT-UHFFFAOYSA-N 0.000 description 14
- 230000008859 change Effects 0.000 description 9
- 230000006870 function Effects 0.000 description 6
- -1 flash ROM Chemical compound 0.000 description 5
- 230000008520 organization Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002207 retinal effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- G06F21/572—Secure firmware programming, e.g. of basic input output system [BIOS]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- G06F21/575—Secure boot
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4416—Network booting; Remote initial program loading [RIPL]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
Definitions
- the present invention relates to the field of enterprise networks, and more particularly to storing and updating authentications, e.g., passwords, authentication numbers, in a boot code image, i.e., binary executable boot code, in each terminal in an enterprise network from a central site by system administrators.
- authentications e.g., passwords, authentication numbers
- boot code image i.e., binary executable boot code
- An enterprise network may refer to a geographically dispersed network under the jurisdiction of one organization.
- an enterprise network may comprise a main server at a central location, e.g., headquarters, coupled to a plurality of intermediate servers where each intermediate server may be located at a geographically separate location from the main server.
- Each intermediate server may represent a particular location, e.g., store, of an organization.
- Each intermediate server may then be coupled to a plurality of terminals, e.g., cash registers, personal computers, at that particular location.
- Each terminal may be equipped with a BIOS (Basic Input/Output System) based password program.
- BIOS Basic Input/Output System
- a BIOS based password program may run before control of the terminal is given to any disk based software. This may prevent an unauthorized user from accessing data by starting the terminal from a floppy disk or using other means to change the disk based software.
- the BIOS based password program may issue a password prompt that appears on the monitor. If the correct password is not entered, the system will not boot. It is noted that the BIOS based password program may further request a separate password primarily for system administrators to access the setup options, e.g., BIOS setup options, of the terminal. If the correct password is not entered, access to the setup options will be denied.
- passwords such as passwords to protect unauthorized users from booting the system and accessing setup options are stored in non-volatile Random Access Memory (RAM).
- RAM non-volatile Random Access Memory
- a user at a terminal may be able to change or modify the password which may not be desirable. Users may accidentally or maliciously change the password which may result in untoward consequences such as not being able to boot up the terminal if the user cannot remember the new password.
- the system administrative staff at the central site e.g., headquarters, may have difficulty assisting the user as they may not know the new password since the user and not the system administrators at the central site changed the password.
- authentications e.g., password to protect unauthorized users from booting the system
- password to protect unauthorized users from accessing setup options
- an authentication number to permit installation of software, within a boot code image, i.e., binary executable boot code, at a terminal, e.g., cash register, personal computer, stored in Read Only Memory (ROM), e.g., flash ROM, thereby preventing the user at the terminal from tampering authentications.
- ROM Read Only Memory
- an authentication e.g., password to protect unauthorized users from booting the system
- password to protect unauthorized users from accessing setup options
- an authentication number to permit installation of software
- a boot code image i.e., binary executable boot code such as BIOS binary executable code, stored in Read Only Memory (ROM), e.g., flash ROM
- ROM Read Only Memory
- the authentication in the boot code image may be stored or updated from a remote central site as described in greater detail below, thereby allowing system administrators at the central site to have knowledge of the current authentication installed at the terminal.
- Each terminal may comprise a boot code image where a portion of the boot code image may be allocated for storing an authentication.
- the authentication stored in that boot code image may be updated, e.g., password may be changed.
- One or more terminals coupled to a server at the central site may then be identified as storing an authentication in their boot code image that needs to be updated.
- the authentication in the boot code image in each of the one or more terminals identified may then be updated.
- a method for storing authentications, e.g., authentication number to install software, within a boot code image, i.e., binary executable boot code, in ROM, e.g., flash ROM, in a terminal from a remote central site may comprise the step of creating a file comprising a boot code image where the boot code image may comprise an authentication, e.g., authentication number to install software.
- the file may be created at a central site geographically separate from the location of one or more terminals to receive the file.
- One or more terminals coupled to the server at the central site may then be identified to store the file created.
- the file created may then be saved in ROM, e.g., flash ROM, in each of the one or more terminals identified.
- the file may be downloaded from the server at the central site to each of the one or more terminals identified via a network, e.g., LAN, WAN.
- the file may be stored on a storage medium, e.g., magnetic disk, compact disc, which may then be loaded onto the one or more terminals identified.
- FIG. 1 illustrates an embodiment of the present invention of an enterprise network system
- FIG. 2 illustrates an embodiment of the present invention of a terminal in an enterprise network
- FIG. 3 illustrates an embodiment of the present invention of a memory in a terminal configured to store a boot code image comprising an authentication
- FIG. 4 illustrates an embodiment of the present invention of a server in an enterprise network
- FIG. 5 is a flowchart of a method for updating authentications within a boot code image in a terminal from a central site.
- FIG. 6 is a flowchart of a method for storing authentications in the boot code image in a terminal from a central site.
- FIG. 1 Enterprise System
- FIG. 1 illustrates an embodiment of the present invention of an enterprise system 100 .
- Enterprise system 100 may comprise a main server 101 located at a central site, e.g., headquarters.
- Main server 101 may be coupled to one or more intermediate servers 102 A-C located at a geographically separate location from main server 101 .
- Intermediate servers 102 A-C may collectively or individually be referred to as intermediate servers 102 or intermediate server 102 , respectively.
- Each intermediate server 102 may be coupled to a plurality of terminals, e.g., cash registers, personal computers, at the location serviced by that intermediate server 102 .
- intermediate server 102 A may be coupled to terminals 103 A-C.
- Intermediate server 102 B may be coupled to terminals 103 D-F.
- Intermediate server 102 C may be coupled to terminals 103 G-I.
- Terminals 103 A-H may collectively or individually be referred to as terminals 103 or terminal 103 , respectively.
- enterprise system 100 may comprise any number of main servers 101 coupled to any number of intermediate servers 102 coupled to any number of terminals 103 .
- the connections between main server 101 and intermediate servers 102 and the connections between intermediate servers 102 and terminals 103 may be any medium type, e.g., wireless, wired.
- enterprise system 100 may comprise a greater or fewer number of hierarchical levels of servers than illustrated and that FIG. 1 is illustrative.
- FIG. 2 Hardware Configuration of Terminal
- FIG. 2 illustrates an embodiment of the present invention of terminal 103 .
- Terminal 103 may comprise a processor 201 coupled to various other components by a bus 202 .
- An operating system 203 may run on processor 201 and provide control as well as coordinate the function of the various components of FIG. 2 .
- Application 204 may run in conjunction with operating system 203 which implements the various functions to be performed by application 204 .
- Terminal 103 may further comprise a read only memory (ROM) 205 , e.g., flash ROM, coupled to bus 202 and may include a boot code image, i.e., binary executable boot code, that controls certain basic functions of terminal 103 as illustrated in FIG. 3 .
- ROM read only memory
- FIG. 3 illustrates an embodiment of the present invention of ROM 205 , e.g., flash ROM.
- ROM 205 may store boot code image 301 , i.e., binary executable boot code such as BIOS binary executable code.
- a portion of boot code image 301 may be allocated for storing authentication 302 , e.g., password to protect unauthorized users from booting the system, password to protect unauthorized users from accessing setup options, an authentication number to permit installation of software, an authentication to permit operation of software.
- authentication 302 may be encrypted.
- Authentication 302 may be encrypted using various encryption schemes that would be recognized by a person of ordinary skill in the art and that such embodiments employing such schemes would fall within the scope of the present invention.
- boot cod image 301 may be configured to store more than one authentication 302 and that FIG. 3 is illustrative.
- RAM 206 Random Access Memory (RAM) 206 , Input/Output (I/O) adapter 207 and communications adapter 208 may also coupled to bus 202 .
- software components including operating system 203 and application 204 may be loaded into RAM 206 which may be terminal's 103 main memory.
- I/O adapter 207 may be an integrated drive electronics (“IDE”) adapter that communicates with a storage medium 209 , e.g., disk drive.
- IDE integrated drive electronics
- Communications adapter 208 may interconnect bus 202 with an outside network enabling terminal 103 to communicate with main server 101 , intermediate server 102 via a Local Area Network (LAN), e.g., Ethernet, Token Ring, ARCnet, or a Wide Area Network (WAN), e.g., Internet.
- LAN Local Area Network
- ARCnet Token Ring
- WAN Wide Area Network
- Terminal 103 may further comprise Input/Output (I/O) devices that may be coupled to bus 202 via a user interface adapter 210 and a display adapter 211 .
- Keyboard 212 and biometric device 214 e.g., fingerprint reader, retinal scanner, may be interconnected to bus 202 through user interface adapter 210 .
- a display device 213 may be coupled to bus 202 through display adapter 211 .
- Biometric device 214 may be used to authenticate the user at terminal 103 thereby establishing that the user is authorized to access that particular terminal 103 . It is noted that there are numerous types of input devices and display devices known to those skilled in the art and thus need not be described in detail herein.
- Implementations of the invention include implementations as a terminal programmed to execute the method or methods described herein, and as a computer program product.
- sets of instructions for executing the method or methods may be resident in the random access memory 206 of one or more terminal systems configured generally as described above.
- the set of instructions may be stored as a computer program product in another memory, for example, in storage medium 209 (which may include a removable memory such as an optical disk or floppy disk for eventual use in the storage medium 209 ).
- the computer program product may also be stored at another computer such as another terminal 103 or intermediate server 102 or main server 101 and transmitted when desired to the user's terminal 103 by a network or by an external network such as the Internet.
- the physical storage of the sets of instructions physically changes the medium upon which it is stored so that the medium carries computer readable information. The change may be electrical, magnetic, chemical, biological or some other physical change.
- FIG. 4 Hardware Configuration of Servers
- FIG. 4 illustrates an embodiment of the present invention of main server 101 , intermediate server 102 .
- main server 101 , intermediate server 102 may comprise a central processing unit (CPU) 410 coupled to various other components by system bus 412 .
- An operating system 430 runs on CPU 410 and provides control and coordinates the function of the various components of FIG. 4 .
- An application 440 in accordance with the principles of the present invention may run in conjunction with operating system 430 and provide calls to operating system 430 where the calls implement the various functions or services to be performed by application 440 .
- An application 440 of main server 101 may include, for example, a program for updating authentications 302 , e.g., passwords, authentication numbers, within boot code image 301 , i.e., binary executable boot code, stored in ROM 205 at terminal 103 from a remote central site as described in the description of FIG. 5 , a program for storing authentications 302 , e.g., passwords, authentication numbers, within boot code image 301 stored in ROM 205 at terminal 103 from a remote central site as described in FIG. 6 .
- Read only memory (ROM) 416 may be coupled to system bus 412 and include a basic input/output system (“BIOS”) that controls certain basic functions of main server 101 , intermediate server 102 .
- BIOS basic input/output system
- Random access memory (RAM) 414 , disk adapter 418 and communications adapter 434 may also be coupled to system bus 412 . It should be noted that software components including operating system 430 and application 440 may be loaded into RAM 414 which is the computer system's main memory. Disk adapter 418 may be a small computer system interface (“SCSI”) adapter that communicates with disk units 420 , e.g., disk drive. It is noted that the program of the present invention that updates authentications 302 , e.g., passwords, authentication numbers, within boot code image 301 , i.e., binary executable boot code, stored in ROM 205 at terminal 103 from a remote central site as described in the description of FIG.
- authentications 302 e.g., passwords, authentication numbers
- boot code image 301 i.e., binary executable boot code
- LAN Local Area Network
- WAN Wide Area Network
- Implementations of the invention include implementations as a computer system programmed to execute the method or methods described herein, and as a computer program product.
- sets of instructions for executing the method or methods are resident in the random access memory 414 of one or more computer systems configured generally as described above.
- the set of instructions may be stored as a computer program product in another computer memory, for example, in disk drive 420 (which may include a removable memory such as an optical disk or floppy disk for eventual use in disk drive 420 ).
- the computer program product can also be stored at another computer and transmitted when desired to the user's workstation by a network or by an external network such as the Internet.
- the physical storage of the sets of instructions physically changes the medium upon which it is stored so that the medium carries computer readable information. The change may be electrical, magnetic, chemical or some other physical change.
- FIG. 5 Method for Updating Authentications within a Boot Code Image Stored in ROM in a Terminal from a Remote Central Site
- FIG. 5 is a flowchart of one embodiment of the present invention of a method 500 for updating authentications 302 , e.g., passwords, authentication numbers, within boot code image 301 , i.e., binary executable boot code such as BIOS binary executable code, stored in ROM, e.g., flash ROM, at terminal 103 from a remote central site.
- boot code image 301 i.e., binary executable boot code such as BIOS binary executable code
- ROM e.g., flash ROM
- FIG. 5 is a flowchart of one embodiment of the present invention of a method 500 for updating authentications 302 , e.g., passwords, authentication numbers, within boot code image 301 , i.e., binary executable boot code such as BIOS binary executable code, stored in ROM, e.g., flash ROM, at terminal 103 from a remote central site.
- BIOS binary executable boot code such as BIOS binary executable code
- ROM e
- authentications e.g., password to protect unauthorized users from booting the system, password to protect unauthorized users from accessing setup options, an authentication number to permit installation of software, an authentication to permit operation of software, within a boot code image, i.e., binary executable boot code, stored in ROM, e.g., flash ROM, at a terminal, e.g., cash register, personal computer, thereby preventing the user at the terminal from tampering authentications. It would further be desirable to update the authentications stored in the boot code image in each terminal from a central site, e.g., headquarters, thereby allowing system administrators the ability to know the current authentication installed at the terminal.
- Method 500 is a method for addressing the above concerns.
- a file associated with boot code image 301 ( FIG. 3 ), i.e., binary executable boot code such as BIOS binary executable code, to be updated in one or more terminals 103 ( FIG. 2 ) may be identified at a central site geographically separate from the location of the one or more terminals 103 to be updated as described below.
- each terminal 103 coupled to main server 101 may comprise a boot code image 301 .
- a portion of boot code image 301 may be allocated for storing authentication 302 , e.g., password to protect unauthorized users from booting the system, password to protect unauthorized users from accessing setup options, an authentication number to permit installation of software, an authentication to permit operation of software.
- a file associated with boot code image 301 to be updated in the one or more terminals 103 may be identified at a central site in step 501 .
- authentication 302 e.g., password to protect unauthorized users from booting the system, password to protect unauthorized users from accessing setup options, authentication number to permit installation of software, an authentication to permit operation of software, in boot code image 301 in the file identified in step 501 may be updated.
- authentication 302 in the file associated with boot code image 103 identified in step 501 may be updated without recompiling the entire file associated with boot code image 103 . That is, the bytes in the file associated boot code image 103 storing authentication 302 may be modified without modifying any other bytes of the file.
- one or more terminals 103 coupled to main server 101 may be identified as storing an authentication 302 in their boot code image 301 that needs to be updated.
- step 504 authentication 302 in boot code image 301 in each of the one or more terminals 103 identified in step 503 may be updated with authentication 302 updated in step 502 .
- the updated file may be downloaded from main server 101 to each of the one or more terminals 103 identified in step 503 via a network, e.g., LAN, WAN.
- the entire boot code image 301 stored in ROM 205 ( FIG. 2 ), e.g., flash ROM, in each of the one or more terminals 103 identified in step 503 may be updated.
- a utility program may be attached to the updated file that erases and writes to selected portions of boot code image 301 stored in ROM 205 , e.g., flash ROM, such as the portion storing authentication 302 . Subsequently, the portion storing authentication 302 in boot code image 301 stored in ROM 205 in each of the one or more terminals 103 identified in step 503 may be erased and written with the updated authentication 302 .
- the updated file may be stored on a storage medium, e.g., magnetic disk, compact disc, which may then be loaded onto the one or more terminals 103 identified in step 503 .
- the entire boot code image 301 stored in ROM 205 FIG.
- each of the one or more terminals 103 identified in step 503 may be updated.
- a utility program may be attached to the updated file that erases and writes to selected portions of boot code image 301 stored in ROM 205 such as the portion storing authentication 302 thereby installing the updated authentication 302 .
- a prompt may be displayed to each user of the one or more terminals 103 identified in step 503 indicating that authentication 302 has been updated.
- boot code image 301 may comprise code to indicate to the user of terminal 103 that authentication 302 has been updated upon updating authentication 302 .
- authentication 302 in boot code image 301 may be updated during the evening when terminal 103 is deactivated.
- the user may receive a prompt indicating that authentication 302 , e.g., password, has been updated and to enter the new authentication 302 , e.g., password.
- the user may enter the new authentication 302 thereby allowing the user to boot the system or to access setup options or to install software, etc.
- ROM 205 e.g., flash ROM
- each terminal 103 e.g., cash register, personal computer, in an enterprise network environment
- a user at terminal 103 may be prevented from tampering authentication 302 .
- a remote central site e.g., headquarters
- system administrators at the central site may have knowledge of the current authentication installed at terminal 103 .
- method 500 may be executed in a different order presented and that the order presented in the discussion of FIG. 5 is illustrative. It is further noted that certain steps may be executed almost concurrently. It is further noted that steps 501 - 504 may be implemented by a program in main server 101 residing in application 440 ( FIG. 4 ) or disk unit 420 ( FIG. 4 ).
- FIG. 6 Method for Storing Authentications within a Boot Code Image Stored in ROM in a Terminal from a Remote Central Site
- FIG. 6 is a flowchart of one embodiment of the present invention of a method 600 for storing authentications 302 , e.g., authentication number to install software, within boot code image 301 , i.e., binary executable boot code such as BIOS binary executable code, stored in ROM 205 at terminal 103 from a remote central site.
- authentications 302 e.g., authentication number to install software
- boot code image 301 i.e., binary executable boot code such as BIOS binary executable code
- a file may be created comprising a boot code image 301 ( FIG. 3 ), i.e., binary executable boot code, where boot code image 301 may comprise an authentication 302 , e.g., authentication number to install software.
- the file may be created at a central site geographically separate from the location of one or more terminals 103 to receive the file as described below.
- step 602 one or more terminals 103 coupled to main server 101 may be identified to store the file created in step 601 .
- the file may be saved in ROM 205 ( FIG. 2 ), e.g., flash ROM, in the one or more terminals 103 identified in step 602 .
- the file may be downloaded from main server 101 to each of the one or more terminals 103 identified in step 602 via a network, e.g., LAN, WAN.
- the file may be stored on a storage medium, e.g., magnetic disk, compact disc, which may then be loaded onto the one or more terminals 103 identified in step 602 .
- method 600 may be executed in a different order presented and that the order presented in the discussion of FIG. 6 is illustrative. It is further noted that certain steps may be executed almost concurrently.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
- Storage Device Security (AREA)
Abstract
Description
- The present application is a continuation application of pending U.S. patent application Ser. No. 10/001,697, which was filed on Oct. 31, 2001, which is assigned to the assignee of the present invention.
- The present invention relates to the field of enterprise networks, and more particularly to storing and updating authentications, e.g., passwords, authentication numbers, in a boot code image, i.e., binary executable boot code, in each terminal in an enterprise network from a central site by system administrators.
- An enterprise network may refer to a geographically dispersed network under the jurisdiction of one organization. For example, an enterprise network may comprise a main server at a central location, e.g., headquarters, coupled to a plurality of intermediate servers where each intermediate server may be located at a geographically separate location from the main server. Each intermediate server may represent a particular location, e.g., store, of an organization. Each intermediate server may then be coupled to a plurality of terminals, e.g., cash registers, personal computers, at that particular location.
- Each terminal may be equipped with a BIOS (Basic Input/Output System) based password program. A BIOS based password program may run before control of the terminal is given to any disk based software. This may prevent an unauthorized user from accessing data by starting the terminal from a floppy disk or using other means to change the disk based software. Each time the terminal is activated, the BIOS based password program may issue a password prompt that appears on the monitor. If the correct password is not entered, the system will not boot. It is noted that the BIOS based password program may further request a separate password primarily for system administrators to access the setup options, e.g., BIOS setup options, of the terminal. If the correct password is not entered, access to the setup options will be denied.
- Typically, passwords such as passwords to protect unauthorized users from booting the system and accessing setup options are stored in non-volatile Random Access Memory (RAM). By storing passwords in non-volatile RAM, a user at a terminal may be able to change or modify the password which may not be desirable. Users may accidentally or maliciously change the password which may result in untoward consequences such as not being able to boot up the terminal if the user cannot remember the new password. Furthermore, if the user at the terminal forgets the new password, the system administrative staff at the central site, e.g., headquarters, may have difficulty assisting the user as they may not know the new password since the user and not the system administrators at the central site changed the password. Furthermore, in an enterprise network environment, it may be difficult, cumbersome and time consuming to update passwords stored in terminals as each terminal may have different passwords from which to update which may not be known by the system administrators.
- It would therefore be desirable to store authentications, e.g., password to protect unauthorized users from booting the system, password to protect unauthorized users from accessing setup options, an authentication number to permit installation of software, within a boot code image, i.e., binary executable boot code, at a terminal, e.g., cash register, personal computer, stored in Read Only Memory (ROM), e.g., flash ROM, thereby preventing the user at the terminal from tampering authentications. It would further be desirable to store or update the authentications stored in the boot code image in each terminal from a remote central site, e.g., headquarters, thereby allowing system administrators at the central site the ability to know the current authentication installed at the terminal.
- The problems outlined above may at least in part be solved in some embodiments by storing an authentication, e.g., password to protect unauthorized users from booting the system, password to protect unauthorized users from accessing setup options, an authentication number to permit installation of software, within a boot code image, i.e., binary executable boot code such as BIOS binary executable code, stored in Read Only Memory (ROM), e.g., flash ROM, in a terminal. By storing an authentication in the boot code image stored in ROM, a user at the terminal may be prevented from tampering with the authentication. Furthermore, the authentication in the boot code image may be stored or updated from a remote central site as described in greater detail below, thereby allowing system administrators at the central site to have knowledge of the current authentication installed at the terminal.
- In one embodiment of the present invention, a method for updating authentications, e.g., passwords, authentication numbers, within a boot code image, i.e., binary executable boot code, stored in ROM, e.g., flash ROM, in a terminal from a remote central site may comprise the step of identifying a file with a boot code image comprising an authentication to be updated in one or more terminals. Each terminal may comprise a boot code image where a portion of the boot code image may be allocated for storing an authentication. Upon identifying a file with the boot code image to be updated in one or more terminals, the authentication stored in that boot code image may be updated, e.g., password may be changed. One or more terminals coupled to a server at the central site may then be identified as storing an authentication in their boot code image that needs to be updated. The authentication in the boot code image in each of the one or more terminals identified may then be updated.
- In another embodiment of the present invention, a method for storing authentications, e.g., authentication number to install software, within a boot code image, i.e., binary executable boot code, in ROM, e.g., flash ROM, in a terminal from a remote central site may comprise the step of creating a file comprising a boot code image where the boot code image may comprise an authentication, e.g., authentication number to install software. The file may be created at a central site geographically separate from the location of one or more terminals to receive the file. One or more terminals coupled to the server at the central site may then be identified to store the file created. The file created may then be saved in ROM, e.g., flash ROM, in each of the one or more terminals identified. In one embodiment, the file may be downloaded from the server at the central site to each of the one or more terminals identified via a network, e.g., LAN, WAN. In another embodiment, the file may be stored on a storage medium, e.g., magnetic disk, compact disc, which may then be loaded onto the one or more terminals identified.
- The foregoing has outlined rather broadly the features and technical advantages of one or more embodiments of the present invention in order that the detailed description of the invention that follows may be better understood. Additional features and advantages of the invention will be described hereinafter which form the subject of the claims of the invention.
- A better understanding of the present invention can be obtained when the following detailed description is considered in conjunction with the following drawings, in which:
-
FIG. 1 illustrates an embodiment of the present invention of an enterprise network system; -
FIG. 2 illustrates an embodiment of the present invention of a terminal in an enterprise network; -
FIG. 3 illustrates an embodiment of the present invention of a memory in a terminal configured to store a boot code image comprising an authentication; -
FIG. 4 illustrates an embodiment of the present invention of a server in an enterprise network; -
FIG. 5 is a flowchart of a method for updating authentications within a boot code image in a terminal from a central site; and -
FIG. 6 is a flowchart of a method for storing authentications in the boot code image in a terminal from a central site. -
FIG. 1 —Enterprise System -
FIG. 1 illustrates an embodiment of the present invention of anenterprise system 100. As stated in the Background Information section, an enterprise system may refer to a geographically dispersed network under the jurisdiction of one organization.Enterprise system 100 may comprise amain server 101 located at a central site, e.g., headquarters.Main server 101 may be coupled to one or moreintermediate servers 102A-C located at a geographically separate location frommain server 101.Intermediate servers 102A-C may collectively or individually be referred to as intermediate servers 102 or intermediate server 102, respectively. Each intermediate server 102 may be coupled to a plurality of terminals, e.g., cash registers, personal computers, at the location serviced by that intermediate server 102. For example,intermediate server 102A may be coupled toterminals 103A-C.Intermediate server 102B may be coupled toterminals 103D-F.Intermediate server 102C may be coupled toterminals 103G-I. Terminals 103A-H may collectively or individually be referred to asterminals 103 orterminal 103, respectively. It is noted thatenterprise system 100 may comprise any number ofmain servers 101 coupled to any number of intermediate servers 102 coupled to any number ofterminals 103. It is further noted that the connections betweenmain server 101 and intermediate servers 102 and the connections between intermediate servers 102 andterminals 103 may be any medium type, e.g., wireless, wired. It is further noted thatenterprise system 100 may comprise a greater or fewer number of hierarchical levels of servers than illustrated and thatFIG. 1 is illustrative. -
FIG. 2 —Hardware Configuration of Terminal -
FIG. 2 illustrates an embodiment of the present invention ofterminal 103.Terminal 103 may comprise aprocessor 201 coupled to various other components by abus 202. Anoperating system 203 may run onprocessor 201 and provide control as well as coordinate the function of the various components ofFIG. 2 .Application 204 may run in conjunction withoperating system 203 which implements the various functions to be performed byapplication 204.Terminal 103 may further comprise a read only memory (ROM) 205, e.g., flash ROM, coupled tobus 202 and may include a boot code image, i.e., binary executable boot code, that controls certain basic functions ofterminal 103 as illustrated inFIG. 3 . - Referring to
FIG. 3 ,FIG. 3 illustrates an embodiment of the present invention ofROM 205, e.g., flash ROM.ROM 205 may storeboot code image 301, i.e., binary executable boot code such as BIOS binary executable code. A portion ofboot code image 301 may be allocated for storingauthentication 302, e.g., password to protect unauthorized users from booting the system, password to protect unauthorized users from accessing setup options, an authentication number to permit installation of software, an authentication to permit operation of software. In one embodiment,authentication 302 may be encrypted.Authentication 302 may be encrypted using various encryption schemes that would be recognized by a person of ordinary skill in the art and that such embodiments employing such schemes would fall within the scope of the present invention. It is noted thatboot cod image 301 may be configured to store more than oneauthentication 302 and thatFIG. 3 is illustrative. - Referring to
FIG. 2 , Random Access Memory (RAM) 206, Input/Output (I/O) adapter 207 andcommunications adapter 208 may also coupled tobus 202. It should be noted that software components includingoperating system 203 andapplication 204 may be loaded intoRAM 206 which may be terminal's 103 main memory. I/O adapter 207 may be an integrated drive electronics (“IDE”) adapter that communicates with astorage medium 209, e.g., disk drive.Communications adapter 208 may interconnectbus 202 with an outside network enabling terminal 103 to communicate withmain server 101, intermediate server 102 via a Local Area Network (LAN), e.g., Ethernet, Token Ring, ARCnet, or a Wide Area Network (WAN), e.g., Internet. -
Terminal 103 may further comprise Input/Output (I/O) devices that may be coupled tobus 202 via a user interface adapter 210 and adisplay adapter 211.Keyboard 212 andbiometric device 214, e.g., fingerprint reader, retinal scanner, may be interconnected tobus 202 through user interface adapter 210. Adisplay device 213 may be coupled tobus 202 throughdisplay adapter 211. In this manner, a user may be capable of inputting toterminal 103 throughkeyboard 212 and receiving output fromterminal 103 viadisplay device 213.Biometric device 214 may be used to authenticate the user atterminal 103 thereby establishing that the user is authorized to access thatparticular terminal 103. It is noted that there are numerous types of input devices and display devices known to those skilled in the art and thus need not be described in detail herein. - Implementations of the invention include implementations as a terminal programmed to execute the method or methods described herein, and as a computer program product. According to the terminal implementation, sets of instructions for executing the method or methods may be resident in the
random access memory 206 of one or more terminal systems configured generally as described above. Until required by the terminal, the set of instructions may be stored as a computer program product in another memory, for example, in storage medium 209 (which may include a removable memory such as an optical disk or floppy disk for eventual use in the storage medium 209). Further, the computer program product may also be stored at another computer such as another terminal 103 or intermediate server 102 ormain server 101 and transmitted when desired to the user's terminal 103 by a network or by an external network such as the Internet. One skilled in the art would appreciate that the physical storage of the sets of instructions physically changes the medium upon which it is stored so that the medium carries computer readable information. The change may be electrical, magnetic, chemical, biological or some other physical change. -
FIG. 4 —Hardware Configuration of Servers -
FIG. 4 illustrates an embodiment of the present invention ofmain server 101, intermediate server 102. Referring toFIG. 4 ,main server 101, intermediate server 102 may comprise a central processing unit (CPU) 410 coupled to various other components bysystem bus 412. Anoperating system 430 runs onCPU 410 and provides control and coordinates the function of the various components ofFIG. 4 . An application 440 in accordance with the principles of the present invention may run in conjunction withoperating system 430 and provide calls tooperating system 430 where the calls implement the various functions or services to be performed by application 440. An application 440 ofmain server 101 may include, for example, a program for updatingauthentications 302, e.g., passwords, authentication numbers, withinboot code image 301, i.e., binary executable boot code, stored inROM 205 at terminal 103 from a remote central site as described in the description ofFIG. 5 , a program for storingauthentications 302, e.g., passwords, authentication numbers, withinboot code image 301 stored inROM 205 at terminal 103 from a remote central site as described inFIG. 6 . Read only memory (ROM) 416 may be coupled tosystem bus 412 and include a basic input/output system (“BIOS”) that controls certain basic functions ofmain server 101, intermediate server 102. Random access memory (RAM) 414,disk adapter 418 and communications adapter 434 may also be coupled tosystem bus 412. It should be noted that software components includingoperating system 430 and application 440 may be loaded intoRAM 414 which is the computer system's main memory.Disk adapter 418 may be a small computer system interface (“SCSI”) adapter that communicates withdisk units 420, e.g., disk drive. It is noted that the program of the present invention that updatesauthentications 302, e.g., passwords, authentication numbers, withinboot code image 301, i.e., binary executable boot code, stored inROM 205 at terminal 103 from a remote central site as described in the description ofFIG. 5 , may reside indisk unit 420 or application 440. It is further noted that the program of the present invention that storesauthentications 302, e.g., passwords, authentication numbers, withinboot code image 301, i.e., binary executable boot code, stored inROM 205 at terminal 103 from a remote central site as described in the description ofFIG. 6 , may reside indisk unit 420 or application 440. Communications adapter 434interconnects bus 412 with an outside network enablingmain server 101, intermediate server 102 to communicate withterminal 103 via a Local Area Network (LAN), e.g., Ethernet, Token Ring, ARCnet, or a Wide Area Network (WAN), e.g., Internet. - Implementations of the invention include implementations as a computer system programmed to execute the method or methods described herein, and as a computer program product. According to the computer system implementations, sets of instructions for executing the method or methods are resident in the
random access memory 414 of one or more computer systems configured generally as described above. Until required bymain server 101, intermediate server 102, the set of instructions may be stored as a computer program product in another computer memory, for example, in disk drive 420 (which may include a removable memory such as an optical disk or floppy disk for eventual use in disk drive 420). Furthermore, the computer program product can also be stored at another computer and transmitted when desired to the user's workstation by a network or by an external network such as the Internet. One skilled in the art would appreciate that the physical storage of the sets of instructions physically changes the medium upon which it is stored so that the medium carries computer readable information. The change may be electrical, magnetic, chemical or some other physical change. -
FIG. 5 —Method for Updating Authentications within a Boot Code Image Stored in ROM in a Terminal from a Remote Central Site -
FIG. 5 is a flowchart of one embodiment of the present invention of amethod 500 for updatingauthentications 302, e.g., passwords, authentication numbers, withinboot code image 301, i.e., binary executable boot code such as BIOS binary executable code, stored in ROM, e.g., flash ROM, at terminal 103 from a remote central site. As stated in the Background Information section, passwords such as passwords to protect unauthorized users from booting the system and accessing setup options are typically stored in non-volatile Random Access Memory (RAM) in the terminal. By storing passwords in non-volatile RAM, a user at a terminal may be able to change or modify the password which may not be desirable. Users may accidentally or maliciously change the password which may result in disastrous consequences such as not being able to boot up the terminal if the user cannot remember the new password. Furthermore, if the user at the terminal forgets the new password, the system administrative staff at the central site, e.g., headquarters, may have difficulty assisting the user as they may not know the new password since the user and not the system administrators at the central site changed the password. Furthermore, in an enterprise network environment, it may be difficult, cumbersome and time consuming to update passwords stored in terminals as each terminal may have different passwords from which to update which may not be known by the system administrators. It would therefore be desirable to store authentications, e.g., password to protect unauthorized users from booting the system, password to protect unauthorized users from accessing setup options, an authentication number to permit installation of software, an authentication to permit operation of software, within a boot code image, i.e., binary executable boot code, stored in ROM, e.g., flash ROM, at a terminal, e.g., cash register, personal computer, thereby preventing the user at the terminal from tampering authentications. It would further be desirable to update the authentications stored in the boot code image in each terminal from a central site, e.g., headquarters, thereby allowing system administrators the ability to know the current authentication installed at the terminal.Method 500 is a method for addressing the above concerns. - In
step 501, a file associated with boot code image 301 (FIG. 3 ), i.e., binary executable boot code such as BIOS binary executable code, to be updated in one or more terminals 103 (FIG. 2 ) may be identified at a central site geographically separate from the location of the one ormore terminals 103 to be updated as described below. As stated above, each terminal 103 coupled tomain server 101 may comprise aboot code image 301. A portion ofboot code image 301 may be allocated for storingauthentication 302, e.g., password to protect unauthorized users from booting the system, password to protect unauthorized users from accessing setup options, an authentication number to permit installation of software, an authentication to permit operation of software. In order to updateauthentication 302 in one ormore terminals 103 coupled tomain server 101, a file associated withboot code image 301 to be updated in the one ormore terminals 103 may be identified at a central site instep 501. - In
step 502,authentication 302, e.g., password to protect unauthorized users from booting the system, password to protect unauthorized users from accessing setup options, authentication number to permit installation of software, an authentication to permit operation of software, inboot code image 301 in the file identified instep 501 may be updated. In one embodiment,authentication 302 in the file associated withboot code image 103 identified instep 501 may be updated without recompiling the entire file associated withboot code image 103. That is, the bytes in the file associatedboot code image 103storing authentication 302 may be modified without modifying any other bytes of the file. - In
step 503, one ormore terminals 103 coupled tomain server 101 may be identified as storing anauthentication 302 in theirboot code image 301 that needs to be updated. - In
step 504,authentication 302 inboot code image 301 in each of the one ormore terminals 103 identified instep 503 may be updated withauthentication 302 updated instep 502. In one embodiment, the updated file may be downloaded frommain server 101 to each of the one ormore terminals 103 identified instep 503 via a network, e.g., LAN, WAN. In one embodiment, the entireboot code image 301 stored in ROM 205 (FIG. 2 ), e.g., flash ROM, in each of the one ormore terminals 103 identified instep 503 may be updated. In another embodiment, a utility program may be attached to the updated file that erases and writes to selected portions ofboot code image 301 stored inROM 205, e.g., flash ROM, such as theportion storing authentication 302. Subsequently, theportion storing authentication 302 inboot code image 301 stored inROM 205 in each of the one ormore terminals 103 identified instep 503 may be erased and written with the updatedauthentication 302. In another embodiment, the updated file may be stored on a storage medium, e.g., magnetic disk, compact disc, which may then be loaded onto the one ormore terminals 103 identified instep 503. In one embodiment, the entireboot code image 301 stored in ROM 205 (FIG. 2 ), e.g., flash ROM, in each of the one ormore terminals 103 identified instep 503 may be updated. In another embodiment, a utility program may be attached to the updated file that erases and writes to selected portions ofboot code image 301 stored inROM 205 such as theportion storing authentication 302 thereby installing the updatedauthentication 302. - In
step 505, a prompt may be displayed to each user of the one ormore terminals 103 identified instep 503 indicating thatauthentication 302 has been updated. In one embodiment,boot code image 301 may comprise code to indicate to the user ofterminal 103 thatauthentication 302 has been updated upon updatingauthentication 302. For example,authentication 302 inboot code image 301 may be updated during the evening when terminal 103 is deactivated. When the user ofterminal 103 activates terminal 103, the user may receive a prompt indicating thatauthentication 302, e.g., password, has been updated and to enter thenew authentication 302, e.g., password. Upon the user receiving thenew authentication 302 from a person in authority, the user may enter thenew authentication 302 thereby allowing the user to boot the system or to access setup options or to install software, etc. - By storing
authentication 302 inboot code image 301 inROM 205, e.g., flash ROM, in each terminal 103, e.g., cash register, personal computer, in an enterprise network environment, a user atterminal 103 may be prevented from tamperingauthentication 302. Furthermore, by updatingauthentication 302 stored inboot code image 301 from a remote central site, e.g., headquarters, system administrators at the central site may have knowledge of the current authentication installed atterminal 103. - It is noted that
method 500 may be executed in a different order presented and that the order presented in the discussion ofFIG. 5 is illustrative. It is further noted that certain steps may be executed almost concurrently. It is further noted that steps 501-504 may be implemented by a program inmain server 101 residing in application 440 (FIG. 4 ) or disk unit 420 (FIG. 4 ). -
FIG. 6 —Method for Storing Authentications within a Boot Code Image Stored in ROM in a Terminal from a Remote Central Site -
FIG. 6 is a flowchart of one embodiment of the present invention of amethod 600 for storingauthentications 302, e.g., authentication number to install software, withinboot code image 301, i.e., binary executable boot code such as BIOS binary executable code, stored inROM 205 at terminal 103 from a remote central site. - In
step 601, a file may be created comprising a boot code image 301 (FIG. 3 ), i.e., binary executable boot code, whereboot code image 301 may comprise anauthentication 302, e.g., authentication number to install software. The file may be created at a central site geographically separate from the location of one ormore terminals 103 to receive the file as described below. - In
step 602, one ormore terminals 103 coupled tomain server 101 may be identified to store the file created instep 601. - In
step 603, the file may be saved in ROM 205 (FIG. 2 ), e.g., flash ROM, in the one ormore terminals 103 identified instep 602. In one embodiment, the file may be downloaded frommain server 101 to each of the one ormore terminals 103 identified instep 602 via a network, e.g., LAN, WAN. In another embodiment, the file may be stored on a storage medium, e.g., magnetic disk, compact disc, which may then be loaded onto the one ormore terminals 103 identified instep 602. - It is noted that
method 600 may be executed in a different order presented and that the order presented in the discussion ofFIG. 6 is illustrative. It is further noted that certain steps may be executed almost concurrently. - Although the system, method and computer program product are described in connection with several embodiments, it is not intended to be limited to the specific forms set forth herein, but on the contrary, it is intended to cover such alternatives, modifications and equivalents, as can be reasonably included within the spirit and scope of the invention as defined by the appended claims. It is noted that the headings are used only for organizational purposes and not meant to limit the scope of the description or claims.
Claims (21)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/200,468 US9117082B2 (en) | 2001-10-31 | 2005-08-09 | Authentications integrated into a boot code image |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/001,697 US6993650B2 (en) | 2001-10-31 | 2001-10-31 | Authentications integrated into a boot code image |
US11/200,468 US9117082B2 (en) | 2001-10-31 | 2005-08-09 | Authentications integrated into a boot code image |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/001,697 Continuation US6993650B2 (en) | 2001-10-31 | 2001-10-31 | Authentications integrated into a boot code image |
Publications (2)
Publication Number | Publication Date |
---|---|
US20060031665A1 true US20060031665A1 (en) | 2006-02-09 |
US9117082B2 US9117082B2 (en) | 2015-08-25 |
Family
ID=21697362
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/001,697 Expired - Lifetime US6993650B2 (en) | 2001-10-31 | 2001-10-31 | Authentications integrated into a boot code image |
US11/200,468 Expired - Fee Related US9117082B2 (en) | 2001-10-31 | 2005-08-09 | Authentications integrated into a boot code image |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/001,697 Expired - Lifetime US6993650B2 (en) | 2001-10-31 | 2001-10-31 | Authentications integrated into a boot code image |
Country Status (1)
Country | Link |
---|---|
US (2) | US6993650B2 (en) |
Families Citing this family (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7237122B2 (en) * | 2001-10-19 | 2007-06-26 | Mcafee, Inc. | Method and apparatus to facilitate software installation using embedded user credentials |
US6993650B2 (en) * | 2001-10-31 | 2006-01-31 | International Business Machines Corporation | Authentications integrated into a boot code image |
US20040025033A1 (en) * | 2002-08-02 | 2004-02-05 | Todd Luke B. | System and method for preventing unauthorized installation, use and reproduction of software |
US7644288B2 (en) * | 2003-03-19 | 2010-01-05 | Ricoh Company, Ltd. | Image forming apparauts that checks authenticity of an update program |
US7142891B2 (en) * | 2003-10-10 | 2006-11-28 | Texas Instruments Incorporated | Device bound flashing/booting for cloning prevention |
US9589117B2 (en) | 2004-02-17 | 2017-03-07 | Hewlett-Packard Development Company, L.P. | Computer security system and method |
US20050262337A1 (en) * | 2004-05-24 | 2005-11-24 | Siemens Vdo Automotive Corporation | Method and device for determining flash software compatibility with hardware |
US7610477B2 (en) * | 2004-09-15 | 2009-10-27 | Microsoft Corporation | Deploying and receiving software over a network susceptible to malicious communication |
JP4764056B2 (en) * | 2005-04-14 | 2011-08-31 | キヤノン株式会社 | Image processing apparatus, control program update method, and program |
US7818580B2 (en) | 2005-08-09 | 2010-10-19 | International Business Machines Corporation | Control of port based authentication protocols and process to support transfer of connection information |
EP2020114A4 (en) | 2006-05-24 | 2014-01-22 | Vidoop L L C | Graphical image authentication and security system |
US8117458B2 (en) * | 2006-05-24 | 2012-02-14 | Vidoop Llc | Methods and systems for graphical image authentication |
US9189603B2 (en) | 2006-05-24 | 2015-11-17 | Confident Technologies, Inc. | Kill switch security method and system |
US20070277224A1 (en) | 2006-05-24 | 2007-11-29 | Osborn Steven L | Methods and Systems for Graphical Image Authentication |
JP4952101B2 (en) * | 2006-07-12 | 2012-06-13 | 富士通株式会社 | Personal authentication device and personal authentication method |
US8707297B2 (en) * | 2006-07-26 | 2014-04-22 | Dell Products L.P. | Apparatus and methods for updating firmware |
KR100832269B1 (en) | 2006-09-08 | 2008-05-26 | 삼성전자주식회사 | Program update method and system for wireless communication terminal |
US8615665B2 (en) * | 2007-01-26 | 2013-12-24 | Harris Corporation | Method for providing high assurance integrity of installed software images in a software defined radio |
AU2008213849A1 (en) * | 2007-02-05 | 2008-08-14 | Vidoop Llc | Methods and systems for delivering sponsored out-of-band passwords |
WO2008098029A1 (en) * | 2007-02-06 | 2008-08-14 | Vidoop, Llc. | System and method for authenticating a user to a computer system |
US20100250937A1 (en) * | 2007-03-05 | 2010-09-30 | Vidoop, Llc | Method And System For Securely Caching Authentication Elements |
US20110202982A1 (en) * | 2007-09-17 | 2011-08-18 | Vidoop, Llc | Methods And Systems For Management Of Image-Based Password Accounts |
US8413130B2 (en) * | 2007-10-03 | 2013-04-02 | International Business Machines Corporation | System and method for self policing of authorized configuration by end points |
US8788637B2 (en) * | 2007-11-05 | 2014-07-22 | Hewlett-Packard Development Company, L.P. | Systems and methods for downloading boot code associated with base stations |
US7979739B2 (en) * | 2007-11-13 | 2011-07-12 | Hewlett-Packard Development Company, L.P. | Systems and methods for managing a redundant management module |
US20090240578A1 (en) * | 2008-03-18 | 2009-09-24 | Christopher James Lee | Methods and systems for graphical security authentication and advertising |
US8621578B1 (en) | 2008-12-10 | 2013-12-31 | Confident Technologies, Inc. | Methods and systems for protecting website forms from automated access |
US8429640B2 (en) * | 2009-06-05 | 2013-04-23 | Dell Products L.P. | System and method for modifying firmware |
US10277616B2 (en) | 2014-09-25 | 2019-04-30 | Vigilant Ip Holdings Llc | Secure digital traffic analysis |
CN105550586A (en) * | 2014-10-30 | 2016-05-04 | 北京京航计算通讯研究所 | Trusted boot design method applicable to DSP environment |
US9767318B1 (en) * | 2015-08-28 | 2017-09-19 | Frank Dropps | Secure controller systems and associated methods thereof |
KR102567097B1 (en) | 2018-12-05 | 2023-08-14 | 삼성전자주식회사 | Method for updating Boot ROM of Embedded system and booting of thereof |
Citations (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6009524A (en) * | 1997-08-29 | 1999-12-28 | Compact Computer Corp | Method for the secure remote flashing of a BIOS memory |
US6167532A (en) * | 1998-02-05 | 2000-12-26 | Compaq Computer Corporation | Automatic system recovery |
US6272628B1 (en) * | 1998-12-14 | 2001-08-07 | International Business Machines Corporation | Boot code verification and recovery |
US6289449B1 (en) * | 1998-12-14 | 2001-09-11 | International Business Machines Corporation | Creating boot code image on a storage medium |
US20020174351A1 (en) * | 2001-05-18 | 2002-11-21 | Aralion Inc | High security host adapter |
US20030033515A1 (en) * | 2001-08-10 | 2003-02-13 | Autry Mark A. | Upgrading a bios |
US6535976B1 (en) * | 1997-03-27 | 2003-03-18 | International Business Machines Corporation | Initial program load in data processing network |
US20030084342A1 (en) * | 2001-10-30 | 2003-05-01 | Girard Luke E. | Mechanism to improve authentication for remote management of a computer system |
US20030120913A1 (en) * | 2001-12-21 | 2003-06-26 | Dell Products, L.P. | System and method for updating BIOS for a multiple-node computer system |
US6647498B1 (en) * | 1998-07-15 | 2003-11-11 | Samsung Electronics Co., Ltd. | Method and apparatus for preventing personal computer from being illegally used |
US6694360B1 (en) * | 2000-06-09 | 2004-02-17 | 3Com Corporation | Multi-mode network interface having loadable software images |
US6993650B2 (en) * | 2001-10-31 | 2006-01-31 | International Business Machines Corporation | Authentications integrated into a boot code image |
US20060136708A1 (en) * | 2004-12-20 | 2006-06-22 | Hassan Hajji | Information processing system, program product, and information processing method |
Family Cites Families (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3461432A (en) * | 1966-12-14 | 1969-08-12 | Burroughs Corp | Bi-directional code converter |
DE4232024C2 (en) | 1991-10-11 | 1997-03-27 | Toshiba Kawasaki Kk | Computer with password processing function and method for password processing on a computer |
JPH08147062A (en) | 1994-11-22 | 1996-06-07 | Oki Electric Ind Co Ltd | Password collating method of computer |
EP0770997A3 (en) | 1995-10-27 | 1998-01-07 | Ncr International Inc. | Password protection for removable hard drive |
GB2311390B (en) | 1996-03-18 | 2000-03-22 | Ibm | Initial program load in data processing network |
US6199163B1 (en) | 1996-03-26 | 2001-03-06 | Nec Corporation | Hard disk password lock |
US5892906A (en) | 1996-07-19 | 1999-04-06 | Chou; Wayne W. | Apparatus and method for preventing theft of computer devices |
KR100223484B1 (en) | 1996-11-25 | 1999-10-15 | 윤종용 | A computer system having password recovery function and a recovery method of that |
US6061794A (en) | 1997-09-30 | 2000-05-09 | Compaq Computer Corp. | System and method for performing secure device communications in a peer-to-peer bus architecture |
US6243809B1 (en) | 1998-04-30 | 2001-06-05 | Compaq Computer Corporation | Method of flash programming or reading a ROM of a computer system independently of its operating system |
US6463474B1 (en) * | 1999-07-02 | 2002-10-08 | Cisco Technology, Inc. | Local authentication of a client at a network device |
US6757825B1 (en) * | 1999-07-13 | 2004-06-29 | Lucent Technologies Inc. | Secure mutual network authentication protocol |
US6725205B1 (en) * | 1999-12-02 | 2004-04-20 | Ulysses Esd, Inc. | System and method for secure software installation |
US6732267B1 (en) * | 2000-09-11 | 2004-05-04 | Dell Products L.P. | System and method for performing remote BIOS updates |
-
2001
- 2001-10-31 US US10/001,697 patent/US6993650B2/en not_active Expired - Lifetime
-
2005
- 2005-08-09 US US11/200,468 patent/US9117082B2/en not_active Expired - Fee Related
Patent Citations (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6535976B1 (en) * | 1997-03-27 | 2003-03-18 | International Business Machines Corporation | Initial program load in data processing network |
US6009524A (en) * | 1997-08-29 | 1999-12-28 | Compact Computer Corp | Method for the secure remote flashing of a BIOS memory |
US6167532A (en) * | 1998-02-05 | 2000-12-26 | Compaq Computer Corporation | Automatic system recovery |
US6647498B1 (en) * | 1998-07-15 | 2003-11-11 | Samsung Electronics Co., Ltd. | Method and apparatus for preventing personal computer from being illegally used |
US6289449B1 (en) * | 1998-12-14 | 2001-09-11 | International Business Machines Corporation | Creating boot code image on a storage medium |
US6272628B1 (en) * | 1998-12-14 | 2001-08-07 | International Business Machines Corporation | Boot code verification and recovery |
US6694360B1 (en) * | 2000-06-09 | 2004-02-17 | 3Com Corporation | Multi-mode network interface having loadable software images |
US20020174351A1 (en) * | 2001-05-18 | 2002-11-21 | Aralion Inc | High security host adapter |
US20030033515A1 (en) * | 2001-08-10 | 2003-02-13 | Autry Mark A. | Upgrading a bios |
US20030084342A1 (en) * | 2001-10-30 | 2003-05-01 | Girard Luke E. | Mechanism to improve authentication for remote management of a computer system |
US6993650B2 (en) * | 2001-10-31 | 2006-01-31 | International Business Machines Corporation | Authentications integrated into a boot code image |
US20030120913A1 (en) * | 2001-12-21 | 2003-06-26 | Dell Products, L.P. | System and method for updating BIOS for a multiple-node computer system |
US20060136708A1 (en) * | 2004-12-20 | 2006-06-22 | Hassan Hajji | Information processing system, program product, and information processing method |
Also Published As
Publication number | Publication date |
---|---|
US20030084275A1 (en) | 2003-05-01 |
US6993650B2 (en) | 2006-01-31 |
US9117082B2 (en) | 2015-08-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9117082B2 (en) | Authentications integrated into a boot code image | |
US8275994B2 (en) | Information storage apparatus and password collation method | |
US7958553B2 (en) | Information storage device, security system, access permission method, network access method and security process execution permission method | |
US9832230B2 (en) | IC chip, information processing apparatus, system, method, and program | |
US20040230843A1 (en) | System and method for authenticating users using image selection | |
CN107169344B (en) | Method for blocking unauthorized application and apparatus using the same | |
JPH03237551A (en) | Transaction system security method and device | |
US20060041944A1 (en) | Information processing device, information processing system, and program | |
WO2001027722A1 (en) | Operation of trusted state in computing platform | |
US9438585B2 (en) | Trusted vendor access | |
CN101901311A (en) | Management of hardware passwords | |
US8544083B2 (en) | Identification security elevation | |
CN103793661B (en) | Mobile terminal device, signal processing method, document storage server and document file management system | |
US6983364B2 (en) | System and method for restoring a secured terminal to default status | |
JP2001202484A (en) | Security management system and its program storage medium | |
JPH05274269A (en) | Method and system for verifying validity of access in computer system | |
CN111709054B (en) | Privacy space information access control method and device and computer equipment | |
JP2001117661A (en) | Portable information terminal equipment and program recording medium for the same | |
CN104346165A (en) | Information processing apparatus, information processing method, program, storage medium, and information processing system | |
JP4486199B2 (en) | Portable terminal device, server device, and recording medium | |
JP2008176506A (en) | Information processing apparatus, information processing method and management server | |
JP4768897B2 (en) | Authentication data storage device and authentication system | |
US20220121748A1 (en) | Modifications to firmware functionality | |
JP4213440B2 (en) | Password management program | |
JP3978964B2 (en) | Security management system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: TOSHIBA GLOBAL COMMERCE SOLUTIONS HOLDINGS CORPORA Free format text: PATENT ASSIGNMENT AND RESERVATION;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:028895/0935 Effective date: 20120731 |
|
ZAAA | Notice of allowance and fees due |
Free format text: ORIGINAL CODE: NOA |
|
ZAAB | Notice of allowance mailed |
Free format text: ORIGINAL CODE: MN/=. |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20230825 |