en:developers:regulatory:wireless-regdb
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:developers:regulatory:wireless-regdb [2015/11/24 07:42] Xose Vazquez Perez |
en:developers:regulatory:wireless-regdb [2023/12/22 03:50] (current) Chen-Yu Tsai [Releases of wireless-regdb] Remove dead release page |
||
|---|---|---|---|
| Line 14: | Line 14: | ||
| ===== The regulatory database ===== | ===== The regulatory database ===== | ||
| - | [[en/developers/Regulatory/CRDA|CRDA]] requires a regulatory database ([[en/developers/Regulatory/Database|Web view]] or [[http://git.kernel.org/?p=linux/kernel/git/sforshee/wireless-regdb.git;a=blob;f=db.txt;hb=HEAD|gitweb]]) to be build and maintained. Our hope is that this database can be used by other platforms (open or proprietary), not just Linux. Seth Forshee maintains this database through the wireless-regdb git tree: | + | [[en/developers/Regulatory/CRDA|CRDA]] requires a regulatory database ([[en/developers/Regulatory/Database|Web view]] or [[http://git.kernel.org/?p=linux/kernel/git/wens/wireless-regdb.git;a=blob;f=db.txt;hb=HEAD|gitweb]]) to be build and maintained. Our hope is that this database can be used by other platforms (open or proprietary), not just Linux. The database is currently unmaintained, but the latest changes can be found in this git tree: |
| - | [[http://git.kernel.org/?p=linux/kernel/git/sforshee/wireless-regdb.git|http://git.kernel.org/?p=linux/kernel/git/sforshee/wireless-regdb.git]] | + | [[http://git.kernel.org/?p=linux/kernel/git/wens/wireless-regdb.git|http://git.kernel.org/?p=linux/kernel/git/wens/wireless-regdb.git]] |
| - | <code>git://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git</code> | + | <code>git://git.kernel.org/pub/scm/linux/kernel/git/wens/wireless-regdb.git</code> |
| The regulatory.bin file there is signed with his RSA private key. We keep the RSA public key embedded as part of CRDA which allows us to verify the authorship and integrity of the regulatory database. | The regulatory.bin file there is signed with his RSA private key. We keep the RSA public key embedded as part of CRDA which allows us to verify the authorship and integrity of the regulatory database. | ||
| Line 25: | Line 25: | ||
| ===== Releases of wireless-regdb ===== | ===== Releases of wireless-regdb ===== | ||
| - | You can find official wireless-regdb releases on the [[http://drvbp1.linux-foundation.org/~mcgrof/rel-html/wireless-regdb/|wireless-regdb release page]], all releases can be downloaded through the [[http://kernel.org/pub/software/network/wireless-regdb/|wireless-regdb archive]] | + | You can find official wireless-regdb releases through the [[http://kernel.org/pub/software/network/wireless-regdb/|wireless-regdb archive]] |
| Line 34: | Line 34: | ||
| <code>country EC: | <code>country EC: | ||
| - | (2402 - 2482 @ 40), (N/A, 20) | + | (2400 - 2483.5 @ 40), (1000 mW) |
| - | (5170 - 5250 @ 20), (6, 17) | + | (5150 - 5250 @ 80), (50 mW), AUTO-BW, DFS |
| - | (5250 - 5330 @ 20), (6, 23), DFS | + | (5250 - 5350 @ 80), (125 mW), AUTO-BW, DFS |
| - | (5735 - 5835 @ 20), (6, 30)</code> | + | (5470 - 5725 @ 160), (125 mW), DFS |
| - | Note that the frequency range (e.g. <code>2402-2482</code>) covers the complete used bandwidth, so this definition allows using the 2 GHz channels 1 through 13 as 40 MHz channels. 5 GHz channels of a bandwidth of 20 MHz can be used if the frequencies used by the channel fit into the specified frequency ranges. | + | (5725 - 5850 @ 80), (1000 mW)</code> |
| + | Note that the frequency range (e.g. <code>2400-2483.5</code>) covers the complete used bandwidth, so this definition allows using the 2 GHz channels 1 through 13 as 40 MHz channels. 5 GHz channels of a bandwidth of 80 or 160 MHz can be used if the frequencies used by the channel fit into the specified frequency ranges. | ||
| Line 48: | Line 49: | ||
| ===== RSA Digital Signature ===== | ===== RSA Digital Signature ===== | ||
| - | Integrity of the binary regulatory file is ensured by digitally signing the regulatory data using a private key and embedding the signature into the binary file. When the file is loaded by the regulatory daemon the signature is checked against a list of public keys built into the regulatory daemon binary or by by checking against the list of public keys in a preconfigured directory. This process ensures regulatory.bin file authorship and integrity. | + | Integrity of the binary regulatory file is ensured by digitally signing the regulatory data using a private key and embedding the signature into the binary file. When the file is loaded by the regulatory daemon the signature is checked against a list of public keys built into the regulatory daemon binary or by checking against the list of public keys in a preconfigured directory. This process ensures regulatory.bin file authorship and integrity. |
| Both CRDA and wireless-regdb allows you to build it without RSA key signature checking, if this is something you find useless then do not use them, but we advise against it. The reason RSA digital signature checks are an option and is what is recommend is that regulatory bodies are highly sensitive towards compliance and the current infrastructure we have gives us best effort on our part of doing the best we can to ensure integrity of the files and also gives us a mechanism to use files from trusted parties on-the-fly. Distribution packaging tends to guarantee file integrity upon installation time and from a specific source but it does not give you on-the-fly file integrity checks. Integrity checks are possible through alternate means such as simple CRC checks but you'd then need a list of all allowed CRCs, by using RSA digital signatures you get both file integrity checks for _any_ binary built with the private key by checking for the signature -- and while at it you also can get file authorship protection -- all of this while the file is being read for usage in memory. Distributions do not protect against file corruption after the files are in place, for example. | Both CRDA and wireless-regdb allows you to build it without RSA key signature checking, if this is something you find useless then do not use them, but we advise against it. The reason RSA digital signature checks are an option and is what is recommend is that regulatory bodies are highly sensitive towards compliance and the current infrastructure we have gives us best effort on our part of doing the best we can to ensure integrity of the files and also gives us a mechanism to use files from trusted parties on-the-fly. Distribution packaging tends to guarantee file integrity upon installation time and from a specific source but it does not give you on-the-fly file integrity checks. Integrity checks are possible through alternate means such as simple CRC checks but you'd then need a list of all allowed CRCs, by using RSA digital signatures you get both file integrity checks for _any_ binary built with the private key by checking for the signature -- and while at it you also can get file authorship protection -- all of this while the file is being read for usage in memory. Distributions do not protect against file corruption after the files are in place, for example. | ||
| Line 59: | Line 60: | ||
| ===== Sending updates to the regulatory database ===== | ===== Sending updates to the regulatory database ===== | ||
| - | If you find any errors please send them to the [[http://lists.infradead.org/mailman/listinfo/wireless-regdb|wirleess-regdb]](subscribers-only) mailing list and the [[en/developers/MailingLists|linux-wireless mailing list]], either as patches to the [[http://git.kernel.org/?p=linux/kernel/git/sforshee/wireless-regdb.git;a=blob;f=db.txt;hb=HEAD|db.txt]] file from the [[http://git.kernel.org/?p=linux/kernel/git/sforshee/wireless-regdb.git;a=summary|wireless-regdb git tree]], or just tell us what is wrong in plain English. | + | **Note**: wireless-regdb is currently unmaintained, and patches or requests for changes are likely to get no response. |
| + | |||
| + | If you find any errors please send them to the [[http://lists.infradead.org/mailman/listinfo/wireless-regdb|wireless-regdb]](subscribers-only) mailing list and the [[en/developers/MailingLists|linux-wireless mailing list]], either as patches to the [[http://git.kernel.org/?p=linux/kernel/git/wens/wireless-regdb.git;a=blob;f=db.txt;hb=HEAD|db.txt]] file from the [[http://git.kernel.org/?p=linux/kernel/git/wens/wireless-regdb.git;a=summary|wireless-regdb git tree]], or just tell us what is wrong in plain English. | ||
| Patches sent to the wireless-regdb git tree should be addressed as follows: | Patches sent to the wireless-regdb git tree should be addressed as follows: | ||
| - | <code>To: seth.forshee@canonical.com | + | <code>To: linux-wireless@vger.kernel.org |
| - | Cc: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org | + | Cc: wireless-regdb@lists.infradead.org |
| Subject: wireless-regdb: Update regulatory rules for France (FR) on 5GHz</code> | Subject: wireless-regdb: Update regulatory rules for France (FR) on 5GHz</code> | ||
| Line 80: | Line 83: | ||
| To change the file format you will need to send patches to both crda (start off with regdb.h) and wireless-regdb/dbparse.py. You should send your patch as an RFC on the linux-wireless mailing list and CC both the wireless-regdb and crda maintainers. | To change the file format you will need to send patches to both crda (start off with regdb.h) and wireless-regdb/dbparse.py. You should send your patch as an RFC on the linux-wireless mailing list and CC both the wireless-regdb and crda maintainers. | ||
| + | |||
en/developers/regulatory/wireless-regdb.1448350971.txt.gz · Last modified: 2015/11/24 07:42 by Xose Vazquez Perez
Page Tools
