Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS20020108045 A1
Publication typeApplication
Application numberUS 10/113,506
Publication dateAug 8, 2002
Filing dateMar 29, 2002
Priority dateJan 22, 1999
Also published asUS6408387
Publication number10113506, 113506, US 2002/0108045 A1, US 2002/108045 A1, US 20020108045 A1, US 20020108045A1, US 2002108045 A1, US 2002108045A1, US-A1-20020108045, US-A1-2002108045, US2002/0108045A1, US2002/108045A1, US20020108045 A1, US20020108045A1, US2002108045 A1, US2002108045A1
InventorsSteve Wells
Original AssigneeSteve Wells
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
Preventing unauthorized updates to a non-volatile memory
US 20020108045 A1
Abstract
An apparatus and method for preventing unauthorized updates to a non-volatile memory. A sequence of encoded values is received in a non-volatile memory device and decoded by a decoding circuit in the non-volatile memory device to generate a sequence of decoded values. The sequence of decoded values is stored in the non-volatile memory device.
Images(7)
Previous page
Next page
Claims(53)
What is claimed is:
1. A method comprising the steps of:
receiving a sequence of encoded values in a non-volatile memory device;
decoding the sequence of encoded values in a decoding circuit within the non-volatile memory device to generate a sequence of decoded values; and
storing the sequence of decoded values in the non-volatile memory device.
2. The method of claim 1 further comprising the step of encoding a sequence of processor instructions to generate the sequence of encoded values.
3. The method of claim 2 wherein the step of encoding a sequence of processor instructions includes the step of encoding Basic Input/Output Services (BIOS) program code, the BIOS program code including program code for booting a computer system.
4. The method of claim 2 wherein the step of encoding a sequence of processor instructions includes the step of logically combining the sequence of processor instructions with a sequence of values generated by a first sequence generator.
5. The method of claim 4 wherein the step of logically combining includes the step of combining the sequence of processor instructions with the sequence of values generated by the sequence generator in one or more exclusive OR operations.
6. The method of claim 4 wherein the step of decoding the sequence of encoded values includes the step of logically combining the sequence of encoded values with a sequence of values generated by a second sequence generator.
7. The method of claim 6 wherein the sequence of values generated by the second sequence generator is the same as the sequence of values generated by the first sequence generator.
8. The method of claim 1 wherein the non-volatile memory device is an electrically erasable, programmable read-only memory (EEPROM).
9. The method of claim 8 wherein the EEPROM is a flash EEPROM.
10. A non-volatile memory device comprising:
storage elements;
writing circuitry to receive encoded data from a data path and to store the data in the storage elements; and
decoding circuitry coupled to the writing circuitry to decode the encoded data received from the data path before the writing circuitry stores the data in the storage elements.
11. The non-volatile memory device of claim 10 wherein the decoding circuitry includes:
a sequence generator to generate a sequence of values; and
logic to combine the sequence of values with the encoded data to decode the encoded data.
12. The non-volatile memory device of claim 11 wherein the sequence generator is a pseudo-random sequence generator.
13. The non-volatile memory device of claim 11 wherein the logic to combine the sequence of values includes logic to combine the sequence of values with the encoded data received from the data path in one or more exclusive OR operations.
14. The non-volatile memory device of claim 10 wherein the encoded data is encoded program code.
15. The non-volatile memory device of claim 10 wherein the non-volatile memory device is a flash electrically erasable, programmable read-only memory (flash EPROM).
16. An apparatus comprising:
storage means for storing data;
writing means for receiving encoded data from a data path and storing the data in the storage means; and
decoding means coupled to the writing means for decoding the data received from the data path before the writing means stores the data in the storage means.
17. The apparatus of claim 16 wherein the decoding means includes:
means for generating a sequence of values; and
means for combining the sequence of values with the encoded data to decode the encoded data.
18. A computer system comprising:
a processor;
a datapath coupled to the processor and
a flash electrically erasable, programmable read-only memory (flash EPROM) coupled to the datapath, the flash EPROM including
storage elements,
writing circuitry to receive encoded data from the processor via the data path and to store the data in the storage elements, and
decoding circuitry coupled to the writing circuitry to decode the encoded data received from the processor before the writing circuitry stores the data in the storage elements.
19. The computer system of claim 18 wherein the decoding circuitry includes:
a sequence generator to generate a sequence of values; and
logic to combine the sequence of values with the encoded data to decode the encoded data.
20. A method comprising the steps of:
storing a sequence of encoded values in storage elements of a non-volatile memory device;
retrieving the encoded sequence of values from the storage elements in response to a read request;
decoding the encoded sequence of values in a decoding circuit within the non-volatile memory device to generate a sequence of decoded values; and
outputting the sequence of decoded values.
21. A non-volatile memory device comprising: storage elements;
reading circuitry to retrieve encoded data from the storage elements and to output the data on a data path; and
decoding circuitry coupled to the reading circuitry to decode the encoded data retrieved from the storage elements before the reading circuitry outputs the data on the data path.
22. A method comprising:
receiving an encoded sequence of values by a non-volatile memory device;
storing the encoded sequence of values in the non-volatile memory device; and
decoding the stored encoded sequence of values by the non-volatile memory device.
23. The method of claim 22, wherein the receiving comprises receiving encoded program code.
24. The method of claim 22, wherein the receiving comprises receiving encoded basic input/output system (BIOS) program code.
25. The method of claim 22, comprising encoding a sequence of values to generate the encoded sequence of values.
26. The method of claim 25, wherein the encoding comprises combining the sequence of values and another sequence of values.
27. The method of claim 26, wherein the combining comprises performing an exclusive-OR operation.
28. The method of claim 22, wherein the decoding comprises combining values of the stored encoded sequence of values and another sequence of values.
29. The method of claim 28, wherein the combining comprises performing an exclusive-OR operation.
30. The method of claim 22, wherein the decoding comprises combining values of the stored encoded sequence of values and another sequence of values used to generate the stored encoded sequence of values.
31. The method of claim 22, wherein the decoding comprises retrieving the stored encoded sequence of values in response to a read request and decoding the retrieved encoded sequence of values.
32. The method of claim 22, wherein the non-volatile memory device comprises an electrically erasable, programmable read-only memory (EEPROM) device.
33. The method of claim 22, wherein the non-volatile memory device comprises a flash electrically erasable, programmable read-only memory (EEPROM) device.
34. An apparatus comprising:
non-volatile storage elements;
circuitry to store an encoded sequence of values in the non-volatile storage elements; and
circuitry to decode the stored encoded sequence of values.
35. The apparatus of claim 34, wherein the encoded sequence of values comprises encoded program code.
36. The apparatus of claim 34, wherein the encoded sequence of values comprises encoded basic input/output system (BIOS) program code.
37. The apparatus of claim 34, wherein the circuitry to decode comprises a sequence generator to generate another sequence of values and circuitry to combine the generated sequence of values and values of the stored encoded sequence of values.
38. The apparatus of claim 37, wherein the sequence generator comprises a pseudo-random sequence generator.
39. The apparatus of claim 37, wherein the circuitry to combine comprises an exclusive-OR gate.
40. The apparatus of claim 37, the sequence generator to generate another sequence of values used to generate the encoded sequence of values.
41. The apparatus of claim 34, comprising circuitry to retrieve the stored encoded sequence of values from the non-volatile storage elements in response to a read request.
42. The apparatus of claim 34, wherein the non-volatile storage elements comprise electrically erasable, programmable read-only memory (EEPROM) storage elements.
43. The apparatus of claim 34, wherein the non-volatile storage elements comprise flash electrically erasable, programmable read-only memory (EEPROM) storage elements.
44. A system comprising:
a processor;
a datapath coupled to the processor; and
a non-volatile memory device coupled to the datapath, the non-volatile memory device comprising non-volatile storage elements, circuitry to store in the non-volatile storage elements an encoded sequence of values received from the processor, and circuitry to decode the stored encoded sequence of values.
45. The system of claim 44, wherein the encoded sequence of values comprises encoded program code.
46. The system of claim 44, wherein the encoded sequence of values comprises encoded basic input/output system (BIOS) program code.
47. The system of claim 44, wherein the circuitry to decode comprises a sequence generator to generate another sequence of values and circuitry to combine the generated sequence of values and values of the stored encoded sequence of values.
48. The system of claim 47, wherein the sequence generator comprises a pseudo-random sequence generator.
49. The system of claim 47, wherein the circuitry to combine comprises an exclusive-OR gate.
50. The system of claim 47, the sequence generator to generate another sequence of values used to generate the encoded sequence of values.
51. The system of claim 44, comprising circuitry to retrieve the stored encoded sequence of values from the non-volatile storage elements in response to a read request.
52. The system of claim 44, wherein the non-volatile storage elements comprise electrically erasable, programmable read-only memory (EEPROM) storage elements.
53. The system of claim 44, wherein the non-volatile storage elements comprise flash electrically erasable, programmable read-only memory (EEPROM) storage elements.
Description
    FIELD OF THE INVENTION
  • [0001]
    The present invention relates to the field of memory management, and more particularly to securing updates to a non-volatile memory used to store program code.
  • BACKGROUND OF THE INVENTION
  • [0002]
    Many computer systems include a non-volatile memory to store basic input/output system (BIOS) program code. The BIOS code is usually the lowest layer of software in a computer system and acts as an interface between system hardware and higher-layer software. For example, the BIOS typically includes routines for managing system startup and for controlling various hardware components such as a wait-state generator, hardware timers, interrupt controllers and so forth.
  • [0003]
    Because BIOS routines interact extensively with system hardware, they are often invoked at a privilege level that allows unrestricted memory and I/O access. This makes the BIOS space (i.e., the memory space allocated to the BIOS) a particularly likely candidate for malicious attack. If unauthorized code (e.g., a computer virus) is substituted for BIOS code, the unauthorized code will likely be able to access a broad range of system devices that privilege-level protections would otherwise prevent. As a result, a successful attack on the BIOS space can result in considerable damage to a computer system, including the loss of sensitive information.
  • [0004]
    In modern computer systems, flash memory devices (e.g., flash electrically-erasable, programmable read-only memory (flash EEPROM)) are often used to store BIOS code. By sending the appropriate commands, flash devices can be erased and reprogrammed. While this makes it easier to install updated BIOS software, it also opens the door to malicious attack on the BIOS space. For example, some BIOS developers post updated BIOS code on sites of the World Wide Web (“the web”) from which they can be downloaded and installed. One seeking to introduce unauthorized code into the BIOS space (i.e., an “attacker”) could modify the posted BIOS code or even intercept and modify the code during download. Alternatively an attacker might masquerade as a legitimate BIOS developer to induce a computer user to download and install unauthenticated code. For example, the attacker could post unauthenticated code on a website and represent the code as being provided by a legitimate developer.
  • [0005]
    [0005]FIG. 1 is a data flow diagram that illustrates one prior-art technique for preventing unauthorized access to the BIOS space. Initially, program code 10 is obtained in a computer system that includes a processor 22, a system memory 11, an updatable, non-volatile memory device 12, a bus 20 and an interrupt generator 28. When a data transfer program 19 is executed, write circuitry 26 within the processor 22 transfers the program code 10 across bus 20 along with commands to the flash device 12 to write the program code into a predetermined space within storage array 18. The interrupt generator 28 snoops the signals transferred across the bus 20 and can therefore detect when a write access to the flash device 12 is being attempted. In response to detecting a write access attempt, the interrupt generator 28 asserts an interrupt 29 to interrupt the processor 22. In response to the interrupt, the processor 22 invokes an interrupt service routine 27 (typically stored in system memory 11) to validate the source of the data write, for example, by determining whether a predetermined value is present in the program code 10 (e.g., header or trailer information).
  • [0006]
    If the interrupt service routine (ISR) 27 determines that the attempted write access to the flash device 12 is valid, the ISR 27 is exited and transfer of the program code 10 is resumed. To prevent repeated interrupt generation after the initial validation operation, the interrupt generator 28 may be disabled until after the transfer is complete.
  • [0007]
    One disadvantage of the above-described technique is that it is relatively easy to circumvent. For example, the vector to the ISR 27 can be changed so that when the interrupt from the interrupt generator 28 is received, a substitute ISR is invoked. This substitute ISR may then disable the interrupt generator without validating the program code 10 that is attempting to write to the flash device 12. Unauthorized program code may then be written to the flash memory device 12. Alternatively, an attacker may access the code of ISR 27 to learn the authenticating value (or set of values) that is expected in the program code 10 and where the authenticating value is stored. The attacker can then store the authenticating value in unauthorized program code so that the ISR 27 erroneously validates the unauthorized program code. Again, the unauthorized program code may be written to the flash memory device 12.
  • SUMMARY OF THE INVENTION
  • [0008]
    An apparatus and method for preventing unauthorized updates to a non-volatile memory are disclosed. A sequence of encoded values is received in a non-volatile memory device. The sequence of encoded values is decoded in a decoding circuit in the non-volatile memory device to generate a sequence of decoded values and the sequence of decoded values is stored in the non-volatile memory device.
  • [0009]
    Other features and advantages of the invention will be apparent from the accompanying drawings and from the detailed description that follows below.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0010]
    The present invention is illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate similar elements and in which:
  • [0011]
    [0011]FIG. 1 is a data flow diagram that illustrates one prior-art technique for preventing unauthorized access to a BIOS space;
  • [0012]
    [0012]FIG. 2 is a data flow diagram that illustrates a method of updating contents of a non-volatile memory device according to one embodiment;
  • [0013]
    [0013]FIG. 3 diagrams one embodiment of a method for generating the encoded program code that restricts access to the encoding technique;
  • [0014]
    [0014]FIG. 4 is a diagram of a flash memory device according to one embodiment;
  • [0015]
    [0015]FIG. 5 is a diagram illustrating the components of a keystream-based encoding/decoding system according to one embodiment; and
  • [0016]
    [0016]FIG. 6 depicts one embodiment of a keystream generator 89 that is used to decode an encoded image.
  • DETAILED DESCRIPTION
  • [0017]
    According to embodiments of the present invention, computer security is increased by writing pre-encoded program code to an enhanced-security, non-volatile memory device. Prior to publishing program code, a software developer encodes the program code using a predetermined encoding technique. When the published, encoded program code is obtained by a consumer and written to the enhanced-security, non-volatile memory device, a decoding circuit within the non-volatile memory device decodes the program code before it is stored in the device's non-volatile storage array. The decoded program code may then be fetched and executed in a conventional manner.
  • [0018]
    If an attacker attempts to transfer unauthorized, unencoded program code to the non-volatile memory device, the decoding circuit will garble the unauthorized code to prevent its execution. While this does not prevent overwriting of contents of the non-volatile memory, it does prevent the storage of program code which, if executed, could result in a loss of valuable or sensitive data. Thus, it is an intended advantage of the present invention to provide enhanced computer security by preventing unauthorized program code from being successfully stored in a non-volatile memory device. Other features and advantages of the present invention will be apparent from the following description and the accompanying drawings.
  • [0019]
    [0019]FIG. 2 is a data flow diagram that illustrates a method of updating contents of a non-volatile memory device according to one embodiment. Program code 10 is encoded according to a predetermined encoding technique and then published for distribution as encoded program code 50. As discussed below, any number of different encoding techniques may be used to generate the encoded program code 50. Also, because an important application of the present invention is to prevent the BIOS space from being written with unauthorized program code, the program code is occasionally referred to as BIOS code in the following description. Application of the present invention is not limited to securing BIOS code, however, and the program code may generally be any program code or data for which enhanced security is desired.
  • [0020]
    After the program code 10 has been encoded, the encoded program code 50 is transferred to a computer system 21 that includes a processor 22, a non-volatile memory device 32 a system memory 11 and a bus 20. The non-volatile memory device 32 is shown in FIG. 2 and described in the following description as a flash memory device, although any non-volatile memory device that can-be erased and reprogrammed in-circuit may be used.
  • [0021]
    After the encoded program code 50 has been received in the computer system 21 (e.g., stored in the system memory 11), writing circuitry 26 in the processor 22 is used to transfer the encoded program code 50 to the flash memory device 32 via the bus 20. The encoded program code is transferred to the flash memory device 32 one word at a time in response to execution of program code 51. The word-size of each word transferred is determined by the width of the data portion of the bus 20 or by the software used to control the transfer 51, or both. In any case, the encoded program code 50 is received by the flash memory device 32 as a stream of data words.
  • [0022]
    In one embodiment, the flash device includes writing circuitry 36, reading circuitry 14, a storage array 18 and decoding logic 38. The writing circuitry 36 within the flash memory device 32 transfers the encoded program code 50 to decoding logic 38. The decoding logic 38 decodes the encoded program code 50 to recover the original program code 10. The decoded program code (i.e., recovered program code 10) is then stored in the storage array 18. Under software control, reading circuitry 24 within the processor 22 may fetch the decoded program code via the reading circuitry 14 in the flash memory device 32. The decoded program code may then be executed by the processor 22 in a conventional manner.
  • [0023]
    According to one embodiment, access to the technique for encoding program code is restricted to authenticated software developers to prevent unauthorized persons from circumventing the security mechanism described above. FIG. 3 diagrams one embodiment of a method for generating the encoded program code (e.g., encoded program code 50 of FIG. 2) that restricts access to the encoding technique to authenticated software developers. At step 41, a software developer 54 presents authentication information to a non-volatile memory component manufacturer 57 in a request to be authenticated as a legitimate software developer. The authentication information may include, but is not limited to, documents affirming the identity of the software developer, information obtained by visiting the software developer's site to assure its legitimacy and security procedures, and so forth. If the software developer 54 is authenticated at step 43, then the memory component manufacturer 57 grants the software developer 54 access to the encoding device or encoding computer program at step 45. According to one embodiment, the memory component manufacturer 57 grants access to the encoding device or program by encoding program code on behalf of the software developer 54. In this way, the memory component manufacturer 57 maintains possession of the encoding device or program, thus enhancing system security. In an alternate embodiment, the memory component manufacturer 57 may release the encoding device or program to the software developer 54 to allow the software developer 54 to perform the encoding operation.
  • [0024]
    At step 47, the program code is encoded into an encoded image (e.g., encoded program code 50 of FIG. 2) by the software developer 54 or by the memory component manufacturer 57 on the software developer's behalf. At step 49, the software developer 54 releases the encoded image for publication. At step 51, a consumer 55 obtains the encoded image of the software developer's program code, for example, by downloading the encoded image from a website or by purchasing a computer-readable medium having the encoded image stored thereon (e.g., CD-ROM or diskette) from a retailer. At step 53, the consumer 55 executes a program (e.g., program code 51 of FIG. 2) to transfer the encoded image to a non-volatile memory device 32 that contains decoding logic 38. The decoding logic 38 restores the encoded program code to its executable form so that the program code may be fetched and executed.
  • [0025]
    [0025]FIG. 4 is a diagram of a flash memory device 32 according to one embodiment. The flash memory device 32 includes input and output buffers 61 and 63, control logic 65, decoding logic 38, an address buffer 67, an address counter 69, block select logic 80, word select logic 82, gating/sensing circuitry 70 and a storage array 18 arranged in blocks 0 to N−1. The flash memory device 32 may include other components that are not shown (e.g., page buffers and page buffer control circuitry). The flash memory device 32 receives and outputs data on an N-bit wide data bus 71, receives addresses on an M-bit wide address bus 73 and receives control signals output enable 74, write enable 75 and chip enable 76 on a control bus 72. In one embodiment, the control bus 72, address bus 73 and data bus 71 are included in the bus 20 shown in FIG. 2.
  • [0026]
    The control logic 65 receives the output enable 74, write enable 75 and chip enable signals 76 and issues control signals to the output buffer 61, input buffer 63 and address buffer 67 in response. For example, when the write enable signal and the chip enable signals are asserted, the control logic 65 issues control signals to enable an input value from the data bus 71 into the input buffer 63 and an address from the address bus 73 into the address buffer 67. The input value is then delivered from the input buffer 63 to either the decoding logic 38 or the control logic 65 based on whether the input value is a command or data. For example, if a data transfer was completed in the preceding transfer cycle, the next input value may be assumed to be a command and is therefore delivered to the control logic 65. Input values that are part of a commanded data transfer are delivered to the decoding logic 38 and then to the gating/sensing circuitry 70. The gating/sensing circuitry 70 programs (writes) each decoded value received from the decoding logic 38 in the storage array 18.
  • [0027]
    Assuming that a command to write a sequence of values (e.g., program code) has been received in the control logic 65, the control logic 65 will cause the address from the address buffer 67 to be stored in the address counter 69 and will then signal the address counter 69 to increment the address as each data value is written to the storage array 18. The block select logic 80 and word select logic 82 receive each incremental address from the address counter 69 and decode the address to select a block within the storage array 18 and a location within the selected block, respectively, at which a decoded data value is stored. The gating/sensing circuitry 70 is used to perform the actual programming (writing) and sensing (reading) operations. When a command is received to read data from the storage array 18, a value is output from the addressed location (as selected by the block select logic 80 and word select logic 82), amplified by the gating/sensing circuitry 70 and driven onto the data bus 71 by the output buffer 61, all under control of the control logic 65.
  • [0028]
    For each unit of program code received from the data bus 71 and buffered in the input buffer 63, the control logic 65 signals the decoding logic 38 to generate a new decoding value that is applied to decode the unit of program code. Each decoded program code value is supplied to the gating/sensing circuitry 70 which programs the decoded program code value into a respective storage location selected by the block select logic 80 and the word select logic 82.
  • [0029]
    The sequence of decoding values generated by the decoding logic 38 and applied to decode an incoming program code sequence is referred to as a keystream. A keystream is generated by a logic element called a keystream generator which may be implemented in software or by a wide variety of circuits.
  • [0030]
    [0030]FIG. 5 is a diagram illustrating the components of a keystream-based encoding/decoding system according to one embodiment. As shown, a program code sequence 10 is exclusive-or'd (e.g., by exclusive-or gate 85) word-by-word with a keystream 84 to produce an encoded image 50. When the encoded image 50 is transferred to a non-volatile memory device that includes decoding logic 38 (e.g., the non-volatile memory device 32 of FIG. 4), a keystream generator 89 within the decoding logic 38 applies the same keystream 84 that was used to produce the encoded image 50 to the recover the original program code sequence 10. The following illustrates the logical equivalence between a code sequence that has been twice exclusively-or'd with the same keystream and the original code sequence:
  • (CODE XOR KEY) XOR KEY=CODE XOR (KEY XOR KEY)=CODE XOR 0=CODE
  • [0031]
    According to one embodiment, the encoded image 50 is produced by executing a computer program to generate the keystream 84 and to XOR the individual keystream values with respective words of the program code sequence. Because the decoding logic is implemented in hardware, a circuit-based keystream generator 89 is used in one embodiment to generate the keystream 84 applied to decode the encoded image 50.
  • [0032]
    [0032]FIG. 6 depicts one embodiment of a keystream generator 89 that is used to decode an encoded image. The keystream generator 89 is one of a class of pseudo-random-sequence generators known as a linear feedback shift register (LFSR). The LFSR 89 includes two components: a shift register 91 and a feedback function 93. With each shifting of the shift register 91, a new most-significant bit 94 is output as part of the keystream, and an input bit 95 is inserted at the beginning of the shift register 91. In one embodiment, the shift register is shifted in response to a control signal (e.g., from control logic 65 of FIG. 4) that is asserted with each new program code value received. Other clocking sources may be used to shift the contents of shift register 91 in alternative embodiments.
  • [0033]
    The feedback function 93 is typically an exclusive-or combination of bits at selected bit positions of the shift register 91. These selected bit positions are referred to as taps. By appropriate selection of the taps, the LFSR 89 can be made to output a keystream that does not repeat until after 2 n−1 key bits have been generated, n being the number of bits in the shift register 91. In alternate embodiments, other circuits may be used to generate the keystream, including, but not limited to, combinations of LFSRs in which the output of one or more LFSRs are logically combined, used to select between outputs of other LFSRs, used to clock other LFSRs, and so forth.
  • [0034]
    According to one embodiment, a single bitstream generated by a keystream generator 89 is applied to decode a sequence of program code values. A single bit output by the keystream generator 89 may be applied to each bit of a program code word so that a word filled with all 1's or all 0's would be used to decode each word of program code. This is shown in FIG. 6 by the exclusive-or combination (element 86) of the most significant bit of the shift register 91 with each of the N-bits of a word of incoming program code. Alternatively, the keystream generator may be clocked so that N bits of the keystream are generated and respectively applied to each of the N-bits of an encoded word of program code. For example, each of the bits in an N-shift register could be respectively applied to the N-bits of an encoded word of program code. The shift register would then be clocked (i.e., shifted) N times to generate a new N-bit keyword for application to the next word of program code.
  • [0035]
    In another embodiment, N separate bitstreams may be generated by a keystream generator to produce a keyword made up of N different key bits. This may be accomplished, for example by providing N differently designed LFSR circuits that operate in parallel to generate the N-bit keyword, or by providing N identically designed LFSR circuits that are seeded differently (e.g., the shift registers of the individual LFSRs may be initialized to different values).
  • [0036]
    According to yet another embodiment, a transfer protocol may be defined in which one or more predetermined values are appended to the beginning of a program code sequence to seed the LFSR circuits. When the seed value prefix is received in the non-volatile memory, the seed values act to initialize the keystream generator to a predetermined state before the output of the keystream generator is applied to the succeeding program values. Logic may be included in the decoding logic to suppress storage of the seed values in the non-volatile storage array or the starting address at which the program code is to be stored may be adjusted to account for storage of the seed values.
  • [0037]
    Another non-volatile memory device comprises storage elements, reading circuitry to retrieve encoded data from the storage elements and to output the data on a data path, and decoding circuitry coupled to the reading circuitry to decode the encoded data retrieved from the storage elements before the reading circuitry outputs the data on the data path.
  • [0038]
    A sequence of encoded values is stored in storage elements of a non-volatile memory device. The encoded sequence of values is retrieved from the storage elements in response to a read request. The encoded sequence of values is decoded in a decoding circuit within the non-volatile memory device to generate a sequence of decoded values. The sequence of decoded values is output.
  • [0039]
    In the foregoing specification, the invention has been described with reference to specific exemplary embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention as set forth in the appended claims. The specification and drawings are, accordingly to be regarded in an illustrative rather than a restrictive sense.
