Hello,
today I encountered a new bug that was introduced with the fix of #266.
A working patch was committed in r4983.
That bug always occurs if there is an EF (i.e. EF.PrKD, EF.PuKD, EF.SKD)
that contains either broken ASN.1 or uses an encoding that OpenSC isn't
able to decode. The committed mes
Andre Zepezauer wrote:
> Hello,
>
> today I encountered a new bug that was introduced with the fix of
> #266. A working patch was committed in r4983.
Please be careful about wording in the subject. It is very much
unclear what the version number means. :\
> That bug always occurs if there is an
Hello Peter,
On Thu, 2010-12-23 at 03:10 +0100, Peter Stuge wrote:
> Andre Zepezauer wrote:
> > Hello,
> >
> > today I encountered a new bug that was introduced with the fix of
> > #266. A working patch was committed in r4983.
>
> Please be careful about wording in the subject. It is very much
>
Hello,
The following e-mail did not make it to the list yesterday.
I prematurely changed the default sender address in the e-mail client
but electricity was lost shortly after sendig the mail so I did not
see the bounce message until today morning. As some of my e-mails have
declared for some tim
Hello,
On Dec 23, 2010, at 5:40 AM, Andre Zepezauer wrote:
> On Thu, 2010-12-23 at 03:10 +0100, Peter Stuge wrote:
>>> That bug always occurs if there is an EF (i.e. EF.PrKD, EF.PuKD, EF.SKD)
>>> that contains either broken ASN.1 or uses an encoding that OpenSC isn't
>>> able to decode. The committ
