--On Monday, February 02, 2009 07:38:23 PM +0100 Andreas Jellinghaus
wrote:
> but keeping openct around with or without ccid
> driver, or having some other drivers around
> to implement non-ccid drivers all ends up with
> the same result: lots of common functionality in
> several places.
The so
--On Monday, February 02, 2009 07:52:30 PM +0200 Alon Bar-Lev
wrote:
> On Mon, Feb 2, 2009 at 7:41 PM, Jeffrey Hutzelman wrote:
>> --On Monday, February 02, 2009 04:28:22 PM +0200 Alon Bar-Lev
>> wrote:
>>
>>> The client library monitors /var/run/libscreader
--On Monday, February 02, 2009 04:28:22 PM +0200 Alon Bar-Lev
wrote:
> The client library monitors /var/run/libscreader for changes
That sounds really nonportable.
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-p
--On Thursday, January 29, 2009 03:36:42 AM +0100 Peter Stuge
wrote:
> Jeffrey Hutzelman wrote:
>> the USB device is entirely in the card.
>
> They are nice. I was building my own expresscard egate adapter for a
> while there.
That sounds like a useful item, and hopefully n
--On Thursday, January 29, 2009 02:58:53 AM +0100 Peter Stuge
wrote:
> Jeffrey Hutzelman wrote:
>> Something like the Reflex "reader" which is really just an egate
>> adapter.
>
> I don't think there is a USB device until the egate is inserted.
That's c
--On Wednesday, January 28, 2009 03:41:49 PM +0100 Ludovic Rousseau
wrote:
(mostly I'm agreeing with Ludovic here and adding a few comments of my own)
> 2009/1/28 Stanislav Brabec :
>> We need a "category" string that covers both and use it for both,
>> otherwise we will have problems in defin
--On Wednesday, January 28, 2009 12:51:05 PM +0200 Alon Bar-Lev
wrote:
>> It assumes the pcsclite library is in a particular location, instead of
>> searching for it. This means it will fail to find libpcsclite on a
>> system where it is installed in /usr/local, for example. Further, the
>>
--On Thursday, July 31, 2008 05:40:40 PM +0200 Andreas Jellinghaus
wrote:
> Changes in OpenSC 0.11.5 released 2008-07-31
> * PC/SC library is dynamic linked no longer compile time dependency.
WHY
What was wrong with using pkg-config to find the library, and then linking
against it? This
--On Thursday, January 08, 2009 11:40:54 AM +0100 Andreas Jellinghaus
wrote:
> Late reply to jeffreys mails (I read them in our web archive):
> 1.) yes, we reduce usability with these changes.
> 2.) I think those are better defaults, you think otherwise.
> what does everyone else think about the
--On Tuesday, January 27, 2009 11:01:15 PM +0100 Ludovic Rousseau
wrote:
> 2009/1/27 Stanislav Brabec :
>> It is possible to detect form factor (credit card size, SIM size)?
>
> No. This information is not stored in any USB descriptor I know.
You certainly can't tell in all cases. For example,
--On Friday, January 23, 2009 12:38:54 PM +0100 Andreas Jellinghaus
wrote:
> hmm. I always wondered if loading binary only pkcs#11 libraries
> via pam_p11/pkcs11 into login and gdm/kdm would be ok.
Loading? Yes, always -- despite the FSF's best efforts to force people to
use only open-source
--On Thursday, January 22, 2009 06:50:34 PM +0100 Andreas Jellinghaus
wrote:
> more complex operations such as "upload new firmware
> to card reader" will most propably never work with pcscd (guessing only,
> I'm no expert here).
I think that's going to depend on the reader driver. There cert
--On Thursday, January 22, 2009 08:49:33 PM +0200 Alon Bar-Lev
wrote:
> Poll the reader to detect card insert.
Yeah, that's still a problem, and certainly one I'd like to see fixed.
It's also per-driver, and I'm not sure it even _can_ be fixed for all kinds
of devices.
>> > 5. The udev sup
--On Thursday, January 22, 2009 08:14:20 PM +0200 Alon Bar-Lev
wrote:
> Well, Ludovic knows my arguments...
> 4. Due to the threading limitation of libusb or kenrel pcscd polls
> readers every 2 seconds which waste CPU and power resources.
Only if you have reader drivers which require this. I
--On Thursday, January 22, 2009 06:24:58 PM +0100 Andreas Jellinghaus
wrote:
> my point of view is:
> there is not a single external driver that I'm aware off.
> thus we could remove the whole code for allowing external
> loadable drivers, as there are none, and that would simplify
> the code.
--On Thursday, January 22, 2009 03:54:07 PM +0100 Stanislav Brabec
wrote:
> Ludovic Rousseau wrote:
>> 2009/1/22 Stanislav Brabec :
>
>> > HAL recognizes Smart Card readers as unknown USB devices
>>
>> Why is that a problem? Why do you need HAL to know about smart card
>> readers?
>
> HAL detect
--On Thursday, January 22, 2009 01:18:44 PM +0100 Stanislav Brabec
wrote:
>> I cannot
>> imagine any vendor shipping policy that would allow ordinary users
>> direct access to smartcard devices.
>
> openSUSE has to do it, at least for selected readers, otherwise users of
> these applications co
--On Thursday, January 22, 2009 02:57:10 PM +0200 Alon Bar-Lev
wrote:
> On 1/22/09, Stanislav Brabec wrote:
>> Alon Bar-Lev wrote:
>> > On 1/21/09, Stanislav Brabec wrote:
>> Yes, udev supports it as well. But most vendors prefer HAL for this
>> purpose nowadays.
>
> vendors? You mean Novel
--On Wednesday, January 21, 2009 07:27:03 PM +0100 Stanislav Brabec
wrote:
> Alon Bar-Lev wrote:
>> I don't understand the motivation.
>> Why do you care if readers are accessible by all users?
>
> 1) There are applications, that need direct access to the reader, not
> using pcsc-lite (example:
--On Thursday, January 08, 2009 11:40:54 AM +0100 Andreas Jellinghaus
wrote:
> Happy new year everyone!
>
> I was offline for a week or so, and due to a mail problem
> all my email was lost. So what is our current status?
>
> Did anyone have time to test the opensc pre-release,
> does it work fo
--On Monday, January 19, 2009 06:40:39 AM +0100 Peter Stuge
wrote:
> http://www.cryptoken.com/en/products/hardware/ct2000.php
>
> Anyone know about this product? Claims Linux support.
I can't say for certain, but it claims to be a JavaCard, which suggests one
could load the muscle applet and g
--On Wednesday, December 31, 2008 09:07:52 AM +0200 Alon Bar-Lev
wrote:
>> Are they actually supposed
>> to be private, per PKCS#15? None of the profiles I looked at do this;
>> are you updating them all, or just cryptoflex?
>
> The PKCS#15 implementation already supported private data object
--On Sunday, December 28, 2008 06:47:46 PM +0100 Andreas Jellinghaus
wrote:
> here is a preview for opensc 0.11.7:
> http://www.opensc-project.org/files/opensc/testing/opensc-0.11.7-pre1.tar
> .gz
>
> this new version has a number of changes for security:
> * lock_login is now on as default. if
23 matches
Mail list logo
