User Tools

Site Tools


en:developers:regulatory

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
en:developers:regulatory [2015/01/26 09:49]
127.0.0.1 external edit
en:developers:regulatory [2015/03/23 01:49] (current)
Seth Forshee [Importing your public key into CRDA]
Line 115: Line 115:
 ==== Importing your public key into CRDA ==== ==== Importing your public key into CRDA ====
  
-CRDA has a directory, //pubkeys// of all trusted public keys it can use to embed onto the binary for RSA signature verification against any particular binary regulatory database. This is used to allow CRDA to trust different authors for regulatory information. By default ​John Linville's key is always present on the pubkeys directory. You can remove it if for your particular application you cannot trust the upstream community regulatory database information. ​+CRDA has a directory, //pubkeys// of all trusted public keys it can use to embed onto the binary for RSA signature verification against any particular binary regulatory database. This is used to allow CRDA to trust different authors for regulatory information. By default ​Seth Forshee's key is always present on the pubkeys directory. You can remove it if for your particular application you cannot trust the upstream community regulatory database information. ​
  
 CRDA can be built with gcrypt or openssl support. If using openssl (USE_OPENSSL=1) you can enable dynamic loading of trusted public keys and stuff custom public keys at any time into the /​etc/​wireless-regdb/​pubkeys directory (by default). ​ CRDA can be built with gcrypt or openssl support. If using openssl (USE_OPENSSL=1) you can enable dynamic loading of trusted public keys and stuff custom public keys at any time into the /​etc/​wireless-regdb/​pubkeys directory (by default). ​
en/developers/regulatory.1422265793.txt.gz ยท Last modified: 2015/03/23 01:49 (external edit)