mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Priyaranjan Das <priyaranjan456789@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ISO/IEC 7811 driver for Magnetic Cards.
Date: Mon, 04 Feb 2013 22:37:14 -0800	[thread overview]
Message-ID: <56bede34-86a7-4565-a8c9-54413d410629@email.android.com> (raw)
In-Reply-To: <CAMNxYszE1EVRMvAtteckbY5=kga3c7-B9Nyuz+=s4ur7KqW+9A@mail.gmail.com>

There is no reason for that to be in the kernel.

Priyaranjan Das <priyaranjan456789@gmail.com> wrote:

>Hi Peter,
>
>On Tue, Feb 5, 2013 at 11:26 AM, H. Peter Anvin <hpa@zytor.com> wrote:
>> On 02/04/2013 09:08 PM, Priyaranjan Das wrote:
>>>
>>> Hi All,
>>>
>>> I am working on a Magnetic Card driver which would support ISO/IEC
>>> 7811 standard for track data. Can anyone tell me if such an
>>> implementation is available in existing kernel or not? I am
>basically
>>> looking for  code that implements the ISO/IEC 7811 standard or any
>>> similar standards.
>>>
>>
>> You have to write a driver for whatever reader/writer you are using. 
>A lot
>> of them simply show up as a USB HID (i.e. a keyboard) and thus don't
>need
>> any driver at all.
>>
>
>Thanks for your reply!
>
>However my question was more of related to ISO/IEC 7811 standard, As
>this is the format of the data read from the magnetic card. I wish to
>know whether any such module is there in the Linux kernel currently
>which works to decode the data as per as these ISO standards.
>
>For e.g,
>
>The first track read from a magnetic card could be as per below
>standard format :
>
>Track 1, Format :
>Start sentinel — one character (generally '%')
>Format code="B" — one character (alpha only)
>Primary account number (PAN) — up to 19 characters. Usually, but not
>always, matches the credit card number printed on the front of the
>card.
>Field Separator — one character (generally '^')
>Name — two to 26 characters
>Field Separator — one character (generally '^')
>Expiration date — four characters in the form YYMM.
>Service code — three characters
>Discretionary data — may include Pin Verification Key Indicator (PVKI,
>1 character), PIN Verification Value (PVV, 4 characters), Card
>Verification Value or Card Verification Code (CVV or CVC, 3
>characters)
>End sentinel — one character (generally '?')
>Longitudinal redundancy check (LRC) — it is one character and a
>validity character calculated from other data on the track.

-- 
Sent from my mobile phone. Please excuse brevity and lack of formatting.

      reply	other threads:[~2013-02-05  6:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-05  5:08 Priyaranjan Das
2013-02-05  5:56 ` H. Peter Anvin
2013-02-05  6:35   ` Priyaranjan Das
2013-02-05  6:37     ` H. Peter Anvin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56bede34-86a7-4565-a8c9-54413d410629@email.android.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=priyaranjan456789@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®