Justin Karneges wrote:
Is the problem that these cards don't support 7816?
7816 is a big family of standards, and the last parts of
it came quite late. at that point every vendor already had
a card implementing his own commands etc.
and because certifications are very, very expensive, why chan
Justin Karneges wrote:
On Thursday 15 February 2007 7:14 am, Douglas E. Engert wrote:
Yes propriety vendor solutions are a major problem. Have a look at the
PIV card comments at:
http://www.opensc-project.org/opensc/wiki/UnitedStatesPIV
The intent is to standardize on multiple vendors for c
On Thursday 15 February 2007 11:00 am, Andreas Jellinghaus wrote:
> Justin Karneges wrote:
> > There would appear to be a standard for #1. I don't remember what it is
> > called, but it involves the ATR and then T=0 or 1 and friends. However,
> > my experience with hacking on the Eutron driver sh
On Thursday 15 February 2007 7:14 am, Douglas E. Engert wrote:
> Yes propriety vendor solutions are a major problem. Have a look at the
> PIV card comments at:
> http://www.opensc-project.org/opensc/wiki/UnitedStatesPIV
>
> The intent is to standardize on multiple vendors for cards,
> multiple ve
On Thursday 15 February 2007 3:26 am, Henryk Plötz wrote:
> There you also get the definition of APDUs (Application Protocol Data
> Unit) for commands and responses. The second part of your #1, 7816-4
> then defines common ("interindustry") commands for most of the basic
> operations: selecting fil
On Thursday 15 February 2007 12:02 am, Ludovic Rousseau wrote:
> On 14/02/07, Justin Karneges <[EMAIL PROTECTED]> wrote:
> > There would appear to be a standard for #1. I don't remember what it is
> > called, but it involves the ATR and then T=0 or 1 and friends.
>
> I think you are talking about
Andreas Jellinghaus wrote:
> I'd be willing to help as time permits, and I'm sure many other people
> here can answer questions about writing new card drivers too. So why
> don't you give it a try? take a look at a few drivers with full support
> (like cardos and cryptoflex and starcos), the basic
Justin Karneges wrote:
There would appear to be a standard for #1. I don't remember what it is
called, but it involves the ATR and then T=0 or 1 and friends. However, my
experience with hacking on the Eutron driver showed that that either there
are still vendor-specific issues (bugs? workarou
Ian Young wrote:
There was a brief discussion a couple of months back about the ACS ACOS5
cards. Did anyone make any progress on this?
Now I have a few cards, a printout of the card manual, and I read it
once. I never wrote a complete card driver so far, but I saw nothing
that looked like tr
Justin Karneges wrote:
Hi folks,
I'm just trying to wrap my head around all of the various protocols involved
in smart card use, and today I was reading the OpenSC website and it got my
mind going again. I'm glad that the website finally discusses these
important details.
Now, PKCS#11, a
There was a brief discussion a couple of months back about the ACS ACOS5
cards. Did anyone make any progress on this?
The certificate management and PKCS#11 support that comes with these as
part of the SDK is Windows-only. That's fine for my current project,
but in the longer term it would be ni
Moin,
Am Sat, 20 Jan 2007 16:35:59 +0100 schrieb Sebastian Thias:
> is there any update on the availability of the Siemens-HiPath-Profile?
I was too busy to look at it lately. However, file access should work
in SVN (e.g. pkcs15-tool -D, pkcs15-tool -r, etc.) as should decrypting
(pkcs15-crypt -
Moin,
Am Wed, 14 Feb 2007 14:34:55 -0800 schrieb Justin Karneges:
> It seems that there are 4 communication areas:
> 1) I/O to the smart card
> 2) I/O to the reader
> 3) filesystem layout/control for reading
> 4) filesystem layout/control for all else
> There would appear to be a standar
On 14/02/07, Justin Karneges <[EMAIL PROTECTED]> wrote:
Hi folks,
Hello,
It seems that there are 4 communication areas:
1) I/O to the smart card
2) I/O to the reader
3) filesystem layout/control for reading
4) filesystem layout/control for all else
There would appear to be a standard
14 matches
Mail list logo
