|Cell/B.E. Security SDK: SFS resource: Implementation details (SDK 3.0)||INFObomb|
|A quick read introducing the Secure File System (SFS) resource which provides a set of APIs that implement reading and writing encrypted and verified files in the Security SDK 3.0; a closer look at implementation||More INFObombs|
The secure file system (SFS) resource delivers a set of APIs that implement reading and writing encrypted and verified files. The model follows the standard I/O
In this mini-series, we'll look at:
Let's look at implementation issues.
For the publicly available version of the SDK, XOR with a static key is used for the data encryption and a cyclic redundancy check (CRC) is used for data verification. For the CDA version of the SDK, symmetric cryptography is used for data encryption and SHA-1 is used for data verification.
The SFS resource maintains information about each open file. This includes the current header section, the verification section, a data buffer, and additional navigation information. The total overhead for this information is approximately
Editor's note: This is the third skills module on the Cell/B.E. Security SDK > Secure file system resource. (You can jump ahead to the original documentation if you want to pursue this topic further before the other installments are available.) Other parts of this mini-series include
Taken from the Cell BE Security SDK v3.0 Installation and User's Guide. Download the SDK 3.0. Check out some reference guides in the Cell Resource Center SDK library.
|ORIGINAL DOCUMENTATION | DOWNLOAD SDK 3.0 | SDK 3.0 LIBRARY | MORE INFObombs | BACK to BLOG | BACK to ZONE|