Set default to hide as we discussed.
On 1/19/09, Alon Bar-Lev wrote:
> On 1/19/09, Martin Paljak wrote:
>
> > On Mon, Jan 19, 2009 at 3:00 PM, Alon Bar-Lev wrote:
> > >> Tried it as well. hide_empty_tokens only matters for PKCS#15-init
> > >> compatible cards and does not apply to read-on
Am Montag 19 Januar 2009 13:38:06 schrieb Martin Paljak:
> BTW, am I the only one having problems with opensc-commit list? I have
> received only 2 mails from it in the past week.
no idea, I did a test commit, and it shows up in the web archive.
also mails to all subscribers are in the postfix mai
On 1/19/09, Martin Paljak wrote:
> On Mon, Jan 19, 2009 at 3:00 PM, Alon Bar-Lev wrote:
> >> Tried it as well. hide_empty_tokens only matters for PKCS#15-init
> >> compatible cards and does not apply to read-only PKCS#15 emulated
> >> cards.
> >
> > Are you sure that emulated PKCS#15 card
On Mon, Jan 19, 2009 at 3:00 PM, Alon Bar-Lev wrote:
>> Tried it as well. hide_empty_tokens only matters for PKCS#15-init
>> compatible cards and does not apply to read-only PKCS#15 emulated
>> cards.
>
> Are you sure that emulated PKCS#15 cards cannot have multiple auth-ids?
They can have mult
On 1/19/09, Martin Paljak wrote:
> > At least by playing with some of my installations, the
> > hide_empty_tokens=yes is quite useful for most users.
> > So I am for modify the code default.
>
> Tried it as well. hide_empty_tokens only matters for PKCS#15-init
> compatible cards and does not
On Fri, Jan 16, 2009 at 11:48 PM, Alon Bar-Lev wrote:
> On 1/16/09, Alon Bar-Lev wrote:
>> > There are still some options in the example configuration file (one
>> > distributed with Ubuntu/Debian by default) that differ from code level
>> > settings:
>> > hide_empty_tokens (yes in confi