-
Notifications
You must be signed in to change notification settings - Fork 50
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
Boundary between securesystemslib and TUF is off. #161
Comments
The general concept makes sense to me. |
We have some utility functions implemented in in-toto that might be a good fit for securesystemslib (see in-toto/in-toto#80). |
3 tasks
awwad
added a commit
that referenced
this issue
Apr 3, 2019
lukpueh
pushed a commit
that referenced
this issue
Sep 4, 2019
Fixed with #165 |
tanishqjasoria
pushed a commit
to tanishqjasoria/securesystemslib
that referenced
this issue
Jan 30, 2020
Largely resolves Issue secure-systems-lab#161, especially given the merge of PR secure-systems-lab#162. See GitHub: secure-systems-lab#161 secure-systems-lab#162 Signed-off-by: Sebastien Awwad <sebastien.awwad@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some of the functions in securesystemslib are really pieces of TUF that I don't think are of use to others and don't belong here.
Some examples that IIUC don't belong in securesystemslib:
Other functions that could conceivably be useful in general have zero context within the module:
Things I'm less sure about:
The text was updated successfully, but these errors were encountered: