[Pcsclite-muscle] Deny card access for one application
Nik T
nicholas
Tue Jul 21 10:49:06 PDT 2015
https://pcsclite.alioth.debian.org/api/group__API.html#ga4e515829752e0a8dbc4d630696a8d6a5
dwShareMode = SCARD_SHARE_EXCLUSIVE
From: Pcsclite-muscle [mailto:pcsclite-muscle-bounces+nicholas=nikom.net at lists.alioth.debian.org] On Behalf Of Nik T
Sent: Tuesday, July 21, 2015 1:47 PM
To: 'Talks about MUSCLE'
Subject: Re: [Pcsclite-muscle] Deny card access for one application
Can you have each application establish an exclusive connection to the reader they need to use?
From: Pcsclite-muscle [mailto:pcsclite-muscle-bounces+nicholas=nikom.net at lists.alioth.debian.org] On Behalf Of Florent
Sent: Tuesday, July 21, 2015 12:57 PM
To: pcsclite-muscle at lists.alioth.debian.org <mailto:pcsclite-muscle at lists.alioth.debian.org>
Subject: [Pcsclite-muscle] Deny card access for one application
Hello list,
On my Ubuntu system I use two different readers containing each one card which are also different.
Both readers must be usable by my user.
One of my application (FreeRDP, not to mention it) is capable of accessing those smartcard through the libpcsclite.so library. However, this means it can access both readers. And I don't want that.
Is there a way to deny the access to one specific reader?
Through udev rules? Through the Info.plist XML file?
(Simply removing the reader from the Info.plist "works" but is not a option since I need to access the "denied" reader in another context while the application is running)
Thanks in advance!
Cheers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pcsclite-muscle/attachments/20150721/e98b3cfa/attachment.html>
More information about the pcsclite-muscle
mailing list