On Thu, 2004-10-21 at 21:18 +0200, Matjaz Rihtar wrote:
> But, when I tried to use it with Pine, I was constantly getting
> segmentation fault (SIGSEGV) inside PKCS7_encrypt.
Try again with OpenSSL 0.9.7e, a bug introduced in 0.9.7d was fixed for
PKCS7 Encryption.
Sincerely,
--
Mathias Br
ature/verification (detached or not), encryption/decryption.
I'm probably missing something but it seems like making a special kind
of ASN1_STRING that is mapped to a read-only file interval BIO might
solve a big piece of the jo
y asked :)
> In this case I suspect that CRYPTO_cleanup_all_ex_data() should be
> called because calling RSA_new() will allocate an internal ex_data
> table.
Wouldn't it be nice to have a function that would call all these
clean-up functions ?
Sincerely,
--
On Fri, 2003-09-05 at 19:59, Ben Laurie wrote:
> Mathias Brossard wrote:
> > - Asymmetric: DSA, RSA, ECDSA
>
> Not my understanding. Anyway, DSS only. RSA can't be, and ECDSA we
> aren't doing.
It's a little disappointing that RSA is not part of the pro
; should be
approximately:
- Symmetric: AES, DES, 3DES, Skipjack
- Asymmetric: DSA, RSA, ECDSA
- Message Authentication: DES MAC, Triple DES MAC
- Hash: SHA-1
- Keyed Hash: HMAC
- RNG: FIPS 186-2 (Appendix 3.1 & 3.2), ANSI X9.31 and ANS
