Deprecated: Since 5.0.0: Calling Table::get() with options array is deprecated. Use named arguments instead. /application/src/Controller/ParagraphsController.php, line: 67 You can disable all deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED`. Adding `src/Controller/ParagraphsController.php` to `Error.ignoredDeprecationPaths` in your `config/app.php` config will mute deprecations from that file only. in /application/vendor/cakephp/cakephp/src/Core/functions.php on line 377

Warning: Unable to emit headers. Headers sent in file=/application/vendor/cakephp/cakephp/src/Core/functions.php line=377 in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 65

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 158

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 191

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 191

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 228
Dave's PCF WIP: Paragraphs

3180

Application Systems and methods for persistent deallocation
Matter Number US8762658B2 Reference Case 1 US8762658B2
Created 3/24/21, 12:00 AM Modified 3/24/21, 12:00 AM
Application Number
Paragraph Number

13

Content

In one embodiment, the apparatus includes a secure erase module that overwrites existing data with characters such that the existing data is non-recoverable. The existing data includes data of a data segment previously stored on the storage device identified with the same data segment identifier as the data segment identified in the storage request. In a further embodiment, the secure erase module further includes an erase confirmation module that transmits a message indicating that the existing data has been overwritten. The erase confirmation message is transmitted in response to the secure erase module overwriting the existing data. In another embodiment, the secure erase module overwrites the existing data during a storage space recovery operation. In another embodiment, the storage request includes a request to overwrite the existing data and the secure erase module overwrites the existing data in response to the request to overwrite the existing data.

Notes

Added by DJM 3 2021