-
-
Notifications
You must be signed in to change notification settings - Fork 212
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
update: Add criteria to VPN Services page and update other sections #2788
Conversation
✅ Your preview is ready!
|
This pull request has been mentioned on Privacy Guides Community. There might be relevant details there: https://discuss.privacyguides.net/t/new-vpn-criterias-and-update-the-page/21864/1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm happy with all of @friadev's suggested changes here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR!
In addition to the changes I suggested below, the IPv6 entry for Proton VPN in the randomized table should be updated as well. | Done here: 25fcc8c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for all your work incorporating all of our feedback! I suggest some changes below for consistency reasons (making most of the criteria noun phrases), but the PR overall looks good to me.
You are welcome, I'm glad we can quickly update sections because it is important for PG credibility. I take this opportunity to ask you to please review my Pull Request about private AI chat (preview) |
This pull request has been mentioned on Privacy Guides Community. There might be relevant details there: https://discuss.privacyguides.net/t/add-ai-chat-tools/14347/164 |
…rivacyguides#2788) Updates include: - Obfuscation info, ProtonVPN IPv6 and added missing download links - added a few criteria Testing: - Proton has IPv6 support on Linux but it didn't work for me - Requirements for FDE/ram servers make sense to prevent logging by malicious employees. - Mullvad/IVPN are ram-only while Proton has FDE. - Requirements for the jurisdiction is to prevent cases like RiseupVPN (https://riseup.net/en/about-us/press/canary-statement). Co-authored-by: redoomed1 <161974310+redoomed1@users.noreply.github.com> Co-authored-by: fria <138676274+friadev@users.noreply.github.com> Signed-off-by: Daniel Gray <dngray@privacyguides.org>
This pull request has been mentioned on Privacy Guides Community. There might be relevant details there: |
List of changes proposed in this PR:
-It adds much needed information about Mullvad's new obfuscation tech, fixes a few quirks and add some info. More importantly, I introduced new criterias that all current VPN providers meet. Of course, those might need discussion in the forum.
Original changelog:
Justifcation for a few of the changes. First, while Proton technically has ipv6 support on Linux, it didn't work for me, so I didn't include it. Second, the requirements for FDE/ram servers make sense to prevent logging by malicious employees. Mullvad/IVPN are ram-only while Proton has FDE. Third, the requirements for the jurisdiction is to prevent cases like RiseUP VPN (https://riseup.net/en/about-us/press/canary-statement).