Ramkumar,
Nikola's message title mentions 'talking directly to port' - that she cannot
do without driver code that wraps the apdu in a command to the reader. So
she must at least know the command set to the GPC410. Quite a bit of the
confusion in the minds of some developers is caused by them thinking that
they send just an apdu (in 7816 format) from their application and it goes
straight to the card. For example, the problem of whether the card is
handled with T=0 or T=1: in T=0 the PC app may send an apdu which both sends
data to the card and expects data back, and somewhere between the PC app and
the card that apdu has to be turned into two tpdus: one to send the command
code with data, another to get the result data back. At the app level API I
expect to see one command to the driver to set either T=0 or T=1, and I also
expect the driver in the PC or the terminal itself to look at the ATR and
maybe do that job for me if the card only offers one protocol - and I expect
to send the same apdu format across the API to the PC driver software
whatever protocol is actually used to talk to the card - but when trying to
handle the terminal directly via the COM port, you need to know and cope
with all the detail at this level.
Regards,
Peter T
----- Original Message -----
From: "Ramkumar.R" <[EMAIL PROTECTED]>
To: "Peter Tomlinson" <[EMAIL PROTECTED]>
Cc: "Opencard ORG" <[EMAIL PROTECTED]>
Sent: Wednesday, April 11, 2001 5:47 PM
Subject: Re: [Re: [OCF] how about talking directlly to port?]
"Peter Tomlinson" <[EMAIL PROTECTED]> wrote:
No, it doesn't work like that. There is no standardisation of the comms
protocol between the PC COM port and readers. As well as commands which get
sent on to the card and a method for getting the responses from the card,
there are commands to the reader and responses from the reader. That is why
you have to have a reader-specific driver level of software in the PC, as
well as having above that level (although too often, it seems, integrated
with that level) a layer of software specific to the card (and, if the card
hosts an app with proprietary commands, driver software specific to that app
as well unless you use a pass-through function in the existing card/reader
drivers).
Peter T
----- Original Message -----
From: "Nikola Mitrovic" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 11, 2001 8:39 AM
Subject: [OCF] how about talking directlly to port?
> I know it sounds weird, but how about accessing to a smartcard via COM
port?
>
> do I really need any wrappers? What are the GPC410 parameteres for
> connection 9600bps 8n1?
>
> that sould be like "open port, put apdu, expect reposnse, etc." right?
>
> I'm trying to write some ultra-lite applicaton, so I'm trying to save as
> much as possible to processing and memory, and distribution, etc...
>
> any suggestions?
>
> Nikola Mitrovic
> [EMAIL PROTECTED]
>
>
>
> ---
> > Visit the OpenCard web site at http://www.opencard.org/ for more
> > information on OpenCard---binaries, source code, documents.
> > This list is being archived at http://www.opencard.org/archive/opencard/
>
> ! To unsubscribe from the [EMAIL PROTECTED] mailing list send an email
> ! to
> ! [EMAIL PROTECTED]
> ! containing the word
> ! unsubscribe
> ! in the body.
>
---
> Visit the OpenCard web site at http://www.opencard.org/ for more
> information on OpenCard---binaries, source code, documents.
> This list is being archived at http://www.opencard.org/archive/opencard/
! To unsubscribe from the [EMAIL PROTECTED] mailing list send an email
! to
! [EMAIL PROTECTED]
! containing the word
! unsubscribe
! in the body.
Hi,
It is very much possible. Without any wrappers
you can talk with smartcard through port.
Also it is same as
Open Port-> Send Command -> Expect response.
apdu will come as a part of command.
Ramkumar
____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1
---
> Visit the OpenCard web site at http://www.opencard.org/ for more
> information on OpenCard---binaries, source code, documents.
> This list is being archived at http://www.opencard.org/archive/opencard/
! To unsubscribe from the [EMAIL PROTECTED] mailing list send an email
! to
! [EMAIL PROTECTED]
! containing the word
! unsubscribe
! in the body.
---
> Visit the OpenCard web site at http://www.opencard.org/ for more
> information on OpenCard---binaries, source code, documents.
> This list is being archived at http://www.opencard.org/archive/opencard/
! To unsubscribe from the [EMAIL PROTECTED] mailing list send an email
! to
! [EMAIL PROTECTED]
! containing the word
! unsubscribe
! in the body.
