alex
/
gluon-firmware2
forked from Freifunk-Leipzig/gluon-firmware
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

docs: Document location and handling of opkg keypair 

Co-Authored-By: Martin Weinelt <martin@darmstadt.freifunk.net>
This commit is contained in:
yanosz 2020-11-24 20:54:06 +01:00 committed by Martin Weinelt
parent 99e1e52740
commit 96dfbc46c0
No known key found for this signature in database
GPG Key ID: 87C1E9888F856759
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/user/getting_started.rst
View File

@ -159,6 +159,14 @@ to sign the generated package repository).
OpenWrt will handle the generation and handling of the keys itself.
When making firmware releases based on Gluon, it might make sense to store
the keypair, so updating the module repository later is possible.
In fact you should take care to reuse the same opkg keypair, so you don't pollute the key
store (see ``/etc/opkg/keys``) on the node.
The signing-key is stored at ``openwrt/key-build.pub``, ``openwrt/key-build``,
``key-build.ucert`` and ``key-build.ucert.revoke``.
The ``openwrt`` directory is the Git checkout, that gets created after calling ``make update``.
After making a fresh clone copy the key files to the aforementioned locations.
.. _getting-started-make-variables: