Abstract: Methods and apparatus teach wear leveling non-volatile memory and secure erasure of data. A computing device receives data to be stored. The data is encrypted, including generation of encryption/decryption key(s). The key(s) are stored in either non-volatile or volatile memory according to a plurality of classification schemes. In a first scheme, key(s) are stored in non-volatile memory and will be retained in the event of a power cycle of the computing device. Otherwise, key(s) stored in volatile memory will be lost upon a power cycle. Upon issuance of a key destruction command, key(s) in the non-volatile memory are sanitized or erased, but the underlying encrypted data need not be erased since no key(s) exist that can recover original content. These techniques limit erasure commands to the non-volatile memory which prolongs its service life. Further embodiments note techniques in imaging devices conducting imaging operations, such as printing or scanning.

Abstract: Methods and apparatus teach wear leveling non-volatile memory and secure erasure of data. A computing device receives data to be stored. The data is encrypted, including generation of encryption/decryption key(s). The key(s) are stored in either non-volatile or volatile memory according to a plurality of classification schemes. In a first scheme, key(s) are stored in non-volatile memory and will be retained in the event of a power cycle of the computing device. Otherwise, key(s) stored in volatile memory will be lost upon a power cycle. Upon issuance of a key destruction command, key(s) in the non-volatile memory are sanitized or erased, but the underlying encrypted data need not be erased since no key(s) exist that can recover original content. These techniques limit erasure commands to the non-volatile memory which prolongs its service life. Further embodiments note techniques in imaging devices conducting operations, such as printing or scanning.

Abstract: Methods and apparatus teach wear leveling non-volatile memory and secure erasure of data. A computing device receives data to be stored. The data is encrypted, including generation of encryption/decryption key(s). The key(s) are stored in either non-volatile or volatile memory according to a plurality of classification schemes. In a first scheme, key(s) are stored in non-volatile memory and will be retained in the event of a power cycle of the computing device. Otherwise, key(s) stored in volatile memory will be lost upon a power cycle. Upon issuance of a key destruction command, key(s) in the non-volatile memory are sanitized or erased, but the underlying encrypted data need not be erased since no key(s) exist that can recover original content. These techniques limit erasure commands to the non-volatile memory which prolongs its service life. Further embodiments note techniques in imaging devices conducting imaging operations, such as printing or scanning.

Abstract: A printer is provided which has a special Emulation Manager function as well as a “code sniffer” function, in which print data received is sent to a code sniffer buffer. A code sniffer function automatically determines the type of emulator that should be called to perform the interpretation or rendering of this print job, and if the code sniffer determines that the correct emulator is PostScript, then the code sniffer scans the data for any “special tokens.” If a special token is found, the PostScript emulator determines if the special token string data is part of a PostScript comment. If it is in the correct format, then the PostScript emulator sets the “mode flag” to the “MacBinary” state, and the code sniffer ceases any further filtering of control characters and disables any change of emulator command that may be received during this print job.

Abstract: A printer is provided which has a special Emulation Manager function as well as a “code sniffer” function, in which print data received is sent to a code sniffer buffer. A code sniffer function automatically determines the type of emulator that should be called to perform the interpretation or rendering of this print job, and if the code sniffer determines that the correct emulator is PostScript, then the code sniffer scans the data for any “special tokens.” If a special token is found, the PostScript emulator determines if the special token string data is part of a PostScript comment. If it is in the correct format, then the PostScript emulator sets the “mode flag” to the “MacBinary” state, and the code sniffer ceases any further filtering of control characters and disables any change of emulator command that may be received during this print job.