Skip to content
Snippets Groups Projects
Unverified Commit 96dfbc46 authored by yanosz's avatar yanosz Committed by Martin Weinelt
Browse files

docs: Document location and handling of opkg keypair

parent 99e1e527
No related branches found
No related tags found
No related merge requests found
...@@ -159,6 +159,14 @@ to sign the generated package repository). ...@@ -159,6 +159,14 @@ to sign the generated package repository).
OpenWrt will handle the generation and handling of the keys itself. OpenWrt will handle the generation and handling of the keys itself.
When making firmware releases based on Gluon, it might make sense to store When making firmware releases based on Gluon, it might make sense to store
the keypair, so updating the module repository later is possible. 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: .. _getting-started-make-variables:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment