From c5f7c1edce747972b5912fb7f7cf188be18c104c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E5=8A=A0=E9=87=8C?= Date: Tue, 18 Nov 2014 20:14:25 +0800 Subject: [PATCH] update doc --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 636d126..75fd9be 100644 --- a/README.md +++ b/README.md @@ -85,7 +85,7 @@ After configuring rootCA, anyproxy could help to decrypt https requests, whose a #### step 2 - generate a rootCA and trust it * you should do this when it is the first time to start anyproxy * execute ``sudo anyproxy --root`` ,follow the instructions on screen -* [important!]you will see some tip like *rootCA generated at : ~/.anyproxy_certs... . ``cd`` to that directory, add/trust the rootCA.crt file to your system keychain. In OSX, you may do that by open the *crt file directly +* [important!]you will see some tip like *rootCA generated at : ~/.anyproxy_certs... . ``cd`` to that directory, add/trust the rootCA.crt file to your system keychain. In OSX, you may do that by open the \*.crt file directly * when debug https requests, you have to trust this rootCA on all of your clients. #### to intercept(decrypt) https requests