> 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 ) > 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.
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. 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. One more sophisticated way would be to use dpkg-reconfigure to choose which of openct or pcsc to use. So the library still contains the code for openct but we avoid polling systematically for both pcsc & openct. Phil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
