On Wed, Jun 1, 2011 at 11:08 AM, Ludovic Rousseau <[email protected]> wrote: > 2011/6/1 Brent Oster <[email protected]>: > Since you do not list what you expect from a pinpad reader or simple > reader I can't give you recommendation.
Well, ideally I would be able prompt the user to punch in buttons on the pinpad, and then read what they select. A fairly low level interface would be fine (ie. "He hit 1, process it. He hit 2, process it. He hit the ok button, process it"). Outputting custom messages to a small display would be very nice. As for the card reader, I'm kind of fuzzy on what I would need. I'm sure I'd need some sort of unique ID on each card so I could tell which card is which (and thus verify their PIN), but beyond that I'm not really sure I'd need anything else. I don't want to store personal information on the card... at least, unencrypted. I was planning on doing authentication linux-side. >> I was also wondering if someone could point me at a good "beginner's >> guide" to getting this sort of thing working. I assume I'll have to >> compile some sort of OpenSC or CCID package, and then... read the >> guide? :D > > Something like that, yes. > You should start using a "normal" computer using a "normal" > distribution. I would recommend Debian (or Ubuntu) since many packages > are already available and easy to install. > You will then use your hardware in an "easy" environment. Definitely. I usually start with Ubuntu. In the past I tried to get an unrelated USB device working that claimed it had linux support, but it turns out that they only provide precompiled libraries... no source, and only for x86. So I was SOL when I tried to port it to the ARM after getting it working on Ubuntu. So this time around I'm wanting to make sure I get something that has a good chance of working on an ARM machine. > I don't know what you want to do so I can't tell what you need. Well, the basics of what I'd like to do are: 1) User inserts smartcard, smartcard tells the system who the user claims to be 2) User authenticates via pinpad 3) User then interacts with a machine also attached to the system. It uses the pinpad to display errors and other messages, possibly prompts for options that allow for some control over the machine. 4) User selects an option to log off (or maybe just removes the card?) Something like that. Is that enough detail? So to kick this off, I'll need to pick some hardware to order in. Then I'll need to figure out how to interface with it. - Brent _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
