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

Assure freshness of contact verification attempts #63

Closed
azul opened this issue Jul 17, 2018 · 2 comments
Closed

Assure freshness of contact verification attempts #63

azul opened this issue Jul 17, 2018 · 2 comments

Comments

@azul
Copy link
Member

azul commented Jul 17, 2018

Bryan Ford is concerned with potential replay attacks a MITM attacker might be able to pull off against either Alice or Bob.

Adding a timestamp or expiry to ensure freshness would mitigate these.

(This issue is part of the feedback on the messaging@moderncrypto mailing list #61)

@azul
Copy link
Member Author

azul commented Jul 18, 2018

The most simple approach to me seems to track the time a QR code was shown or scanned on the respective device. The invite would remain valid for one day. If no message is received in that timeframe the record is removed from the database. This way we would not need to transfer timestamps or worry about synchronized clocks and timezones etc.

@azul
Copy link
Member Author

azul commented Aug 27, 2018

#66 addressed this.

@azul azul closed this as completed Aug 27, 2018
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

No branches or pull requests

1 participant