summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
author李 博洋 <[email protected]>2024-06-03 04:26:14 +0000
committer李 博洋 <[email protected]>2024-06-03 04:26:14 +0000
commit2f43d9bc1ed2711e5eac6ea07e7ffeec7fc9376e (patch)
treefedc8b3ad218a5e5db03134aaa8077290c8905f6
parent830c7ac0a298e3152c290844864e332ea368e7a6 (diff)
Update README.md,使用geneva进行修改
-rw-r--r--README.md31
1 files changed, 0 insertions, 31 deletions
diff --git a/README.md b/README.md
index 66af39b..f2ffca4 100644
--- a/README.md
+++ b/README.md
@@ -1,34 +1,3 @@
-# GET /out: Automated Discovery of Application-Layer Censorship Evasion Strategies Artifacts
-
-Evaluating our artifact will require an evaluator to retrieve our artifact from
-Zenodo, creating a cloud VPS, and issuing network requests to verify that our
-software evades censorship. Thank you to the artifact evaluators for examining
-our artifacts.
-
-## Artifacts Abstract
-In this paper, we present the first techniques to automate the discovery of new
-censorship evasion techniques purely in the application layer. We present a
-general solution and apply it specifically to HTTP and DNS censorship in China,
-India, and Kazakhstan. Our automated techniques discovered a total of 77 unique
-evasion strategies for HTTP and 9 for DNS, all of which require only
-application-layer modifications, making them easier to incorporate into apps and
-deploy. We analyze these strategies and shed new light into the inner workings
-of the censors. We find that the success of application-layer strategies can
-depend heavily on the type and version of the destination server. Surprisingly,
-a large class of our evasion strategies exploit instances in which censors are
-more RFC-compliant than popular application servers.
-
-For the purposes of this submission, our artifacts are (1) the strategies we
-present in the paper and (2) the code used to implement them. We developed our
-fuzzer by building off of the open-source Geneva project
-(https://github.com/Kkevsterrr/geneva), but our code has not yet merged into
-that repository publicly. Therefore, we have provided the full modified
-codebase to assist in the evaluation.
-
-For this artifact evaluation, we demonstrate how the reader can evaluate (1)
-that our strategies can generate modified requests; (2) that our strategies can
-evade censorship. Optionally, the evaluator can test for themselves that our
-tool can fuzz HTTP requests.
## Evaluation