Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
---|---|---|---|---|---|---|
dont_auto_create_keypair | [PATCH] Don't automatically create key-pairs If the private key is missing, this is probably an error in the build configuration. Don't create a private key unless it's the only explicit goal for make. |
Ben Hutchings <ben@decadent.org.uk> | no | |||
enable_recording_and_using_an_external_signature.patch | Enable recording and using an external signature To make wireless-regdb build reproducibly, we need a way to save the signature of the database to an external file and later reuse it instead of requiring the private key. [bwh: Update for version 2019.06.03 and Python 3 compatibility] [rperier: Update for version 2020.04.29] |
Jérémy Bobbio <lunar@debian.org> | no | debian | 2015-02-09 | |
split_signature_generation.patch | Split signature generation Now that db2bin.py supports recording a signature to re-use it later, we now split the generation of regulatory.bin to create an intermediate signature. The signature can then be shipped in the source to allow the build to be reproduced by independent parties. [bwh: Call the signature file regulatory.bin.sig, not signature. Update for version 2019.06.03.] |
Jérémy Bobbio <lunar@debian.org> | no | debian | 2015-02-09 | |
run-scripts-with-python-3.patch | Run scripts with Python 3 All the Python scripts here are meant to be Python 3 compatible, but they still use "/usr/bin/env python" as their interpreter. Since Debian is deprecating Python 2 but not (yet) changing "python" to Python 3, change the shebang lines. |
Ben Hutchings <ben@decadent.org.uk> | no | debian | 2020-01-29 |