I'm working on a C++ security library solution that uses openssl internally.
It offers Sign/Verify, Digest and Encrypt/Decrypt as its features (please
check available methods below).
I'm using FIPS 2.0 test vectors to validate my library, but I'm having a bit
of trouble with that.
Testing
Thanks for both answers.
I tried using Y as the public key, but ssl seems not to accept that.
Here is the error scenario:
From the FIP file:
[mod = 1024]
P =
fda5442483ccf7a12399d6c13d56ff882d689524f1885fcb7424e26da2d200a1657b631dcc74
,
based on p, q, g and y?
De: openssl-users [mailto:openssl-users-boun...@openssl.org] Em nome de
Marcus Vinicius do Nascimento
Enviada em: terça-feira, 12 de maio de 2015 17:06
Para: openssl-users@openssl.org
Assunto: [openssl-users] RES: Testing OpenSSL based solution
Thanks for both
From: openssl-users On Behalf Of Marcus Vinicius do Nascimento
Sent: Tuesday, May 12, 2015 16:50
I did some quick research and found this:
http://en.wikipedia.org/wiki/Digital_Signature_Algorithm
If my understanding is correct, the public key is (p, q, g, y).
You might want to look
Hello,
I'm trying to use the CFB1 mode for AES-128.
However I'm having a bit of trouble interpreting the encrypt output.
I believe the EVP_EnvryptUpdate should get the data length in BITS (other
algorithms it should use in bytes). Is it correct?
How can I interpret the output correctly?
Hi there,
I've been trying to use DES_EDE3_CFB1 encryption in openssl version 1.0.1f
but I couldn't make it work correctly.
My understanding is that EVP_CipherUpdate is expecting the input data length
(inl) in bytes, not bits as expected.
I tried digging a little the GitHub repository but