Patent Citations
Cited PatentFiling datePublication dateApplicantTitle
US4694412 *Sep 30, 1985Sep 15, 1987Intel CorporationRandom number generator for use in an authenticated read-only memory
US5778070 *Jun 28, 1996Jul 7, 1998Intel CorporationMethod and apparatus for protecting flash memory
US5835594 *Feb 9, 1996Nov 10, 1998Intel CorporationMethods and apparatus for preventing unauthorized write access to a protected non-volatile storage
US5844986 *Sep 30, 1996Dec 1, 1998Intel CorporationSecure BIOS
US6026016 *May 11, 1998Feb 15, 2000Intel CorporationMethods and apparatus for hardware block locking in a nonvolatile memory
Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US6957335Oct 22, 2003Oct 18, 2005International Business Machines CorporationInitializing, maintaining, updating and recovering secure operation within an integrated system employing a data access control function
US7356707 *Oct 23, 2003Apr 8, 2008International Business Machines CorporationInitializing, maintaining, updating and recovering secure operation within an integrated system employing a data access control function
US8042176 *Jul 18, 2005Oct 18, 2011Fuji Xerox Co., Ltd.Computer readable medium on which is stored a program for preventing the unauthorized use of program data
US8321933 *Nov 14, 2007Nov 27, 2012Caterpillar Inc.Securing electronic control unit code
US8484752Nov 14, 2007Jul 9, 2013Caterpillar Inc.Verifying authenticity of electronic control unit code
US8843693May 17, 2011Sep 23, 2014SanDisk Technologies, Inc.Non-volatile memory and method with improved data scrambling
US8929961Jul 13, 2012Jan 6, 2015Blackbird Technology Holdings, Inc.Protective case for adding wireless functionality to a handheld electronic device
US9104548 *Jan 20, 2012Aug 11, 2015Blackbird Technology Holdings, Inc.Method and apparatus for memory management
US9166894Jul 7, 2014Oct 20, 2015Blackbird Technology Holdings, Inc.Method and apparatus for rapid group synchronization
US9325634Oct 21, 2014Apr 26, 2016Blackbird Technology Holdings, Inc.Method and apparatus for adaptive traffic management in a resource-constrained network
US9357425Mar 9, 2015May 31, 2016Blackbird Technology Holdings, Inc.Method and apparatus for adaptive searching of distributed datasets
US9379808May 22, 2015Jun 28, 2016Blackbird Technology Holdings, Inc.Method and apparatus for low-power, long-range networking
US9414342Nov 10, 2014Aug 9, 2016Blackbird Technology Holdings, Inc.Method and apparatus for query-based congestion control
US9425847Jan 6, 2015Aug 23, 2016Blackbird Technology Holdings, Inc.Protective case for adding wireless functionality to a handheld electronic device
US20030200454 *Apr 18, 2002Oct 23, 2003International Business Machines CorporationInitializing, maintaining, updating and recovering secure operation within an integrated system employing a data access control function
US20040083375 *Oct 23, 2003Apr 29, 2004International Business Machines CorporationInitializing, maintaining, updating and recovering secure operation within an integrated system employing a data access control function
US20060212858 *Jul 18, 2005Sep 21, 2006Mitsuhisa KameiComputer readable medium on which is stored a program for preventing the unauthorized use of program data
US20080175381 *Mar 27, 2008Jul 24, 2008International Business Machines CorporationE-fuses for storing security version data
US20080310622 *Mar 26, 2008Dec 18, 2008International Business MachinesE-fuses for storing security version data
US20090125985 *Nov 14, 2007May 14, 2009Traenkenschuh John LVerifying electronic control unit code
US20090126028 *Nov 14, 2007May 14, 2009Traenkenschuh John LSecuring electronic control unit code
US20120191901 *Jan 20, 2012Jul 26, 2012John Peter NorairMethod and apparatus for memory management
WO2003090402A1 *Apr 16, 2003Oct 30, 2003International Business Machines CorporationInitializing, maintaining, updating and recovering secure operation within an integrated system employing a data access control function
Classifications
U.S. Classification713/182
International ClassificationG06F9/445, G06F21/00
Cooperative ClassificationG06F8/65, G06F21/572
European ClassificationG06F8/65, G06F21/57A