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.

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

Remaining TUF 1.0 tasks #326

Merged

Conversation

vladimir-v-diaz
Copy link
Contributor

Implementation of remaining TUF 1.0 tasks:

  • redesign of repository tool
  • support role delegations that resemble a graph
  • store all delegations in one directory
  • update documentation to follow the new behaviour of the repository tool
  • Prevent freeze attacks where a client if left with stale, local metadata
  • Update repository data (used in tests) following all of the changes
  • WIP (Minor refactor of developer tool)

trishankkarthik and others added 30 commits February 19, 2016 17:27
Add all encountered delegated roles to the top-level targets object.  For example:
'django' role delegated by 'unclaimed' (which in turn was delgated by 'targets') is available at repository.targets('unclaimed')
A delegated rolename is no longer required to start with 'targets'
When loading roles from disk, ensure these roles are not marked as dirty.  Add a boolean to relevant functions to provide the option to update the roledb without marking roles as dirty
…add_role())

We shouldn't remove delegated roles if the repository can resemble a graph of delegations, since the delegations of one role are independent of another
@trishankkarthik
Copy link
Contributor

@JustinCappos I don't mean to make life more difficult, but could we flesh out Section 5.1 (The client application) a bit more?

Right now, there are not enough details for an independent programmer to implement a TUF client using that section. The programmer has to refer to the Python reference implementation.

I think it'd be a good idea to flesh out more details, because the UPTANE RFC will have skip over the TUF bits for brevity.

I'd love to contribute as I find the space and time, but I can't commit to it right now.

@vladimir-v-diaz
Copy link
Contributor Author

I think this is something Sebastien and I can work on, since it overlaps with changes he's making to support the Director role for Uptane (just finished discussing it in person). We can work on a more detailed client workflow for TUF 1.0, and then Sebastien can expand it for the changes needed for Uptane.

@JustinCappos
Copy link
Member

Okay, I think this is a good plan.

On Wed, Jul 27, 2016 at 11:33 AM, Vladimir Diaz [email protected]
wrote:

I think this is something Sebastien and I can work on, since it overlaps
with changes he's making to support the Director role for Uptane (just
finished discussing it in person). We can work on a more detailed client
workflow for TUF 1.0, and then Sebastien can expand it for the changes
needed for Uptane.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#326 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0XD_vkBU02LU3HWLzrKaP5Y5WWWBLQks5qZ3pjgaJpZM4IAobU
.

To simplify the addition of keys to keydb, add all of the valid keyids to keydb in the for loop instead of adding the default keyid separately
@vladimir-v-diaz vladimir-v-diaz merged commit 4d2c302 into theupdateframework:develop Jul 27, 2016
@vladimir-v-diaz
Copy link
Contributor Author

Note: I created a "master" branch and we'll edit the "develop" branch (containing the latest 1.0 changes) directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants