diff options
author | Joachim StroĢmbergson <joachim@secworks.se> | 2018-08-16 13:12:54 +0200 |
---|---|---|
committer | Joachim StroĢmbergson <joachim@secworks.se> | 2018-08-16 13:12:54 +0200 |
commit | b75bd86d3cb8cfd540253b9e29a791582daf3945 (patch) | |
tree | 3d7482713cea442918cf32fcfca3342473c2f9fe | |
parent | 5a96b9a1c664ee43e27631e326655dca818ab837 (diff) |
Updated the info about max object size supports and number of banks.
-rw-r--r-- | README.md | 12 |
1 files changed, 6 insertions, 6 deletions
@@ -5,8 +5,8 @@ This core implememts AES KEY WRAP as defined in [RFC 3394](https://tools.ietf.org/html/rfc3394) and the keywrap with padding according to [RFC 5694](https://tools.ietf.org/html/rfc5649) -The core supports wrap/unwrap of objects up to 32 kbits in size. The -core supports 128 and 256 bit keys. +The core supports wrap/unwrap of objects up to 64 kByte in size. +The core supports 128 and 256 bit wrapping keys. ## Status ## @@ -53,7 +53,7 @@ magic block) into the RLEN register. Finally the caller needs to write the wrapping key. Due to address space limitations in the Cryptech cores (with 8-bit -address space) the object storage is divided into banks (bank -0..3). Each bank supports 4096 bits. For objects lager than 4096 bits, -it is the callers responsibilty to switch banks when reading and writing -to the storage. +address space) the object storage is divided into banks [0 .. 127]. Each +bank supports 128 32-bit words or 4096 bits. For objects lager than 4096 +bits, it is the callers responsibilty to switch banks when reading and +writing to the storage. |