Threat Model - Githubissues

vacp2p / research

Thinking in code

MIT License

62 stars 4 forks source link

Closed decanus closed 4 years ago

decanus commented 4 years ago

Currently there is no threat model attached to our protocol, this is an important aspect of building secure protocols however.

corpetty commented 4 years ago

propose to have a work session around the RFC. Desired outcomes will be:

detailed understanding of the work that needs to be done to have a completed RFC
who is going to own that
expected timeline to finish it

oskarth commented 4 years ago

What's the state of this issue? The goal was to have something timeboxed that could be done in April.

oskarth commented 4 years ago

This doesn't seem to be happening, especially last month. If it is deprioritized, let's be explicit and close it with a note.

@corpetty @decanus

oskarth commented 4 years ago

Yeah this never happened. In the future, please be explicit about deprio in issue so we can be honest with ourselves.