Skip to content

Harden BAF handling by adding term #1021

Description

@tock-ibm

What's optionally left to do is to:

  • check for primary self-signed equivocation even if they are not propagated to secondaries,
  • include the term in the BAF for easy filtering of secondary's bogus self signed BAFs (terms from the future, term != primary, etc).

Originally posted by @tock-ibm in #37

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions