Bugzilla – Bug 336330
Marx Dongles are not accessible
Last modified: 2009-01-30 17:51:41 UTC
Marx dongles are not accessible for normal users. When adding the following file it works for desktop users, as desired: martin:~ # cat /usr/share/hal/fdi/information/20thirdparty/20-usb-raw-dongle.fdi <?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- --> <deviceinfo version="0.2"> <device> <match key="@info.parent:usb_device.vendor_id" int="0x0d7a"> <merge key="resmgr.class" type="string">desktop</merge> </match> </device> </deviceinfo>
What's a Marx Dongle any why do you need to access it?
We need to access it, because we use that dongle for a copy protection of our software. The usb-dongle is a smartcard-replacement, which can for instance en/decrypt aes/rsa in its hardware. If you need a photo, have a look at this website. ;-) http://www.cryptoken.com/de/produkte/hardware/ctm2048.php
Sounds like a rather specific use case for a multi purpose piece of hardware. I'm not sure whether it makes sense to ship the distro with a configuration that grants everyone access by default. So your solution to create a site local, custom fdi file is probably the way to go -> WONTFIX. Out of curiosity, could you please attach the lshal output for that device anyways?
No, that's the common way to use and access such a device. Marx suggest to make the usbdevfs read and writable for everybody. But imho that's not the proper way. Util now I included that file in one of our rpms. But bringing this file upstream possibly makes life easier for other people.
Created attachment 182428 [details] output of lshal
The device has a vendor specific class. hal-resmgr is not the right place to put lists with vendor/device ids. IMHO there should be a hal capability similar to 'portable_audio_player' or 'pda'. Lists for such devices are both provides by addon packages as well as hal itself. So hal could indeed be the correct place to classify this device. hal-resmgr can then match the info.capability for this device. Reassigning to Danny.
We define currently a HAL namespace and ACL/PolicyKit policy for iso7816 devices. I guess this device fits in here. I mark this bug as duplicate of the actual bug. *** This bug has been marked as a duplicate of bug 438131 ***