Archived
Clarify and expand VPN criteria #1175
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1175
Reference in New Issue
Block a user
Building on https://github.com/privacytoolsIO/privacytools.io/pull/1174#discussion_r314960176, this PR expands our criteria to be more "complete". It also adds the number of servers and locations to each provider.
Deploy preview for privacytools-io ready!
Built with commit
3aec5c328chttps://deploy-preview-1175--privacytools-io.netlify.com
Change “required” to “require”?
@@ -23,0 +101,4 @@<ul><li>Strongest Encryption: RSA-4096.</li><li>Perfect Forward Secrecy (PFS).</li><li>Comprehensive published security audits from a reputable third-party firm.</li>Should we specify a desired time since the audit was conducted? Like for these audit(s) to be “recent/relevant”?
Minor suggestions but overall LGTM 👍🏼 Awesome work.
@@ -23,0 +101,4 @@<ul><li>Strongest Encryption: RSA-4096.</li><li>Perfect Forward Secrecy (PFS).</li><li>Comprehensive published security audits from a reputable third-party firm.</li>On L89 I did say
...on a repeated (yearly) basis.which I think covers that. That would be for the best-case scenario though. As far as making it a minimum criteria, I'm not sure how many providers would be running audits frequently. We're getting to the point where if we're any more strict we can't recommend anybody.