Greetings!
Here is the patch providing CMS support for ccgost engine.
--
SY, Dmitry Belyavsky
diff -u openssl-1.0.0e_orig/engines/ccgost//gost_ameth.c openssl-1.0.0e/engines/ccgost//gost_ameth.c
--- openssl-1.0.0e_orig/engines/ccgost//gost_ameth.c 2012-02-26 00:04:16.0 +0400
+++ openssl-
Greetings!
A memory leak occurs in openssl 1.0.0e
OpenSSL cmdline: /home/beldmit/cengine/openssl-1.0.0e/apps/openssl
dgst -mac gost-mac -macopt
hexkey:414243444546474849404142434445464748494041424344454647484940
dgst.dat
STDERR CONTENTS:
MAC parameter error
"hexkey:41424344454647484940414243444
Greetings!
A memory leak occurs in openssl 1.0.0e
OpenSSL cmdline: /home/beldmit/cengine/openssl-1.0.0e/apps/openssl
dgst -mac gost-mac -macopt
hexkey:414243444546474849404142434445464748494041424344454647484940
dgst.dat
STDERR CONTENTS:
MAC parameter error
"hexkey:41424344454647484940414243444
Greetings!
The problem occurs with cms resign command (openssl-1.0.0e).
$ openssl cms -sign -binary -inform der -inkey U_cms_1/seckey.pem
-signer U_cms_1/cert.pem -in signed_cms2.dat -out
signed_cms2_1_det.msg -outform smime
$ openssl cms -resign -binary -inkey U_cms_2/seckey.pem -signer
U_cms_2
ms/nt.mak and ms/ntdll.mak end up with
FIPSDIR=C:\\
BASEADDR=...
and the trailing \ quotes the line ending. Or something, anyway it
doesn't work.
I didn't notice that earlier because I send an incorrect suggestion for
PR: 2708; mine changed just the first / which isn't what was inten
ssl3_shutdown() incorrectly indicates SSL_want_read() or
SSL_want_write() when the underlying read/write results in a permanent
error. This means that callers of nonblocking SSL_shutdown() will go
into an infinite loop retrying the shutdown.
This bug appears in both OpenSSL 0.9.8t and 1.0.1-bet
Greetings!
The problem occurs with cms resign command (openssl-1.0.0e).
$ openssl cms -sign -binary -inform der -inkey U_cms_1/seckey.pem
-signer U_cms_1/cert.pem -in signed_cms2.dat -out
signed_cms2_1_det.msg -outform smime
$ openssl cms -resign -binary -inkey U_cms_2/seckey.pem -signer
U_cms_2
Hi devel list,
I have a need to limit the outgoing record size on a TLS connection.
What is the best way to do it?
The default size is 16K defined as a macro in the code. I could not find
an API to change this and recompiling with a new value changes both the
in and out size. What would be id
>>> In Debian we ship several versions of the shared libraries on i386.
>>> One that's build the default instruction set of that architecture
>>> (which is still i486 I think), and then 2 optimised versions,
>>> one for 586 and one for 686. The 586 and 686 versions use the
>>> assembler and so hav
Hi,
I was working on some project at work and was in the need for RSA
encrypt/decrypt operation with OAEP SHA256 padding - but I could not find
the ability to do so.
It seems like there is only support for padding of OAEP SHA1.
Is this correct, or did I miss this ability?
If I write code that imple
On Mon, 27 Feb 2012, Stephen Henson via RT wrote:
OK thanks it works fine now. The cause is rather subtle: when OpenSSL
reencodes a BIT STRING it normally preserves the original encoding so
this shouldn't happen. However in the case of a BIT STRING inside a Name
(X509_NAME) structure it didn't d
On Mon, 27 Feb 2012, Remi Gacogne wrote:
You're right, I'm sorry, I have mixed it up with another test.
This one is the right one.
Ok, just checked by downloading the certificate from RT, and it is
corrupted again.
I can't think of any other way that putting it here :
http://coredump.fr/op
Hi,
The certificate example you gave seems to be corrupted: the parse
rejects it and it never calls i2c_ASN1_BIT_STRING().
You're right, I'm sorry, I have mixed it up with another test.
This one is the right one.
Thank you for looking into this issue !
Regards,
Remi Gacogne
openssl-1.0.
13 matches
Mail list logo
