2009/12/16 Andreas Jellinghaus :
> Hi,
Hello,
> should we modify all tools so they print the version
> info with "--help"? or implement a "--version"?
Adding a "--version" could not hurt.
I think the more important is to know:
- with which version of OpenSC a card was "personalized".
- what is
Hi,
should we modify all tools so they print the version
info with "--help"? or implement a "--version"?
I know opensc-tool has something like that already,
but it feels strange that only one of the command
line tools can print the version. what do you think?
Regards, Andreas
___
any idea how to implement that?
in theory we need only to trigger reading of
the pin and prkey DF files, and make sure they
are written too. but I have no clue about those
things (like what pin handling is necessary etc.).
any idea how to do that?
Regards, Andreas
Hi,
I changed the opensc server configuration:
you can now change your wiki password once you are
logged in.
In theory spammers could now again register new accounts,
but as I redirected all /opensc/register (and co) links,
that should not be possible.
Lets see if the new configuration works bet
Am Dienstag 15 Dezember 2009 11:37:00 schrieb Ludovic Rousseau:
> 2009/12/14 :
> > +So far no place has been found where we could mark new tokens
> > +differently, to see if a token has been initialized with an old
> > +copy of opensc or a recent one. One place that could be used
> > +would be Tok
2009/12/14 :
> +So far no place has been found where we could mark new tokens
> +differently, to see if a token has been initialized with an old
> +copy of opensc or a recent one. One place that could be used
> +would be TokenInfo manufacturerID which is currently set by
> +pkcs15init/profile.c as
