Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm working on an app that will authenticate user with a smartcard when the user inserts it in the card reader (this is on Red Hat 5.5). How do I detect a card has been inserted? Is there a daemon service I need to listen to and associated api to get notified etc? thanks in advance.
However I forgot to mention that we'd need to get notified at red hat login screen level. would udev allow that at login level where user simply inserts to the card for authentication instead of entering user name password?
there is PAM level config you can do to authenticate a user without having to write your own app however we need to do some extra stuff due to which we need event notification (or detection of card insertion).
I honestly don't know about the login level. udev runs at boot, and can hold up device detection if one of your rules takes a long time. However, the login is well after device detection anyway, so I would have thought it would be a matter of interfacing your custom udev action rule with the PAM config somehow, short circuiting the login process. How you do that, again, I don't know - it's not something I've attempted.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.