On Feb 4, 2011, at 2:11 PM, Toni Sjöblom - Aventra wrote:
> Hi,
>
>> -Original Message-
>> From: Andre Zepezauer [mailto:andre.zepeza...@student.uni-halle.de]
>> Sent: 23. tammikuuta 2011 4:45
>>
>> On Sat, 2011-01-22 at 15:42 +0200, Martin Paljak wrote:
>>> On Jan 21, 2011, at 9:33 AM,
Hi,
> -Original Message-
> From: Andre Zepezauer [mailto:andre.zepeza...@student.uni-halle.de]
> Sent: 23. tammikuuta 2011 4:45
>
> On Sat, 2011-01-22 at 15:42 +0200, Martin Paljak wrote:
> > On Jan 21, 2011, at 9:33 AM, Aventra wrote:
> > > Could this fix that Andre has proposed be commi
On Sat, 2011-01-22 at 15:42 +0200, Martin Paljak wrote:
> On Jan 21, 2011, at 9:33 AM, Aventra wrote:
> > Could this fix that Andre has proposed be committed to trunk?
> > It should work for all cards, since it only makes two elements of the
> > TokenInfo optional.
> Yes, but I'm not able to direc
On Jan 21, 2011, at 9:33 AM, Aventra wrote:
> Could this fix that Andre has proposed be committed to trunk?
> It should work for all cards, since it only makes two elements of the
> TokenInfo optional.
Yes, but I'm not able to directly locate the relevant part in the ASN.1
description (for objId
Sent: 10. tammikuuta 2011 16:24
> To: Aventra development
> Cc: opensc-devel@lists.opensc-project.org
> Subject: Re: [opensc-devel] Braking change in OpenSC 0.12.0 tokenInfo
>
> This patch should fix it:
>
Le mercredi 12 janvier 2011 à 13:07 +0200, Kalev Lember a écrit :
>
> Putting my Fedora packager hat on, please release new tarballs if you
> have important bugfixes to distribute. This ensures everybody is using
> the same code and makes problems much easier to debug.
I also second this approac
On 01/11/2011 06:21 PM, Mr Dash Four wrote:
>
>>> Something like that might actually warrant a new point release of
>>> opensc to make sure Linux distros pick up the fix.
>>
>> Having a point release for every single bug fix would be overkill. So
>> the question is, what's the best approach to quic
On Jan 11, 2011, at 6:21 PM, Mr Dash Four wrote:
>
>>> Something like that might actually warrant a new point release of opensc
>>> to make sure Linux distros pick up the fix.
>>>
>>
>> Having a point release for every single bug fix would be overkill. So
>> the question is, what's the best a
>> Something like that might actually warrant a new point release of opensc
>> to make sure Linux distros pick up the fix.
>>
>
> Having a point release for every single bug fix would be overkill. So
> the question is, what's the best approach to quickly distribute
> important fixes? What wo
On Tue, 2011-01-11 at 16:17 +0200, Kalev Lember wrote:
> On 01/11/2011 03:28 PM, Aventra development wrote:
> > Hi,
> >
> > Thank you very much! This fixed the problem, could it be committed to the
> > trunk?
> > Too bad the release was already done, but when is the next one, so that
> > this fix
Hello,
On Jan 10, 2011, at 11:21 AM, Aventra development wrote:
> I have been testing the new release and sadly found a braking change that
> causes cards that are not initialized with (the current version of) OpenSC to
> result in the message “Unsupported card”. The cause is the token info (5032
On 01/11/2011 03:28 PM, Aventra development wrote:
> Hi,
>
> Thank you very much! This fixed the problem, could it be committed to the
> trunk?
> Too bad the release was already done, but when is the next one, so that this
> fix could be included.
> Getting this to the Linux distributions would b
Hi,
Thank you very much! This fixed the problem, could it be committed to the trunk?
Too bad the release was already done, but when is the next one, so that this
fix could be included.
Getting this to the Linux distributions would be even more important.
Thanks,
Toni
> -Original Message
This patch should fix it:
Index: libopensc/pkcs15.c
===
--- libopensc/pkcs15.c (revision 5078)
+++ libopensc/pkcs15.c (working copy)
@@ -42,8 +42,8 @@
{ "algorithmPKCS#11", SC_ASN1_INTEGER,SC_ASN1_TAG_INTEGER,
Hi,
I have been testing the new release and sadly found a braking change that
causes cards that are not initialized with (the current version of) OpenSC
to result in the message Unsupported card. The cause is the token info
(5032 file). There is some element that OpenSC requires, otherwise it
15 matches
Mail list logo
