diff options
| author | Chandradeep Dey <chandradeepdey@posteo.net> | 2020-02-26 00:31:24 +0530 |
|---|---|---|
| committer | Linus Färnstrand <linus@mullvad.net> | 2020-02-26 13:29:09 +0100 |
| commit | 4f712092e7de0613748ee3d3e39c07537d503b64 (patch) | |
| tree | 75d91d4b990c888f0b974a04e7e99bf2249798b0 /docs/security.md | |
| parent | e64e71c646b59c46459f3cf8cdee1c371a56230f (diff) | |
| download | mullvadvpn-4f712092e7de0613748ee3d3e39c07537d503b64.tar.xz mullvadvpn-4f712092e7de0613748ee3d3e39c07537d503b64.zip | |
Fix typo in docs/security.md
Diffstat (limited to 'docs/security.md')
| -rw-r--r-- | docs/security.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/security.md b/docs/security.md index 4e0ff30c3b..1d19ca2c01 100644 --- a/docs/security.md +++ b/docs/security.md @@ -186,7 +186,7 @@ The app avoids the term "kill switch". Because it sounds like a red button that has to be *engaged when a problem arises*. This app is much more proactive and applies [strict firewall rules](#app-states) directly when it leaves the [disconnected] state and keeps those rules active and enforced until the app comes back to the [disconnected] -state via an explicit user request again. Said strict firewall rules unsure that packets can only +state via an explicit user request again. Said strict firewall rules ensure that packets can only leave or enter the computer in a few predefined ways, most notably to the selected VPN server of course. Changes to the firewall are done in atomic transactions. Meaning there is no time window where no or invalid rules are active on the device. |