Bug 811691 - ykpers: please do not call non-existent, and always have been udev internal, tools
Summary: ykpers: please do not call non-existent, and always have been udev internal, ...
Alias: None
Product: Fedora
Classification: Fedora
Component: ykpers
Version: 17
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Maxim Burgerhout
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2012-04-11 18:25 UTC by Kay Sievers
Modified: 2012-10-15 10:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-10-15 10:16:59 UTC
Type: Bug

Attachments (Terms of Use)

Description Kay Sievers 2012-04-11 18:25:52 UTC
The instructions in:
can not work since quite a while; they will do nothing but throw errors.

They have been wrong since day one, because the called tools are internal
to udev an _not_ supposed to be called _ever_ by any other tool.

Please remove the rule entirely, or alternatively integrate properly with:


Comment 1 Maxim Burgerhout 2012-07-24 19:42:25 UTC
For posterity:

Kay has added a new ID_SECURITY_TOKEN rule in systemd. I'll submit a patch upstream to set Yubikey devices to that ID and thus get this fixed in a new release of ykpers.

Comment 2 Fedora Update System 2012-10-01 14:58:12 UTC
ykpers-1.8.0-1.fc18 has been submitted as an update for Fedora 18.

Comment 3 Fedora Update System 2012-10-01 20:12:22 UTC
Package ykpers-1.8.0-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ykpers-1.8.0-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 4 Maxim Burgerhout 2012-10-15 10:16:59 UTC
New udev file merged upstream[1] and ykpers-1.8.0-1.fc18 pushed to stable.

[1] https://github.com/Yubico/yubikey-personalization/commit/b76fb49ad9eb7dd9da6f4568975e8ee99f3ba35f

Note You need to log in before you can comment on or make changes to this bug.