Bug#469485: error spamming: "can't open /var/run/openct/status"
> Yeah, that was bad. You did also see my screencast, right? :-) > Yes I first saw the screencast actually >> 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. > I though the duplication of code is ugly but then I saw that the path retrieval is in ct_format_path() and available, so it's ok cf /usr/include/openct/path.h from libopenct1-dev >> So one immediate way would be to document the option reader_drivers >> > I could do that, but many people will miss it. > Without documenting it, for sure they'll miss it ;-) > [...] No, that would be debconf-abuse. I see no need to use debconf here You're the boss ;-) Silent detection within libbeidlibopensc2 is the best way. Maybe sth to forward also to the libopensc2 guys? Phil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#469485: error spamming: "can't open /var/run/openct/status"
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. -- 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]
Bug#469485: error spamming: "can't open /var/run/openct/status"
> 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]
Bug#469485: error spamming: "can't open /var/run/openct/status"
On Wed, Mar 05, 2008 at 03:08:29PM +0100, Philippe Teuwen wrote:
> Package: libbeidlibopensc2
> Version: 2.6.0-3
> Severity: normal
> Tags: patch
>
> Hello,
>
> I just saw that my ~/.xsession-errors logfile was full of
> Error: can't open /var/run/openct/status...
>
> It happens whenever icedove/iceweasel are open (so when the
> libbeidpkcs11.so is loaded)
>
> I found a similar bugreport on Ubuntu:
> https://bugs.launchpad.net/ubuntu/+source/belpic/+bug/70442
>
> The proposed fix works:
>
> >>
> OpenSC has support for three driver types : PCSC, OpenCT and CT-API.
> Belpic only needs PC/SC, and will produce errors/warnings if you leave
> support for OpenCT enabled.
This is wrong.
The Belgian electronic ID card needs a smartcard driver; either PCSC,
OpenCT, or CT-API will indeed work. The government removed the OpenCT
and CT-API drivers since they don't sell any cardreaders that use those;
however, that doesn't mean the card won't work with other cardreaders.
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.
> Fix:
> Edit /etc/beidbase.conf, and insert a statement that limits the use of
> drivers to pcsc. Right before the reader_driver config feels like an OK
> place to do this :
>
> ## specify driver family pcsc.
> # Others (openct, ..) are not needed for Belpic and
> # may produce errors/warnings
>
> reader_drivers = pcsc ;
>
> reader_driver pcsc {
>
> <<
>
> I sometime saw those errors when playing on the command line and
> I even think I've read somewhere a statement that said
> "normal that doesn't hurt" but here I'm talking about 6-8 lines
> of log every second and I just got a nice crash because of this big
> error file.
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.
--
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]
Bug#469485: error spamming: "can't open /var/run/openct/status"
Package: libbeidlibopensc2
Version: 2.6.0-3
Severity: normal
Tags: patch
Hello,
I just saw that my ~/.xsession-errors logfile was full of
Error: can't open /var/run/openct/status...
It happens whenever icedove/iceweasel are open (so when the
libbeidpkcs11.so is loaded)
I found a similar bugreport on Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/belpic/+bug/70442
The proposed fix works:
>>
OpenSC has support for three driver types : PCSC, OpenCT and CT-API.
Belpic only needs PC/SC, and will produce errors/warnings if you leave
support for OpenCT enabled.
Fix:
Edit /etc/beidbase.conf, and insert a statement that limits the use of
drivers to pcsc. Right before the reader_driver config feels like an OK
place to do this :
## specify driver family pcsc.
# Others (openct, ..) are not needed for Belpic and
# may produce errors/warnings
reader_drivers = pcsc ;
reader_driver pcsc {
<<
I sometime saw those errors when playing on the command line and
I even think I've read somewhere a statement that said
"normal that doesn't hurt" but here I'm talking about 6-8 lines
of log every second and I just got a nice crash because of this big
error file.
Phil
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.22-3-vserver-686
Debian Release: lenny/sid
990 testing ftp.kulnet.kuleuven.ac.be
500 unstableftp.kulnet.kuleuven.ac.be
500 unstabledebian.jones.dk
--- Package information. ---
Depends (Version) | Installed
=-+-
libc6 (>= 2.7-1) | 2.7-6
libgcc1 (>= 1:4.1.1-21) | 1:4.3-20080202-1
libopenct1 (>> 0.6.9) | 0.6.14-2
libqt3-mt(>= 3:3.3.7) | 3:3.3.8b-4
libssl0.9.8 (>= 0.9.8f-1) | 0.9.8g-4
libstdc++6 (>= 4.2.1-4) | 4.3-20080202-1
libwxgtk2.6-0 (>= 2.6.3.2.2) | 2.6.3.2.2-2
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
