-
Notifications
You must be signed in to change notification settings - Fork 275
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.
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
Misleading / missing steps in TUTORIAL for delegated roles #838
Comments
Two parts of this issue have been addressed:
However one item remains, a warning that indicates that the verification keys have "already been used" is still emitted. I don't think warning is the right log level for this. In what scenarios is the message useful? Could the logged message be clearer about what the impact is? |
I can only guess, but I would say the original intention was to prevent someone from re-using the same key for different roles, which is a legitimate motivation. But as @awwad indicates above, the warning does not check for key re-use among roles, it just checks if the key, detached from any role, is already in the keydb (a global dictionary associated with a repository). My assessment:
|
Btw. thanks for updating the status of this issue, @joshuagl! |
Closing this issue as it was filed against (what is now known as) the legacy codebase: issue seems to not be relevant anymore. Please re-open or file a new issue if you feel that the issue is revelant to current python-tuf. TUTORIAL is no longer, we have examples in examples/ directory though. More detailsCurrent source code (and upcoming 1.0 release) only contains the modern components
Legacy components (e.g. tuf.client, tuf.repository_tool, tuf.repository_lib as well as the repo and client scripts) are no longer included. See announcement and API reference for more details. |
There are a few issues here:
The output if you try to delegate to a delegated role can include two warnings that may be misleading, as it is not made clear in standard out that they are warnings:
The tutorial doesn't tell you how to deal with writing delegated roles, which requires that you mark the role (and timestamp and snapshot at least) as dirty, every time.
The text was updated successfully, but these errors were encountered: