* @enum odp_cipher_alg:ODP_CIPHER_ALG_NULL
 * No cipher algorithm specified

Is this comment correct?
Don't we actually mean "Null cipher algorithm"?
The null algorithm is a valid cipher algorithm, it just doesn't
provide much security....

Should we define ciphers like AES well? Didn't the original crypto
proposal specify a more complete  of cipher algorithms?

Does the crypto implementation have to know about the mode (e.g. CBC,
CTR)? Cipher 3DES is defined with CBC mode. For counter mode each
block has its own counter value and it could be specified by the user
if each block is passed for encryption/decryption separately. How
large is a block supposed to be? A packet?

Can crypto.h be extended to asymmetric (public/private key)
encryption/decryption as well? Do we need new calls and data
structures or just some new enums?

-- Ola

_______________________________________________
lng-odp mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/lng-odp

Reply via email to