In version 1.1.1 CRDA added the ability to load public keys from a directory instead of just using Linville's compiled in key. By fixing the ebuild to use this new ability we can build our own wireless-regdb instead of shipping a binary. This is both safer and more maintainable as we don't have to trust a binary and we can make wireless-regdb ship the key that goes with the db so crda and wireless-regdb can be safely updated seperately. Reproducible: Always Steps to Reproduce: 1.install crda 2.build wireless-regdb 3.crda can't use the wireless-regdb if the key wasn't built into crda Actual Results: Fire, brimestone, cats and dogs living together. Expected Results: crda and wireless-regdb should be able to be built from source, seperately, in any order, and still function. In the provided ebuild I have chosen to move the runtime pubkey directory from the default to place the keys next to the regdb. This is not strictly nessesary but personally I prefer the binary keys to not sit in /etc. Do what you must.
Created attachment 217882 [details] example ebuild 1.) Yes I know I keyworded it stable. You are welcome to change that. I have crda building with no option to back out this new behavior. I can't imagine wanting to no support runtime public keys. There is no advantage, this is tested stable, and the only negative is requiring openssl which nearly all systems will have anyway. If needed, this new behavior could be put on a useflag but really this should be the default behavior.
Reassign to gurligebis@gentoo.org per metadata.xml of net-wireless/crda.
It should be fixed in 1.1.2-r1 . I have changed it, so it installs the udev rules to the correct directory ( /etc/udev/rules.d ) , and so it loads keys from the recommended folder, which is /etc/wireless-regdb/pubkeys . Please give it a go, and report back.
