[Cryptech-Commits] [core/util/keywrap] 64/95: Updated the info about max object size supports and number of banks.

[git at cryptech.is]

This is an automated email from the git hooks/post-receive script.

paul at psgd.org pushed a commit to branch master
in repository core/util/keywrap.

commit b75bd86d3cb8cfd540253b9e29a791582daf3945
Author: Joachim Strömbergson <joachim at secworks.se>
AuthorDate: Thu Aug 16 13:12:54 2018 +0200

    Updated the info about max object size supports and number of banks.
---
 README.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index 41430f1..9873ae0 100644
--- a/README.md
+++ b/README.md
@@ -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.