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