On Tue, Mar 11, 2008 at 11:00:08AM +0100, Philippe Teuwen wrote: > > Since my cardreader does, in fact, use the OpenCT driver rather than the > > PC/SC one, I re-added this driver to the beid packages. Disabling the > > driver afterwards would be rather silly. > > > You're right, meanwhile I saw the video of your speech at Fosdem ;-) > (Mm ok the video itself didn't convince me you could use successfully > openct without demo effect :-p )
Yeah, that was bad. You did also see my screencast, right? :-) > > I'll see if I can make libbeidlibopensc2 stop those warnings, then. > > That's a better option than to remove a driver for no good reason > Apparently the message is actually from libopenct (src/ct/status.c) > openct_reader_init() -> ct_reader_info() -> ct_status() -> ct_map_status() > and is not specific to the Belgian middleware but rather from using > opensc and declaring to use openct while there is actually no openct > daemon running. Yes, I know. The point was that I want to verify whether it can be suppressed by a change in beid. > If something could be done in libbeidlibopensc2, it's to make a silent > test about /var/run/openct/status (or cf ct_format_path() ) before > calling the openct lib (/src/newpkcs11/src/libopensc/reader-openct.c) > but it's quite ugly. I don't think so. Verifying whether something is there before using it seems like proper coding to me. > The other refs of this problem between opensc and openct I found give > the same advise as I said: > - http://osdir.com/ml/encryption.opensc.user/2006-06/msg00075.html > - http://esteidutil.sourceforge.net/install.txt > > So one immediate way would be to document the option reader_drivers to > only enable the reader the people want to use in /etc/beidbase.conf and > warn people about those flooding messages. I could do that, but many people will miss it. > One more sophisticated way would be to use dpkg-reconfigure to choose > which of openct or pcsc to use. No, that would be debconf-abuse. I see no need to use debconf here. -- <Lo-lan-do> Home is where you have to wash the dishes. -- #debian-devel, Freenode, 2004-09-22 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
