Dear Maintainer,

I recently encountered the error

    cfg80211: loaded regulatory.db is malformed or signature is missing/invalid

when booting kernel 5.8.7 without Debian patches.  Based on
/usr/share/doc/wireless-regdb/README.Debian I understand that this is
expected and I need to switch the regulatory.db alternative.  This all
works well, thanks.

However, I don't understand the implications of this change.  How does
the Debian version differ from the upstream version, if at all?  They
appear to be binary identical on my system, and that this is enforced by
the build scripts.  Is the difference only the signing keys?  Presumably
there is good reason for this divergence.  Would it be possible to
document the differences and motivation in README.Debian and/or
regulatory.db(5) to help users like myself understand?

Thanks,
Kevin

I just faced the same cfg80211 error, trying to switch from CRDA to the
kernel builtin feature. It took me a while to find this bug report and
about the need to switch to the upstream version of the database. Thanks
for the pointer, and my fault to not read the README.

Would be great if the difference and reasons behind the Debian version
of the database could be explained, as it seems to make things
complicated and breaks using the WiFi adapter properly OOTB, especially
in AP mode, when not using a Debian kernel. The kernel may not even have
support for CRDA enabled, as it is usually seen deprecated or at least
redundant.

Best regards,

Micha