On Wed, Mar 25, 2009 at 8:08 PM, Paul Wise <pabs@xxxxxxxxxx> wrote: > On Thu, Mar 26, 2009 at 4:03 AM, Paul Wise <pabs@xxxxxxxxxx> wrote: > >> When we do, just adding a second public key to the CRDA pubkeys dir >> and using the corresponding private key (from outside the package) >> during the build process of wireless-regdb would be just fine. This >> would mean the maintainer of crda would also have to be the >> wireless-regdb maintainer. I assume the wireless-regdb is >> architecture-independent so this would work because the buildds do not >> build such packages. > > Brainwave: no need to add a second public key to CRDA itself, the > wireless-regdb could install the public key corresponding to the > private key it was built with. Can you elaborate on what you mean? Do you mean for wireless-regdb to put the actual pubkey into the users' system somewhere? Otherwise not sure what you mean. >> It is possible for users to add more public keys to the CRDA pubkeys >> dir and build their own wireless-regdb using their own private key. > > The above simplification makes this much easier. Not sure what you mean, but the idea with the pubkeys directory when building CRDA is it lets you add more keys to CRDA so it can use regulatory.bin from multiple trusted parties. A small example is a distribution can decide to use their own pubkey and also leave John's in the pubkeys/ directory. This allow the user to then install and actually use the distribution's release of wireless-regdb while also enabling the users to upgrade to John's latest regulatory.bin themselves whenever they feel like it either manually or using the upstream package. Of course if the distribution keeps up with these then there is no need for the user to be doing any of this. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
