Hi Stephen,
I could not spot in the kernel where we are computing GHASH when the
IV is bigger than 12 Bytes for GCM encryption.
libkcapi and kernel appears to ignore the bytes beyond 12th byte in the IV.
SO the o/p is same with iv=12 bytes or iv=128 bytes as can be seen below:
jlulla@ubuntu:~/li
Hi,
Consider the following 2 invocations from kcapi and the results we get
from it. They are not matching with the NIST vectors [links pasted
below].
Could somebody please tell why that could be happening?
thanks
JItendra
https://csrc.nist.gov/CSRC/media/Projects/Cryptographic-Algorithm-Validat
Hi,
the following NIST link has test vectors for SHA1/2/3.
https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program/secure-hashing
They have test vectors for bit oriented messages also e.g. a message
of 7 bits for example. [grep "Bit-Oriented" on the page, bottom of the
page]
So
Hi,
http://lwn.net/Articles/410848/
The following code is taken from the above page:
int main(void)
{
int opfd;
int tfmfd;
struct sockaddr_alg sa = {
.salg_family = AF_ALG,
.salg_type = "skcipher",
.salg_name = "cbc(aes)"
};
struct msghdr msg = {};
struct cmsghdr *cmsg;
char cbuf[CMSG_SPACE(4) +
Hi,
This is regarding the hash computation over a file with AF_ALG from
user space. [without OpenSSL]
The following link has the mail from Herbert with subject : "RFC:
Crypto API User-interface"
http://lwn.net/Articles/410848/
I was trying to take help from the code snippet he has put in his mai
