Re: [tor-talk] Tor 0.2.3.2-alpha is out

what is UseMicrodescriptors 1 work???????

> Date: Wed, 20 Jul 2011 23:15:54 -0600
> From: Jimmymac@xxxxxxxxxx
> To: tor-talk@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: [tor-talk] Tor 0.2.3.2-alpha is out
>
> Roger Dingledine wrote:
> > Tor 0.2.3.2-alpha introduces two new experimental features:
> > microdescriptors and pluggable transports. It also continues cleaning
> > up a variety of recently introduced features.
>
> [snip]
>
> > Changes in version 0.2.3.2-alpha - 2011-07-18
> > o Major features:
> > - Clients can now use microdescriptors instead of regular descriptors
> > to build circuits. Microdescriptors are authority-generated
> > summaries of regular descriptors' contents, designed to change
> > very rarely (see proposal 158 for details). This feature is
> > designed to save bandwidth, especially for clients on slow internet
> > connections. It's off by default for now, since nearly no caches
> > support it, but it will be on-by-default for clients in a future
> > version. You can use the UseMicrodescriptors option to turn it on.
>
> First, thank you for implementing this.
>
> I've download, compiled, and installed version 0.2.3.2-alpha. I
> previously ran version 0.2.1.30. I did not delete or alter ~/.tor
> between versions. I've added the following line to torrc:
>
> UseMicrodescriptors 1
>
> So far, after a brief test, everything seems to be fine. I was curious
> about what was logged and wondering if it represents any kind of an
> error or bug. The full log is listed at the end of this email. The
> lines I am wondering about are:
>
> Jul 20 19:42:30 Host Tor[9506]: I learned some more directory
> information, but not enough to build a circuit: We have only 0/2480
> usable microdescriptors.
> Jul 20 19:43:22 Host Tor[9506]: We now have enough directory information
> to build circuits.
> Jul 20 19:44:10 Host Tor[9506]: Bootstrapped 100%: Done.
>
> I am wondering if the first line is accurately reporting the state when
> 52 seconds later (with a 52kbps connection) it reports it has enough
> information to build circuits and 100 seconds after which, it reports
> 100% bootstrapped and stops downloading data (observer using iftop).
>
> Here is the full log (the two SIGHUPs were sent from a different command):
>
> Jul 20 19:41:41 Host Tor[9506]: Parsing GEOIP file
> /usr/local/share/tor/geoip.
> Jul 20 19:41:42 Host Tor[9506]: Configured to measure statistics. Look
> for the *-stats files that will first be written to the data directory
> in 24 hours from now.
> Jul 20 19:41:42 Host Tor[9506]: OpenSSL OpenSSL 0.9.8b 04 May 2006
> [90802f] looks like it's older than 0.9.8l, but some vendors have
> backported 0.9.8l's renegotiation code to earlier versions, and some
> have backported the code from 0.9.8m or 0.9.8n. I'll set both
> SSL3_FLAGS and SSL_OP just to be safe.
> Jul 20 19:41:42 Host Tor[9506]: Reloaded microdescriptor cache. Found 0
> descriptors.
> Jul 20 19:41:43 Host Tor[9506]: I learned some more directory
> information, but not enough to build a circuit: We have no usable
> consensus.
> Jul 20 19:41:44 Host Tor[9506]: Bootstrapped 5%: Connecting to directory
> server.
> Jul 20 19:41:44 Host Tor[9506]: Heartbeat: Tor's uptime is 0:00 hours,
> with 1 circuits open. I've pushed 0 kB and received 0 kB.
> Jul 20 19:41:47 Host Tor[9506]: Bootstrapped 10%: Finishing handshake
> with directory server.
> Jul 20 19:41:49 Host Tor[9506]: Bootstrapped 15%: Establishing an
> encrypted directory connection.
> Jul 20 19:41:50 Host Tor[9506]: Bootstrapped 20%: Asking for
> networkstatus consensus.
> Jul 20 19:41:51 Host Tor[9506]: Bootstrapped 25%: Loading networkstatus
> consensus.
> Jul 20 19:42:15 Host Tor[9506]: Received reload signal (hup). Reloading
> config and resetting internal state.
> Jul 20 19:42:15 Host Tor[9506]: Read configuration file
> "/usr/local/etc/tor/torrc".
> Jul 20 19:42:15 Host Tor[9506]: ControlPort is open, but no
> authentication method has been configured. This means that any program
> on your computer can reconfigure your Tor. That's bad! You should
> upgrade your Tor controller as soon as possible.
> Jul 20 19:42:23 Host Tor[9506]: Received reload signal (hup). Reloading
> config and resetting internal state.
> Jul 20 19:42:23 Host Tor[9506]: Read configuration file
> "/usr/local/etc/tor/torrc".
> Jul 20 19:42:23 Host Tor[9506]: ControlPort is open, but no
> authentication method has been configured. This means that any program
> on your computer can reconfigure your Tor. That's bad! You should
> upgrade your Tor controller as soon as possible.
> Jul 20 19:42:30 Host Tor[9506]: Bootstrapped 45%: Asking for relay
> descriptors.
> Jul 20 19:42:30 Host Tor[9506]: I learned some more directory
> information, but not enough to build a circuit: We have only 0/2480
> usable microdescriptors.
> Jul 20 19:43:22 Host Tor[9506]: We now have enough directory information
> to build circuits.
> Jul 20 19:43:22 Host Tor[9506]: Bootstrapped 80%: Connecting to the Tor
> network.
> Jul 20 19:43:34 Host Tor[9506]: Bootstrapped 85%: Finishing handshake
> with first hop.
> Jul 20 19:44:03 Host Tor[9506]: Bootstrapped 90%: Establishing a Tor
> circuit.
> Jul 20 19:44:10 Host Tor[9506]: Tor has successfully opened a circuit.
> Looks like client functionality is working.
> Jul 20 19:44:10 Host Tor[9506]: Bootstrapped 100%: Done.
>
>
>
>
>
>
> _______________________________________________
> tor-talk mailing list
> tor-talk@xxxxxxxxxxxxxxxxxxxx
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk