Skip to content

ngclient: test fast-forward recovery #1713

Description

@jku

I think we do not currently test successful rollback (aka fast-forward recovery) for timestamp, snapshot and targets:

  • simulate a fast-forward attack: create repository with valid timestamp/snapshot/targets with version=MAX_VERSION (or something large anyway)
  • update client so it sees the large versions
  • rotate the affected key (timestamp or snapshot) and set metadata version=1
  • update client, assert that new metadata is accepted by ngclient (even though the version number is lower than the local version)

Activity

  1. added this to the Sprint 14 milestone on Dec 8, 2021
  2. kairoaraujo commented on Dec 8, 2021

    @kairoaraujo
    Contributor

    Please, can you sign this issue for me?

  3. jku commented on Dec 15, 2021

    @jku
    MemberAuthor

    create repository with valid timestamp/snapshot/targets with version=MAX_VERSION

    I'm not sure if there even is a practical MAX_VERSION in our implementation -- python seems to seamlessly upgrade from an int to some big int implementation... I think this is not relevant anyway: the point is that version is something large that we want to reinitialize to 1.

  4. jku commented on Jan 11, 2022

    @jku
    MemberAuthor

    I think we're done here! Thanks Kairo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions