Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
FFS Gluon
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
firmware
FFS Gluon
Commits
96dfbc46
Unverified
Commit
96dfbc46
authored
4 years ago
by
yanosz
Committed by
Martin Weinelt
3 years ago
Browse files
Options
Downloads
Patches
Plain Diff
docs: Document location and handling of opkg keypair
Co-Authored-By:
Martin Weinelt
<
martin@darmstadt.freifunk.net
>
parent
99e1e527
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/user/getting_started.rst
+8
-0
8 additions, 0 deletions
docs/user/getting_started.rst
with
8 additions
and
0 deletions
docs/user/getting_started.rst
+
8
−
0
View file @
96dfbc46
...
@@ -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:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment