linux-kernel - Re: ISO/IEC 7811 driver for Magnetic Cards.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMNxYszE1EVRMvAtteckbY5=kga3c7-B9Nyuz+=s4ur7KqW+9A@mail.gmail.com>
Date:	Tue, 5 Feb 2013 12:05:40 +0530
From:	Priyaranjan Das <priyaranjan456789@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: ISO/IEC 7811 driver for Magnetic Cards.

Hi Peter,

On Tue, Feb 5, 2013 at 11:26 AM, H. Peter Anvin <hpa@...or.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/