Hello,
Fix committed to trunk (revision 4347). Could you please test it?
Thanks
Aleksey Samsonov wrote:
> Hello,
>
> Martin Paljak wrote:
>> Hello,
>>
>> On Apr 22, 2010, at 23:08 , Aleksey Samsonov wrote:
>>
>>> What are you think about solution in attachment? (openssl.cnf isn't
>>> needed in
Hello,
Martin Paljak wrote:
> Hello,
>
> On Apr 22, 2010, at 23:08 , Aleksey Samsonov wrote:
>
>> What are you think about solution in attachment? (openssl.cnf isn't needed
>> in this case)
>> Thanks
>> Index: src/pkcs11/openssl.c
>>
>
>> +#ifndef OPENSSL_NO_ENGINE
>> +ENGINE *e;
>> +
>> +
Hello,
On Apr 22, 2010, at 23:08 , Aleksey Samsonov wrote:
> What are you think about solution in attachment? (openssl.cnf isn't needed in
> this case)
> Thanks
> Index: src/pkcs11/openssl.c
>
> +#ifndef OPENSSL_NO_ENGINE
> + ENGINE *e;
> +
> +#if !defined(OPENSSL_NO_STATIC_ENGINE) && !def
Hello,
Jan Just Keijser wrote:
Hi Martin,
Martin Paljak wrote:
On Apr 22, 2010, at 00:25 , Jan Just Keijser wrote:
Hi Andreas,
Andreas Jellinghaus wrote:
hmm. if we had only one engine doing both rsa and gost, the
problem would be gone, without this "hack" required in opensc?
my po
Hi Martin,
Martin Paljak wrote:
> On Apr 22, 2010, at 00:25 , Jan Just Keijser wrote:
>
>> Hi Andreas,
>>
>> Andreas Jellinghaus wrote:
>>
>>> hmm. if we had only one engine doing both rsa and gost, the
>>> problem would be gone, without this "hack" required in opensc?
>>>
>>> my point of
On Apr 22, 2010, at 00:25 , Jan Just Keijser wrote:
> Hi Andreas,
>
> Andreas Jellinghaus wrote:
>> hmm. if we had only one engine doing both rsa and gost, the
>> problem would be gone, without this "hack" required in opensc?
>>
>> my point of view:
>> if so: I think that is the solution! please
Robert Relyea wrote:
> On 04/21/2010 02:25 PM, Jan Just Keijser wrote:
>
>> Hi Andreas,
>>
>>
>>
>>> or send patches for libp11/engine_pkcs11 to handle gost.
>>> (no idea how much work that would be - I'm quite clueless
>>> over there. also gost engine might be much better than the
>>> s
On 04/21/2010 02:25 PM, Jan Just Keijser wrote:
> Hi Andreas,
>
>
>> or send patches for libp11/engine_pkcs11 to handle gost.
>> (no idea how much work that would be - I'm quite clueless
>> over there. also gost engine might be much better than the
>> simple and hacky engine_pkcs11).
>>
>> but m
Hi Andreas,
Andreas Jellinghaus wrote:
> hmm. if we had only one engine doing both rsa and gost, the
> problem would be gone, without this "hack" required in opensc?
>
> my point of view:
> if so: I think that is the solution! please drop the stuff
> from opensc, and work in that direction.
>
> en
hmm. if we had only one engine doing both rsa and gost, the
problem would be gone, without this "hack" required in opensc?
my point of view:
if so: I think that is the solution! please drop the stuff
from opensc, and work in that direction.
engine_pkcs11.c is bsd3 / openssl license, and libp11
is
Aleksey Samsonov wrote:
> Hello,
>
> Jan Just Keijser wrote:
>> Martin Paljak wrote:
>>> On Apr 16, 2010, at 09:51 , Aleksey Samsonov wrote:
>>>
I commented out the OPENSSL_config(NULL) and now it works ...
> should this added as a patch? the FIXME seems to be to *remove*
>
Hello,
Jan Just Keijser wrote:
Martin Paljak wrote:
On Apr 16, 2010, at 09:51 , Aleksey Samsonov wrote:
I commented out the OPENSSL_config(NULL) and now it works ...
should this added as a patch? the FIXME seems to be to *remove* the
explicit call to OPENSSL_config; I can confirm that t
Hello,
Call OPENSSL_config(NULL) was need for loading GOST engine. It was need
for applications which use PKCS#11 (opensc-pkcs11.so) with GOST
algorithms and which don't use openssl directly (not call
OPENSSL_config(NULL)).
Jan was right, he wrote more detailed:
Jan Just Keijser wrote:
> the
Am Samstag 17 April 2010 16:30:02 schrieb Martin Paljak:
> Compatibility with OpenSSL 1.0 is a good reason for a new release but I've
> not yet understood if it really is a problem with OpenSC or OpenSSL
> (reading up)
as far as I understand the issue:
* the combination of openssl, gost engine
On Apr 16, 2010, at 19:40 , Andreas Jellinghaus wrote:
> Am Freitag 16 April 2010 01:16:47 schrieb Jan Just Keijser:
>> hi list,
>>
>> I hate to answer my own question but I think I found it:
>>
>> in opensc-0.11.13/src/pkcs11/openssl.c there's section
>>
>> 106 void
>> 107 sc_pkcs11_register_op
Hi Aleksey,
Aleksey Samsonov wrote:
> Hello,
>
> Andreas Jellinghaus wrote:
>
>> Am Freitag 16 April 2010 08:51:31 schrieb Aleksey Samsonov:
>>
>>> Hello,
>>>
>>> Jan Just Keijser wrote:
>>>
in opensc-0.11.13/src/pkcs11/openssl.c there's section
106 void
107 sc_p
Hello,
Andreas Jellinghaus wrote:
> Am Freitag 16 April 2010 08:51:31 schrieb Aleksey Samsonov:
>> Hello,
>>
>> Jan Just Keijser wrote:
>>> in opensc-0.11.13/src/pkcs11/openssl.c there's section
>>>
>>> 106 void
>>> 107 sc_pkcs11_register_openssl_mechanisms(struct sc_pkcs11_card *card)
>>> 108 {
>
Am Freitag 16 April 2010 08:51:31 schrieb Aleksey Samsonov:
> Hello,
>
> Jan Just Keijser wrote:
> > in opensc-0.11.13/src/pkcs11/openssl.c there's section
> >
> > 106 void
> > 107 sc_pkcs11_register_openssl_mechanisms(struct sc_pkcs11_card *card)
> > 108 {
> > 109 #if OPENSSL_VERSION_NUMBER >= 0x
Am Freitag 16 April 2010 01:16:47 schrieb Jan Just Keijser:
> hi list,
>
> I hate to answer my own question but I think I found it:
>
> in opensc-0.11.13/src/pkcs11/openssl.c there's section
>
> 106 void
> 107 sc_pkcs11_register_openssl_mechanisms(struct sc_pkcs11_card *card)
> 108 {
> 109 #if O
maybe an strace (strace -o strace.log -f -s -tt openssl ... )
will show what is wrong.
if possible put the file on a web page, as it could be huge,
too big for this list. if that isn't possible, compress
it and send it to me only (but no idea when I will be able
to look at it).
what you trie
Martin Paljak wrote:
> On Apr 16, 2010, at 09:51 , Aleksey Samsonov wrote:
>
>> I commented out the OPENSSL_config(NULL) and now it works ...
>>
>>> should this added as a patch? the FIXME seems to be to *remove* the
>>> explicit call to OPENSSL_config; I can confirm that this works for bo
On Apr 16, 2010, at 09:51 , Aleksey Samsonov wrote:
> I commented out the OPENSSL_config(NULL) and now it works ...
>>
>> should this added as a patch? the FIXME seems to be to *remove* the
>> explicit call to OPENSSL_config; I can confirm that this works for both
>> openssl-1.0.0-beta4 and the
Hi Aleksey,
Aleksey Samsonov wrote:
> Hello,
>
> Jan Just Keijser wrote:
>> in opensc-0.11.13/src/pkcs11/openssl.c there's section
>>
>> 106 void
>> 107 sc_pkcs11_register_openssl_mechanisms(struct sc_pkcs11_card *card)
>> 108 {
>> 109 #if OPENSSL_VERSION_NUMBER >= 0x1000L
>> 110 /* FIXME:
Hello,
Jan Just Keijser wrote:
> in opensc-0.11.13/src/pkcs11/openssl.c there's section
>
> 106 void
> 107 sc_pkcs11_register_openssl_mechanisms(struct sc_pkcs11_card *card)
> 108 {
> 109 #if OPENSSL_VERSION_NUMBER >= 0x1000L
> 110 /* FIXME: see openssl-1.0.0-beta3/engines/ccgost/README.g
hi list,
I hate to answer my own question but I think I found it:
in opensc-0.11.13/src/pkcs11/openssl.c there's section
106 void
107 sc_pkcs11_register_openssl_mechanisms(struct sc_pkcs11_card *card)
108 {
109 #if OPENSSL_VERSION_NUMBER >= 0x1000L
110 /* FIXME: see openssl-1.0.0-beta3/e
25 matches
Mail list logo
