Ludovic Rousseau wrote:
> > what is the best way to find a fair solution?
>
> Maybe create a section "orphaned" or "unmaintained"
> with gtkcard and scb in it?
"Mature" is a nice term. :)
//Peter
___
opensc-devel mailing list
opensc-devel@lists.opensc
2009/10/20 Andreas Jellinghaus :
> the current entries are
> opensc openct
> scb pam_pkcs11
> sca pam_p11
> engine_pkcs11 libp11
> gtkcard opensc-java
> pkcs11-helper opensc build
>
> shouldn't we reorder this?
>
On 10/20/2009 02:56 AM, David Smith wrote:
> On Tue, Oct 20, 2009 at 6:47 PM, Alon Bar-Lev wrote:
>
>> Oh... I really don't know libp11...
>> But if one process called C_Initialize() and then another/same thread
>> called C_Initialize() again and calls C_Finalize, first thread will
>> not be ab
One of those warning for card-piv.c is actually a bug.
Attached is a patch to remove the variable not initialized error
for "tag", and to fix another error when loading a 3des key when
the string passed to sc_hex_to_bin is not terminated.
Both this patch and the westcos Openssl-0.9.7 are agains
Andreas Jellinghaus wrote:
Am Dienstag 20 Oktober 2009 17:08:31 schrieb Alessandro Premoli:
Andreas Jellinghaus ha scritto:
OpenSC 0.11.10 released today now includes a new driver "westcos"
This raised the requirements with OpenSSL 0.9.8, while previously opensc
could be compiled also with
Andreas Jellinghaus ha scritto:
> thanks for reporting, I was not aware of that. Can you post the error messages
> you get, if openssl 0.9.7 is used for compiling?
westcos files use the openssl 0.9.8 RSA_generate_key_ex() function. In
0.9.7 there is only RSA_generate_key().
> if we can make a sma
I too do not know any reasonb why openssl-0.9.7 should not work.
On Tue, Oct 20, 2009 at 5:36 PM, Andreas Jellinghaus
wrote:
> Am Dienstag 20 Oktober 2009 17:08:31 schrieb Alessandro Premoli:
>> Andreas Jellinghaus ha scritto:
>> > OpenSC 0.11.10 released today now includes a new driver "westcos
Am Dienstag 20 Oktober 2009 17:08:31 schrieb Alessandro Premoli:
> Andreas Jellinghaus ha scritto:
> > OpenSC 0.11.10 released today now includes a new driver "westcos"
>
> This raised the requirements with OpenSSL 0.9.8, while previously opensc
> could be compiled also with 0.9.7. Is it intentiona
Here is a statistic for warnings from opensc code:
4 card-entersafe.c
2 card-myeid.c
19 cardos-tool.c
2 card-piv.c
6 card-westcos.c
1 eidenv.c
12 libtool
2 mechanism.c
2 misc.c
3 muscle.c
13 openssl.c
3 p15emu-westcos.c
2 pk
the current entries are
opensc openct
scb pam_pkcs11
sca pam_p11
engine_pkcs11 libp11
gtkcard opensc-java
pkcs11-helper opensc build
shouldn't we reorder this?
* scb is outdated, lets move it last,
Libp11 0.2.7 released today fixes a small bug: If C_Initialize
returns CKR_CRYPTOKI_ALREADY_INITIALIZED, that is ok and is not
ignored. That way applications like wpa_supplicant can unload and
reload pkcs11 modules without issues.
http://www.opensc-project.org/files/libp11/libp11-0.2.7.tar.gz
Eng
Thanks Andreas!
2009/10/20 Andreas Jellinghaus
> Hi David,
>
> thanks for both patches, they look good to me so I applied them
> right away.
>
> Regards, Andreas
> ___
> opensc-devel mailing list
> opensc-devel@lists.opensc-project.org
> http://www.ope
Hi David,
thanks for both patches, they look good to me so I applied them
right away.
Regards, Andreas
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
On Tue, Oct 20, 2009 at 6:47 PM, Alon Bar-Lev wrote:
> Oh... I really don't know libp11...
> But if one process called C_Initialize() and then another/same thread
> called C_Initialize() again and calls C_Finalize, first thread will
> not be able to continue working.
>
That could be an acceptable
On Tue, Oct 20, 2009 at 6:41 PM, Alon Bar-Lev wrote:
> For the C_Initialize() patch... If you got already initialize you
> should not call C_Finalize.
Can you explain more? How should the handling look like with libp11?
>
>
> On Tue, Oct 20, 2009 at 11:23 AM, David Smith
> wrote:
>> Hi OpenSC f
Oh... I really don't know libp11...
But if one process called C_Initialize() and then another/same thread
called C_Initialize() again and calls C_Finalize, first thread will
not be able to continue working.
On Tue, Oct 20, 2009 at 11:45 AM, David Smith
wrote:
> On Tue, Oct 20, 2009 at 6:41 PM, Al
For the C_Initialize() patch... If you got already initialize you
should not call C_Finalize.
On Tue, Oct 20, 2009 at 11:23 AM, David Smith
wrote:
> Hi OpenSC folks,
>
> While debugging some issues with pkcs#11 related handling in
> wpasupplicant, I found two small bugs that I'm sending patches
Hi OpenSC folks,
While debugging some issues with pkcs#11 related handling in
wpasupplicant, I found two small bugs that I'm sending patches for.
Both are related to attempting to reuse pkcs#11 modules in one
process, something that wpasupplicant does when switching to and from
networks that one w
18 matches
Mail list logo
