docs: site: pubkey_privacy works for wireguard #3254
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
maurerle
approved these changes
May 29, 2024
|
Please remove the Draft state and we can get this merged. |
blocktrron
added
the
2. status: waiting-on-author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I removed a comment from the site documentation citing, that fastd is the only vpn where
pubkey_privacyhas an effect.I just verified by editing /lib/gluon/site.json and running gluon-reconfigure and reboot, that this settings also works for wireguard VPNs.
I'm not sure whether it works for Tunneldigger, so this documentation change requires further feedback.
Is there a fourth VPN provider we support?