Needed by gdm
coolkey was never stable, and upstream is not responsive nor endorse packaging of non rpm distros. I still remember bug#163395 in which I did not want to take ownership... at the end it went as expected to crypto. I do not understand how gdm requires coolkey which is a driver and not application.
It needs it for smartcard support: smartcard? ( app-crypt/coolkey sys-auth/pam_pkcs11 ) But grepping in sources I only found one reference: $ grep -r coolkey * gui/simple-greeter/extensions/smartcard/gdm-smartcard-manager.c:#define GDM_SMARTCARD_MANAGER_DRIVER LIBDIR"/pkcs11/libcoolkeypk11.so"
(In reply to Pacho Ramos from comment #2) > It needs it for smartcard support: > smartcard? ( > app-crypt/coolkey > sys-auth/pam_pkcs11 ) > > But grepping in sources I only found one reference: > $ grep -r coolkey * > gui/simple-greeter/extensions/smartcard/gdm-smartcard-manager.c:#define > GDM_SMARTCARD_MANAGER_DRIVER LIBDIR"/pkcs11/libcoolkeypk11.so" This should can be overridden with any PKCS#11 provider. It is only a default. /* fallback to compiled in driver path */ These packages should be installed manually if user wish to have smartcard support, pam_pkcs11 is one option, pam_p11 is another, coolkey provider which is endorsed by red hat is one option other options are available as well.
@gnome, any thoughts on this? Will proceed with dropping the RDEPs from gdm if not
+ 07 Nov 2013; Pacho Ramos <pacho@gentoo.org> gdm-3.8.4-r3.ebuild, metadata.xml: + Remove smartcard USE flag and its pulled rdeps (#488784 by Alon Bar-Lev) +
