[tor-commits] [tor/master] dir_connection_t: Explain dirconn_direct better

[teor@xxxxxxxxxxxxxx]

commit 08efb28743038894f8ac6f53a7a3dfa5d1bd824a
Author: teor <teor@xxxxxxxxxxxxxx>
Date:   Wed Jan 22 09:27:40 2020 +1000

    dir_connection_t: Explain dirconn_direct better
    
    Direct connections can use a DirPort or ORPort.
    Indirect connections must use a multi-hop Tor circuit.
    
    Comment-only changes.
---
 src/feature/dircommon/dir_connection_st.h | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/feature/dircommon/dir_connection_st.h b/src/feature/dircommon/dir_connection_st.h
index 2c68e6184..12230e674 100644
--- a/src/feature/dircommon/dir_connection_st.h
+++ b/src/feature/dircommon/dir_connection_st.h
@@ -28,7 +28,9 @@ struct dir_connection_t {
   * fingerprints.
   **/
   char *requested_resource;
-  unsigned int dirconn_direct:1; /**< Is this dirconn direct, or via Tor? */
+  /** Is this dirconn direct, or via a multi-hop Tor circuit?
+   * Direct connections can use the DirPort, or BEGINDIR over the ORPort. */
+  unsigned int dirconn_direct:1;
 
   /** If we're fetching descriptors, what router purpose shall we assign
    * to them? */

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