📝 Correction | Auditing a VPN #2264

Open
opened 2021-04-19 07:52:19 +00:00 by ghost · 0 comments
ghost commented 2021-04-19 07:52:19 +00:00 (Migrated from github.com)

Description

The VPN requirements state "Published security audits from a reputable third-party firm.".
This is ambiguous.
You need to clarify whether you are auditing the VPN client or the VPN service itself.

Why I am making the suggestion

For Mullvad and ProtonVPN, the client source code is audited. The service itself has not been audited.
The server may be storing logs even if the client does not have a backdoor.

IVPN, on the other hand, is an audit of the service itself.
Mullvad/ProtonVPN and IVPN differ in the nature of the audit.

My connection with the software

No connection

  • I will keep the issue up-to-date if something I have said changes or I remember a connection with the software.
## Description The VPN requirements state "Published security audits from a reputable third-party firm.". This is ambiguous. You need to clarify whether you are auditing the VPN client or the VPN service itself. ## Why I am making the suggestion For Mullvad and ProtonVPN, the client source code is audited. The service itself has not been audited. The server may be storing logs even if the client does not have a backdoor. IVPN, on the other hand, is an audit of the service itself. Mullvad/ProtonVPN and IVPN differ in the nature of the audit. ## My connection with the software No connection <!-- Are you the author? Competitor? Just hating the software with passsion for some reason? --> - [x] I will keep the issue up-to-date if something I have said changes or I remember a connection with the software.
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#2264
No description provided.