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.

Sign up for GitHub

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

Jump to bottom

Implement REQUIRE_AUTHENTICATED policy #154

Closed
olabini opened this issue Sep 21, 2018 · 2 comments
Closed

Implement REQUIRE_AUTHENTICATED policy #154

olabini opened this issue Sep 21, 2018 · 2 comments
Labels
architecture importance medium An issue that is medium level importance. It's good to have but not 100% necessary.
Milestone
March

Comments

@olabini
Copy link
Contributor

olabini commented Sep 21, 2018

This policy means that we will only activate any of the OTR behavior when the other party is likely to be authenticated. This means that before starting a DAKE, if we have at least one trusted fingerprint for the peer, we should go ahead with the DAKE. AFTER the DAKE, we should also ensure that the key used was one we have a trusted fingerprint for. Otherwise we should abort the DAKE.
This should be configurable through the UI as well.
@olabini olabini mentioned this issue Sep 21, 2018
Closed
@claucece claucece added importance medium An issue that is medium level importance. It's good to have but not 100% necessary. architecture labels Sep 21, 2018
@claucece claucece added this to the October milestone Oct 2, 2018
@claucece claucece modified the milestones: October, November Nov 4, 2018
@olabini olabini removed this from the November milestone Mar 11, 2019
@claucece
Copy link
Member

This depends on #28

@claucece claucece added this to the architecture milestone Oct 20, 2019
@claucece claucece modified the milestones: architecture, March Feb 6, 2020
claucece added a commit that referenced this issue Nov 29, 2020
@claucece
Implement REQUIRE_AUTHENTICATED policy #154
e587600
@claucece
Copy link
Member

Should be done now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
architecture importance medium An issue that is medium level importance. It's good to have but not 100% necessary.
Projects
None yet
Milestone
March
Development

No branches or pull requests
2 participants
@olabini @claucece