This repository has been archived by the owner on May 21, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 61
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1769 from advancedtelematic/feat/prep-2020.10
preparing 2020.10
- Loading branch information
Showing
8 changed files
with
54 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
name: ota-client | ||
title: OTA Connect Developer Guide | ||
version: latest | ||
display_version: 2020.9 (latest) | ||
display_version: 2020.10 (latest) | ||
nav: | ||
- modules/ROOT/nav.adoc |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
27 changes: 27 additions & 0 deletions
27
docs/ota-client-guide/modules/ROOT/pages/finding-unsigned-metadata.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
= Find the unsigned Root and Targets metadata | ||
ifdef::env-github[] | ||
|
||
[NOTE] | ||
==== | ||
We recommend that you link:https://docs.ota.here.com/ota-client/latest/{docname}.html[view this article in our documentation portal]. Not all of our articles render correctly in GitHub. | ||
==== | ||
endif::[] | ||
|
||
If you want to use your own PKI, you need to know where in your local repository you can find the metadata that you want to sign. | ||
It may be the `root.json` or `targets.json` files. You can find both files in the `tuf/<reponame>/roles/unsigned` folder. | ||
|
||
NOTE: <reponame> is the name you specified when you initialized your repository using `garage-sign init`. | ||
|
||
If the `unsigned/` folder is empty, you need to pull the metadata files: | ||
|
||
* To pull the unsigned `root.json` file, use `garage-sign root pull`. | ||
* To pull the unsigned `targets.json` file, use `garage-sign targets pull`. | ||
If you have not created any targets, to create the unsigned `targets.json` file, use `garage-sign targets init`. | ||
|
||
To learn more about the `garage-sign` commands and options, see its xref:garage-sign-reference.adoc[reference] documentation. | ||
|
||
== Generate Root and Targets metadata in a canonical form | ||
|
||
To generate unsigned metadata in a canonical form, use the `garage-sign root get-unsigned` and `garage-sign targets get-unsigned` commands | ||
for the unsigned `root.json` and `targets.json` files respectively. The files that you get are stored in the `unsigned/` folder. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters