summaryrefslogtreecommitdiffstats
path: root/share
diff options
context:
space:
mode:
authorjmg <jmg@FreeBSD.org>2015-07-03 01:55:06 +0000
committerjmg <jmg@FreeBSD.org>2015-07-03 01:55:06 +0000
commitac82978a2d5a7d501dd96eafc3d5f05f1d0c1e77 (patch)
tree1522011df3a84ffd226e34c06d334828e9c3cda6 /share
parent33d849db59d9bfa76cb96479395ccbcb126d639e (diff)
downloadFreeBSD-src-ac82978a2d5a7d501dd96eafc3d5f05f1d0c1e77.zip
FreeBSD-src-ac82978a2d5a7d501dd96eafc3d5f05f1d0c1e77.tar.gz
more word smithing wrt the crd_inject field...
We've already defined IV earlier, so no need to expand it a second time here...
Diffstat (limited to 'share')
-rw-r--r--share/man/man9/crypto.912
1 files changed, 7 insertions, 5 deletions
diff --git a/share/man/man9/crypto.9 b/share/man/man9/crypto.9
index 3c4dae3..d7bee01 100644
--- a/share/man/man9/crypto.9
+++ b/share/man/man9/crypto.9
@@ -356,10 +356,12 @@ How many bytes, after
.Va crd_skip ,
should be processed.
.It Va crd_inject
-Offset from the beginning of the buffer to insert any results.
-For encryption algorithms, this is where the initialization vector
-(IV) will be inserted when encrypting or where it can be found when
-decrypting (subject to
+The
+.Va crd_inject
+field specifies an offset in bytes from the beginning of the buffer.
+For encryption algorithms, this may be where the IV will be inserted
+when encrypting or where the IV may be found for
+decryption (subject to
.Va crd_flags ) .
For MAC algorithms, this is where the result of the keyed hash will be
inserted.
@@ -393,7 +395,7 @@ provided by the consumer in the
field.
Otherwise, for encryption operations the IV is provided for by
the driver used to perform the operation, whereas for decryption
-operations it is pointed to by the
+operations the offset of the IV is provided by the
.Va crd_inject
field.
This flag is typically used when the IV is calculated
OpenPOWER on IntegriCloud