[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-commits] [stem/master] Using sub-headers for connection/authentication methods



commit 632de4498defe1002a9c6ee2fe8aac4a58866608
Author: Damian Johnson <atagar@xxxxxxxxxxxxxx>
Date:   Sat Mar 22 12:25:55 2014 -0700

    Using sub-headers for connection/authentication methods
    
    Using headers rather than an unordered list for the sections so we can link
    directly to them.
---
 docs/faq.rst |   12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/docs/faq.rst b/docs/faq.rst
index 72c7db1..4e79251 100644
--- a/docs/faq.rst
+++ b/docs/faq.rst
@@ -96,7 +96,8 @@ Yup. You don't need a library to interact with Tor's `controller interface <http
 
 We'll tackle each of these scenarios one at a time...
 
-* **I'm using a ControlPort**
+**I'm using a ControlPort**
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 If you are using a **ControlPort** then the easiest method of talking with Tor is via **telnet**. You always need to authenticate after connecting, even if Tor does not restrict access. If your torrc doesn't have a **CookieAuthentication** or **HashedControlPassword** then to authenticate you will simply call **AUTHENTICATE** after connecting without any credentials.
 
@@ -118,7 +119,8 @@ If you are using a **ControlPort** then the easiest method of talking with Tor i
   250 closing connection
   Connection closed by foreign host.
 
-* **I'm using a ControlSocket**
+**I'm using a ControlSocket**
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 A **ControlSocket** is a file based socket, so we'll use **socat** to connect to it...
 
@@ -136,7 +138,8 @@ A **ControlSocket** is a file based socket, so we'll use **socat** to connect to
   QUIT
   250 closing connection
 
-* **I'm using cookie authentication**
+**I'm using cookie authentication**
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Cookie authentication simply means that your credential is the content of a file in Tor's **DataDirectory**. You can learn information about Tor's method of authentication (including the cookie file's location) by calling **PROTOCOLINFO**...
 
@@ -178,7 +181,8 @@ To get the credential for your AUTHENTICATE command we will use **hexdump**...
   250 closing connection
   Connection closed by foreign host.
 
-* **I'm using password authentication**
+**I'm using password authentication**
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Tor's other method of authentication is a credential you know. To use it you ask Tor to hash your password, then use that in your torrc...
 

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits