I released a new version of libp11 today.
What needs to be done for openct and opensc?
are there other projects that need new releases?
Changes from Aleksey for rutoken and Douglas for PIV
are already commited, but I haven't heard back from
martin about the sc_error -> sc_debug changes.
Anything
Hello,
Andreas Jellinghaus:
> are there other changes/patches/projects that I forgot
> and that need to be applied / need new releases too?
Could you please apply the pkcs15-rutoken.c and pkcs15-rtecp.c patches I
sent on 7/17/2009 to the next release?
Thanks
Am Dienstag 21 Juli 2009 22:35:50 schrieb Douglas E. Engert:
> Andreas,
> Can you add the card-piv.c and pkcs15-piv.c patches I sent
> on 7/16/2009 as piv-patch.20090716 as part of ticket #189
> to the next release?
sure, commited. thanks for the patches and testing!
Regards, Andreas
__
Thanks.
Boarman, Christopher L wrote:
> Doug,
>
> Great job on the fix.
Thanks.
Andreas,
Can you add the card-piv.c and pkcs15-piv.c patches I sent
on 7/16/2009 as piv-patch.20090716 as part of ticket #189
to the next release?
--
Douglas E. Engert
Argonne National Laboratory
9700
hristopher L
Subject: Re: [opensc-devel] New releases?
Andreas Jellinghaus wrote:
> Hi,
>
> which projects need new releases, and what changes
> should go in before?
>
> I'm aware off:
> * libp11 needs a new release because the new function
> wasn't added to
Andreas Jellinghaus wrote:
> Hi,
>
> which projects need new releases, and what changes
> should go in before?
>
> I'm aware off:
> * libp11 needs a new release because the new function
> wasn't added to the export file.
Yes, as the openssl engine will can not load because of the
missing en
2009/7/17 Andreas Jellinghaus :
> Patches not yet applied:
> * martins patch to remove sc_error and related code.
> I'm all for it, had an even larger rewrite in the
> past.
> * douglas changes to the piv code.
>
> I'm not sure if it would be better to have a new release
> now and another release
Hi,
which projects need new releases, and what changes
should go in before?
I'm aware off:
* libp11 needs a new release because the new function
wasn't added to the export file.
* opensc has a number of changes, so a new release would
be good.
* openct has updates for a new rutoken driver
P
Andreas Jellinghaus wrote:
> Hi,
>
> maybe I can find some time to at least put out some new releases
> of everything (that has changes). is this a good idea?
Not sure if it a good idea to produce a release before Christmas.
What you want it to produce a pre release and get developers
to test i
> not sure if they follow this mailing list.
pkcs11-tool for Rutoken S is not yet supported (have problems).
pkcs15-tool is supported (almost all options).
Andreas Jellinghaus:
> Hi Pavel,
>
> can you check with the rutoken authors?
> not sure if they follow this mailing list.
> I neither hav
Hi Pavel,
can you check with the rutoken authors?
not sure if they follow this mailing list.
I neither have a token nor documentation (nor time right now),
so I can't be of any help.
rutoken is a new driver, so if it is not working 100% so far,
that is not a show stopper for the next release. but
Andreas Jellinghaus wrote:
> Hi,
>
> maybe I can find some time to at least put out some new releases
> of everything (that has changes). is this a good idea?
>
> are there any patches waiting for a merge?
> and show-stopper bugs we should fix before (or patched to undo
> if they don't work ok righ
Hi.
I have a bunch of other code changes waiting to be sent for comments/
commiting before beginning of january but I've been pre-occupied with
my 1st son who arrived (a bit early) a week ago, so the work has to
wait a bit yet there is a deadline of 2nd of January.
The list-token thing of co
On 12/17/08, Andreas Jellinghaus wrote:
> > As we discussed in the mailing list, I don't like the new addition
> > martin added to pkcs11-tool, adding new standalone option
> > --list-token-slots instead of modifier to --list-slots... No blocker,
> > but change in interface of tools should be
Am Mittwoch, 17. Dezember 2008 20:20:17 schrieb Alon Bar-Lev:
> Windows (32bit, 64bit) build is OK.
>
> As we discussed in the mailing list, I don't like the new addition
> martin added to pkcs11-tool, adding new standalone option
> --list-token-slots instead of modifier to --list-slots... No block
Hi,
Windows (32bit, 64bit) build is OK.
As we discussed in the mailing list, I don't like the new addition
martin added to pkcs11-tool, adding new standalone option
--list-token-slots instead of modifier to --list-slots... No blocker,
but change in interface of tools should be considered as stati
Hi,
maybe I can find some time to at least put out some new releases
of everything (that has changes). is this a good idea?
are there any patches waiting for a merge?
and show-stopper bugs we should fix before (or patched to undo
if they don't work ok right now)?
alon, can you check if trunk is
On 10/4/08, Andreas Jellinghaus <[EMAIL PROTECTED]> wrote:
> alon, can you check if the windows/mingw build still works fine?
Ready.
Alon.
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinf
Hi,
I think we should publish new releases with the recent fixes
for the build systems. for example debian and ubuntu still
have old opensc releases, with the recent fixes it should be
much easier for them to update to the new versions.
is there anything we need to fix now before doing a new rele
19 matches
Mail list logo
