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

Match no OpenVPN relays when core privacy features are enabled #6668

Merged
merged 2 commits into from
Aug 28, 2024

Conversation

dlon
Copy link
Member

@dlon dlon commented Aug 23, 2024

WireGuard will always be preferred, when any of these features is enabled, even when the tunnel protocol is set to auto.

Core privacy features include PQ, multihop, and DAITA.

Close DES-1066.


This change is Reviewable

Copy link

linear bot commented Aug 23, 2024

@dlon dlon marked this pull request as ready for review August 23, 2024 11:24
@Serock3 Serock3 self-requested a review August 23, 2024 11:43
Copy link
Contributor

@hulthe hulthe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 5 of 6 files at r1, 1 of 1 files at r2, all commit messages.
Reviewable status: 6 of 7 files reviewed, 2 unresolved discussions (waiting on @dlon)


CHANGELOG.md line 31 at r2 (raw file):

### Changed
- OpenVPN is never used as a fallback protocol when any of the following features is enabled:
  multihop, quantum-resistant tunnels, or DAITA.

should have an imperative form

Suggestion:

Disable use of OpenVPN as a fallback protocol when any of the following features is enabled:

mullvad-relay-selector/src/relay_selector/matcher.rs line 168 at r2 (raw file):

/// Returns whether `relay` satisfy the daita constraint posed by `filter`.
pub fn filter_on_daita(filter: &Constraint<bool>, relay: &Relay) -> bool {

BTW I'd argue it's more type safe to pass the &WireguardRelayQuery instead of the bool constraint since it's such a non-specific type. Feel free to ignore if you disagree though

Copy link
Member Author

@dlon dlon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 2 of 8 files reviewed, 3 unresolved discussions (waiting on @hulthe and @Serock3)


CHANGELOG.md line 31 at r2 (raw file):

Previously, hulthe (Joakim Hulthe) wrote…

should have an imperative form

Suggestion:

Disable use of OpenVPN as a fallback protocol when any of the following features is enabled:

Done.

Copy link
Contributor

@hulthe hulthe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 3 of 6 files at r3, 1 of 3 files at r4, all commit messages.
Reviewable status: 6 of 9 files reviewed, 2 unresolved discussions (waiting on @Serock3)

Copy link
Contributor

@Serock3 Serock3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 1 of 6 files at r1, 1 of 1 files at r2, 2 of 6 files at r3, 2 of 3 files at r4, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved

Core privacy features currently include PQ, multihop, and
DAITA
@dlon dlon merged commit 4f6e151 into main Aug 28, 2024
55 checks passed
@dlon dlon deleted the disable-openvpn-fallback branch August 28, 2024 12:21
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

Successfully merging this pull request may close these issues.

3 participants