| commit | 06d8a4351b5b38227e805f4374a8297878515c9a | |
| author | Phil Sutter <phil.sutter@viprinet.com> | |
| Tue, 18 Jan 2011 12:18:29 +0000 (18 13:18 +0100) | ||
| committer | Nikos Mavrogiannopoulos <nmav@gnutls.org> | |
| Sat, 22 Jan 2011 11:14:19 +0000 (22 12:14 +0100) | ||
| tree | 8eaa57a032732ef9754b773de9b2d39ca7d6a537 | treesnapshot (tar.gz zip) |
| parent | 47e803d26cc4b843498bb5a694aa2c0548abe806 | commitdiff |
allow updating the IV in userspace
When the user has specified COP_FLAG_WRITE_IV in crypt_op.flags, the
updated IV will be written back to userspace. This is useful for
encryption of continuous data in several steps, without having to care
for each cipher's inerna.
Protecting this functionality by a flag allows for backwards
compatibility as well as using a read-only (i.e. const) buffer holding
the IV.
Signed-off-by: Nikos Mavrogiannopoulos <nmav@gnutls.org>
When the user has specified COP_FLAG_WRITE_IV in crypt_op.flags, the
updated IV will be written back to userspace. This is useful for
encryption of continuous data in several steps, without having to care
for each cipher's inerna.
Protecting this functionality by a flag allows for backwards
compatibility as well as using a read-only (i.e. const) buffer holding
the IV.
Signed-off-by: Nikos Mavrogiannopoulos <nmav@gnutls.org>
| cryptodev.h | diffblobblamehistory | |
| cryptodev_int.h | diffblobblamehistory | |
| cryptodev_main.c | diffblobblamehistory |