Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Minor tutorial related tweaks made after reviewing PR #775 #961

Merged
merged 2 commits into from
Nov 29, 2019
Merged

Minor tutorial related tweaks made after reviewing PR #775 #961

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
282c9aa
TUTORIAL: minor cleanup
joshuagl Nov 28, 2019
ff21b36
repository_tool: sort the list of roles in dirty_roles()
joshuagl Nov 28, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions docs/TUTORIAL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,14 +62,14 @@ and verify metadata files.
To begin, cryptographic keys are generated with the repository tool. However,
before metadata files can be validated by clients and target files fetched in a
secure manner, public keys must be pinned to particular metadata roles and
metadata signed by role's private keys. After covering keys, the four required
top-level metadata are created next. Examples are given demonstrating the
expected work flow, where the metadata roles are created in a specific order,
keys imported and loaded, and metadata signed and written to disk. Lastly,
target files are added to the repository, and a custom delegation performed to
extend the default roles of the repository. By the end, a fully populated TUF
repository is generated that can be used by clients to securely download
updates.
metadata signed by the role's private keys. After covering keys, the four
required top-level metadata are created next. Examples are given demonstrating
the expected work flow, where the metadata roles are created in a specific
order, keys imported and loaded, and metadata signed and written to disk.
Lastly, target files are added to the repository, and a custom delegation
performed to extend the default roles of the repository. By the end, a fully
populated TUF repository is generated that can be used by clients to securely
download updates.

### Keys ###
The repository tool supports multiple public-key algorithms, such as
Expand Down
2 changes: 1 addition & 1 deletion tuf/repository_tool.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -446,7 +446,7 @@ def dirty_roles(self):
None.
"""

logger.info('Dirty roles: ' + str(tuf.roledb.get_dirty_roles(self._repository_name)))
logger.info('Dirty roles: ' + str(sorted(tuf.roledb.get_dirty_roles(self._repository_name))))



Expand Down