From cc7da21ff6492daece4e803f540e217cc793d7e1 Mon Sep 17 00:00:00 2001 From: klzgrad Date: Thu, 4 Jun 2020 20:56:07 +0800 Subject: [PATCH] Update README.md Strategically reduce the amount of self-promotion. --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index fe3ebe1be1..168cc83f51 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # NaïveProxy [![Build Status](https://travis-ci.com/klzgrad/naiveproxy.svg?branch=master)](https://travis-ci.com/klzgrad/naiveproxy) [![Build status](https://ci.appveyor.com/api/projects/status/ohpyaf49baihmxa9?svg=true)](https://ci.appveyor.com/project/klzgrad/naiveproxy) -NaïveProxy uses Chrome's network stack to camouflage traffic with stronger censorship resistence and less detectablility than custom-made network stacks (Shadowsocks and variants, V2Ray suite, handmade Golang stacks). Reusing Chrome's stack also ensures NaïveProxy has the best practices in performance and security. +NaïveProxy uses Chrome's network stack to camouflage traffic with strong censorship resistence and low detectablility. Reusing Chrome's stack also ensures best practices in performance and security. The following traffic attacks are mitigated in NaïveProxy: @@ -9,6 +9,8 @@ The following traffic attacks are mitigated in NaïveProxy: * [Active probing](https://ensa.fi/active-probing/): defeated by *application fronting*, i.e. hiding proxy servers behind a commonly used frontend with application-layer routing. * Length-based traffic analysis: mitigated by length padding. +The code consists of a patch series morphed and rebased onto every new Chrome release. It's normal to see the latest commit being old, while most recent activities happen in [project releases](https://github.com/klzgrad/naiveproxy/releases). + ## Architecture [Browser → Naïve (client)] ⟶ Censor ⟶ [Frontend → Naïve (server)] ⟶ Internet