Fixed in latest OpenSSL, ticket closed.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
__
OpenSSL Project http://w
Greetings!
It seems to be not enough.
openssl is built with "shared" option
the config is
openssl_conf = openssl_def
[openssl_def]
engines = engine_section
[engine_section]
gost = gost_section
[gost_section]
engine_id = gost
default_algorithms = ALL
CRYPT_PARAMS = id-Gost28147-89-Crypto
Greetings!
It seems to be not enough.
openssl is built with "shared" option
the config is
openssl_conf = openssl_def
[openssl_def]
engines = engine_section
[engine_section]
gost = gost_section
[gost_section]
engine_id = gost
default_algorithms = ALL
CRYPT_PARAMS = id-Gost28147-89-Crypto
Stephen Henson via RT wrote:
> I've finally had time to look into this. Please see if this fixes the issue:
May be is not related, but this engine lack call of
ENGINE_register_pkey_asn1_meths . It seems to me without this
registration initialization is different . If engine configuration is
wit
Stephen Henson via RT wrote:
I've finally had time to look into this. Please see if this fixes the issue:
May be is not related, but this engine lack call of
ENGINE_register_pkey_asn1_meths . It seems to me without this
registration initialization is different . If engine configuration is
wit
I've finally had time to look into this. Please see if this fixes the issue:
http://cvs.openssl.org/chngview?cn=22789
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
___
Greetings!
I see, thank you!
What about #2744?
On Wed, Feb 29, 2012 at 10:56 PM, Stephen Henson via RT
wrote:
>> [beld...@gmail.com - Wed Feb 29 19:41:11 2012]:
>>
>> Greetings!
>>
>> If I implement the patch you describe would it be accepted?
>>
>
> Yes. One way is to check with ENGINE_by_id
Greetings!
I see, thank you!
What about #2744?
On Wed, Feb 29, 2012 at 10:56 PM, Stephen Henson via RT
wrote:
>> [beld...@gmail.com - Wed Feb 29 19:41:11 2012]:
>>
>> Greetings!
>>
>> If I implement the patch you describe would it be accepted?
>>
>
> Yes. One way is to check with ENGINE_by_id
> [beld...@gmail.com - Wed Feb 29 19:41:11 2012]:
>
> Greetings!
>
> If I implement the patch you describe would it be accepted?
>
Yes. One way is to check with ENGINE_by_id to see if the GOST ENGINE
already exists. The call to ENGINE_add will also fail but that's rather
too late. Alternatively
Greetings!
If I implement the patch you describe would it be accepted?
On Wed, Feb 29, 2012 at 10:29 PM, Stephen Henson via RT
wrote:
> I think the best way to deal with this is to cope attempts to load the
> ENGINE multiple times. This could be treated as a hard error or just
> returning a cop
Greetings!
If I implement the patch you describe would it be accepted?
On Wed, Feb 29, 2012 at 10:29 PM, Stephen Henson via RT
wrote:
> I think the best way to deal with this is to cope attempts to load the
> ENGINE multiple times. This could be treated as a hard error or just
> returning a cop
I think the best way to deal with this is to cope attempts to load the
ENGINE multiple times. This could be treated as a hard error or just
returning a copy of the already loaded ENGINE.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: htt
-- Forwarded message --
From: Dmitry Belyavsky
Date: Mon, Sep 12, 2011 at 12:51 PM
Subject: GOST engine memory problems
To: r...@openssl.org, openssl-dev@openssl.org
Greetings!
When we load the GOST engine twice (because of misconfiguration or
so), the problems with memory manag
13 matches
Mail list logo
