On Mon, 10 Jan 2011 16:50:37 +0800, Viktor TARASOV
viktor.tara...@opentrust.com wrote:
On 09.01.2011 12:41, Martin Paljak wrote:
Proprietary card dump:
PKCS#15 Card [Gooze ]:
Version: 0
Serial number : 0834493916261110
Manufacturer ID:
On 11.01.2011 09:23, Xiaoshuo Wu wrote:
On Mon, 10 Jan 2011 16:50:37 +0800, Viktor TARASOV
viktor.tara...@opentrust.com wrote:
Do we have any chance to influence the card producer and to change behavior
of their middlewares ?
If so, then it make a sense to wait.
OpenSC compatibility is an
Hi,
What do you think about the possibility that when a card is initialized
using pkcs15-init that it would create the whole structure that is defined
in the profile used.
Currently it only creates the necessary files during initialization, but not
any private or public key DIR files etc,
Hello,
On 11.01.2011 13:32, Aventra development wrote:
What do you think about the possibility that when a card is initialized using
pkcs15-init that it would create the whole structure that is defined in the
profile used.
Currently it only creates the necessary files during initialization,
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
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 be even
Hello:
I am trying to get the Feitian FTCOS/PK-01C smart card to work with OpenSC
version 12 and far my observations have been very intermittent communication.
Sometimes I can return information about the card instantaneously, for example
opensc-tool -n or pkcs15-tool -D but most of the time
Hi all,
Viktor TARASOV wrote:
On 11.01.2011 09:23, Xiaoshuo Wu wrote:
On Mon, 10 Jan 2011 16:50:37 +0800, Viktor TARASOV
viktor.tara...@opentrust.com wrote:
Do we have any chance to influence the card producer and to change behavior
of their middlewares ?
If so, then it make a
Hello,
On Jan 11, 2011, at 4:50 PM, Jan Just Keijser wrote:
I've been reading this discussion and a question comes to mind.
The Feitian cards work with the OpenSC driver
The Feitian cards also work with the proprietary driver from Feitian
itself, in a way that is almost 100% compatible with
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 would fit
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 approach to
Le mardi 11 janvier 2011 à 15:50 +0100, Jan Just Keijser a écrit :
The Feitian cards work with the OpenSC driver
The Feitian cards also work with the proprietary driver from Feitian
itself, in a way that is almost 100% compatible with OpenSC.
How did the Feitian driver writers achieve this
On 1/11/2011 2:39 AM, francois.lebl...@cev-sa.com wrote:
Hello,
I come back after some holidays so sorry if I missing some things or
answers.
First I've seen talk about gina used in XP and it's obsolete since this
change in Vista and 7.
Second for use smart card you can build your own
Le mardi 11 janvier 2011 à 20:53 +0100, Ludovic Rousseau a écrit :
After insertion of the reader?
I don't know. I would say before insertion.
There is always a short delay between the time that you insert the token
or smartcard+reader, and you can run commands like pkcs15-tool. I did
not try to
Hello,
the wiki page of MyEID [1] contains the following paragraph:
Many readers don't support receiving the default amount of data (254).
Problems will only appear when reading larger files from the card (e.g.
certificates). So if you have problems with reading the card with no
apparent reason,
opensc-devel-boun...@lists.opensc-project.org a écrit sur 11/01/2011
18:18:18 :
[image supprimée]
Re: [opensc-devel] Consistence between the OpenSC and proprietary
drivers
Douglas E. Engert
A :
opensc-devel
11/01/2011 18:19
Envoyé par :
16 matches
Mail list logo
