On Fri, Mar 05, 2010 at 10:27:03AM +1000, Kel Modderman wrote: > On Friday 05 March 2010 01:31:28 John W. Linville wrote: > > On Fri, Mar 05, 2010 at 12:08:50AM +1000, Kel Modderman wrote: > > > When USE_OPENSSL=1 do not embed crypto data into binary, use the PUBKEY_DIR > > > variable just as it is when USE_GCRYPT=1 and just load certs from PUBKEY_DIR > > > for signature verification at runtime. Remove ssl support from > > > utils/key2pub.py. > > > > > > This allows wireless-regdb to be built from source and upgraded independently > > > of crda and is _crucial_ for distributions who want to build their own > > > regulatory.bin. > > > > I don't understand -- isn't this possible already? > > No. Perhaps you could use a few more words? It seems to me that what limits you is the policies of some distributions. Certainly crda and wireless-regdb can be maintained separately so long as the key doesn't change between builds or with alternate keys installed in the proper locations. Am I missing something? John -- John W. Linville Someday the world will need a hero, and you linville@xxxxxxxxxxxxx might be all we have. Be ready. -- 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
