tor-webwml.git

@@ -117,7 +117,9 @@ Internet addresses correctly).

 </li>

 <li>The easier step to configure a relay is to use Vidalia.  The more advanced step is to edit your torrc directly.

-<ul><strong>Easy Configuration</strong>:

+<br />

+<strong>Easy Configuration</strong>:

+<ul>

 <li>Right click on the Vidalia icon in your task bar.  Choose <tt>Control Panel</tt>.</li>

 <li>Click <tt>Setup Relaying</tt>.</li>

 <li>Choose <tt>Relay Traffic for the Tor network</tt>.</li>

@@ -132,9 +134,11 @@ the services you don't want to allow through your relay.  If you want to

 be a non-exit relay, un-check all services.</li>

 <li>Click the <tt>Ok</tt> button.  See Step Two below for confirmation

 that the relay is working correctly.</li>

-</li>

+</ul>

+<br />

 <strong>Advanced Configuration</strong>:

+<ul>

 <li>Edit the bottom part of your torrc. (See <a

 href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">this

 FAQ entry</a> for help.)

@@ -144,8 +148,7 @@ tor. <em>If you want to run more than one relay that's great, but

 please set <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#MultipleRelays">the

 MyFamily option</a> in all your relays' configuration files.</em></li>

-</li>

-</ul>

+</ul></li>

 <li> If you are using a firewall, open a hole in your firewall so

 incoming connections can reach the ports you configured (ORPort, plus

@@ -154,7 +154,7 @@ Bardziej zaawansowanym krokiem jest bezpośrednia edycja pliku torrc.

  <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#MultipleRelays">opcję

  MyFamily</a> w plikach konfiguracyjnych wszystkich przekaźników.</em>

  </li>

-</ul>

+</ul></li>

 <li>

  Jeśli używasz zapory ogniowej, otwórz w niej przejście, by połączenia

@@ -113,8 +113,10 @@ Simple proxy providers also create a single point of failure.  The provider know

 <p>

 Tor passes your traffic through at least 3 different servers before sending it on to the destination.  Tor does not modify, or even know, what you are sending into it.  It merely relays your traffic, completely encrypted through the Tor network and has it pop out somewhere else in the world, completely intact.  The Tor client is required because we assume you trust your local computer.  The Tor client manages the encryption and the path chosen through the network.  The relays located all over the world merely pass encrypted packets between themselves.</p>

 <p>

+<dl>

 <dt>Doesn't the first server see who I am?</dt><dd>Possibly. A bad first of three servers can see encrypted Tor traffic coming from your computer.  It still doesn't know who you are and what you are doing over Tor.  It merely sees "This IP address is using Tor".  Tor is not illegal anywhere in the world, so using Tor by itself is fine.  You are still protected from this node figuring out who you are and where you are going on the Internet.</dd>

 <dt>Can't the third server see my traffic?</dt><dd>Possibly.  A bad third of three servers can see the traffic you sent into Tor.  It won't know who sent this traffic.  If you're using encryption, such as visiting a bank or ecommerce website, or encrypted mail connections, etc, it will only know the destination.  It won't be able to see the data inside the traffic stream.  You are still protected from this node figuring out who you are and if using encryption, what data you're sending to the destination.</dd>

+</dl>

 </p>

 <a id="CompatibleApplications"></a>

@@ -64,7 +64,7 @@ enhance your own security</a>.)

 If running a relay isn't for you, we need

 <a href="<page volunteer>">help with many other aspects of the project</a>,

 and we need funds to continue making the Tor network faster and easier to use while maintaining good

-security</a>.</p>

+security.</p>

 <p>Tor is a registered 501(c)(3) non-profit whose mission is to allow you to protect your Internet traffic from analysis. Please make a <a href="<page donate>">tax-deductible donation.</a>

 </p>

@@ -128,7 +128,7 @@ Tor-related stories that have popped up.  </p>

 <tr style="background-color: #e5e5e5;">

 <td>2009 Apr 22</td>

 <td>Le Monde</td>

-<td><a href="http://bugbrother.blog.lemonde.fr/2009/04/22/comment-contourner-la-cybersurveillance/">How to circumvent cybersurveillance</td>

+<td><a href="http://bugbrother.blog.lemonde.fr/2009/04/22/comment-contourner-la-cybersurveillance/">How to circumvent cybersurveillance</a></td>

 </tr>

 <tr>

 <td>2009 Apr 06</td>

@@ -130,6 +130,7 @@ na świecie, całkowicie nienaruszony. Klient Tora jest wymagany, gdyż zakłada

 do swojego komputera. Klient Tora zarządza szyfrowaniem i wybraną ścieżką przez sieć Tora.

 Przekaźniki rozmieszczone na całym świecie tylko przekazują zaszyfrowane pakiety między sobą.</p>

 <p>

+<dl>

 <dt>Czy pierwszy serwer nie widzi, kim jestem?</dt><dd>Być może. Zły pierwszy z trzech

 serwerów może widzieć zaszyfrowany ruch Tora pochodzący z Twojego komputera. Ale ciągle

 nie wie, kim jesteś i co robisz przez Tora. Po prostu widzi "Ten adres IP używa Tora".

@@ -142,6 +143,7 @@ połączeń do poczty itd., będzie tylko znał przeznaczenie. Nie będzie widza

 strumieniu ruchu.  Jesteś ciągle chroniony/a przed tym, by ten węzeł odkrył, kim jesteś,

 a jeśli używasz szyfrowania - także przed zobaczenie Twoich danych wysyłanych do ich

 miejsca przeznaczenia.</dd>

+</dl>

 </p>

@@ -243,8 +243,8 @@ implementation and testing work on January 15, 2009.

     <a id="Oct08"></a>

     <a class="anchor" href="#Oct08">Oct 08</a>

   </td>

-  <td>

-<small><em><p>We didn't hit our "finish

+  <td><p>

+<small><em>We didn't hit our "finish

 the implementation" milestone for this month since the developer leading

 the project has too much on his plate. The good news there is that we've

 gotten quite a bit of the implementation work done, and it's been in for

@@ -255,13 +255,13 @@ circuit (we probably want to use a new cell type specifically for this,

 so we cut out a round-trip), and then teach clients to do that when the

 relay they're using is running a recent enough version. These two steps

 are written in more detail in

-<a href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/141-jit-sd-downloads.txt">Section 3.2 of proposal 141</a></p>

+<a href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/141-jit-sd-downloads.txt">Section 3.2 of proposal 141</a></em></small></p>

-<p>Our new timing plan is to have both of these pieces in place by mid Nov,

+<p><small><em>Our new timing plan is to have both of these pieces in place by mid Nov,

 and if that starts looking less likely then we're going to do a more

-radical overhaul of our timing plan and maybe also the design.</p>

+radical overhaul of our timing plan and maybe also the design.</em></small></p>

- <p>There are several other components we'd like to get

+<p><small><em>There are several other components we'd like to get

 to after this piece of it -- one we've been thinking about a lot lately

 is downloading "diffs" of the latest consensus:

 <a href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/140-consensus-diffs.txt">140-consensus-diffs.txt</a>.

@@ -277,7 +277,7 @@ advantage of transient relays: right now a relay needs to be up for 3 or

 who want to run a relay but only want to be up a few hours at a time.</p>

 <p>The next step is to get the

 implementation for proposal 141 finished so we can start putting it in

-front of users for testing. Soon, we hope!</p></em></small>

+front of users for testing. Soon, we hope!</em></small></p>

   </td>

 </tr>

@@ -287,23 +287,23 @@ front of users for testing. Soon, we hope!</p></em></small>

     <a class="anchor" href="#Nov08">Nov 08</a>

   </td>

   <td>

-<small><em><p>It looks like the

+<p><small><em>It looks like the

 original plan we had for the last development piece was both a) way

-harder than we hoped, and b) hopefully overkill compared to what we need.</p>

+harder than we hoped, and b) hopefully overkill compared to what we need.</em></small></p>

-<p> Roger restarted the design discussion on or-dev:

-<a href="http://archives.seul.org/or/dev/Nov-2008/threads.html">http://archives.seul.org/or/dev/Nov-2008/threads.html</a>.</p>

+<p><small><em> Roger restarted the design discussion on or-dev:

+<a href="http://archives.seul.org/or/dev/Nov-2008/threads.html">http://archives.seul.org/or/dev/Nov-2008/threads.html</a>.</em></small></p>

-<p>I think we now have a better handle on the options and tradeoffs:

-<a href="http://archives.seul.org/or/dev/Nov-2008/msg00007.html">http://archives.seul.org/or/dev/Nov-2008/msg00007.html</a>.</p>

+<p><small><em>I think we now have a better handle on the options and tradeoffs:

+<a href="http://archives.seul.org/or/dev/Nov-2008/msg00007.html">http://archives.seul.org/or/dev/Nov-2008/msg00007.html</a>.</em></small></p>

-<p>Nick has been buried in other development projects (hopefully starting to

+<p><small><em>Nick has been buried in other development projects (hopefully starting to

 wrap up this month-ish), and I want to get his opinion on how to proceed;

-I am hoping we'll pick one of the more simple approaches.</p>

+I am hoping we'll pick one of the more simple approaches.</em></small></p>

-<p>Alas, the really simple approaches provide less scalability. But I think

+<p><small><em>Alas, the really simple approaches provide less scalability. But I think

 they will be good stopgaps until later -- and when 'later' arrives, who

-knows what else will have changed.</p></em></small>

+knows what else will have changed.</em></small></p>

   </td>

 </tr>

@@ -313,18 +313,18 @@ knows what else will have changed.</p></em></small>

     <a class="anchor" href="#Jan09">Jan 09</a>

   </td>

   <td>

-<small><em><p>

+<p><small><em>

 I wrote up the more detailed version of our new design idea, as <a

 href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/158-microdescriptors.txt">Tor

 proposal #158</a>, and discussion has started at <a

-href="http://archives.seul.org/or/dev/Jan-2009/msg00010.html">http://archives.seul.org/or/dev/Jan-2009/msg00010.html</a>.</p>

+href="http://archives.seul.org/or/dev/Jan-2009/msg00010.html">http://archives.seul.org/or/dev/Jan-2009/msg00010.html</a>.</em></small></p>

-<p>

+<p><small><em>

 I think this is finally the one! (Well, once I finish folding in all

 the comments.)

-</p>

+</em></small></p>

-<p>

+<p><small><em>

 One of the big reasons why the project isn't on its original schedule is

 that a main conclusion from <a href="<page projects/hidserv>">Karsten's

 NLnet project on hidden service performance</a> was that it's the circuit

@@ -332,13 +332,13 @@ extension that's the main killer. Yet this project had proposed to add

 more round-trips and complexity into exactly that step. So we needed

 to build a better plan to achieve the original goal without screwing up

 performance even more.

-</p>

+</em></small></p>

-<p>We've been revising the design proposal over the past weeks, and

+<p><small><em>We've been revising the design proposal over the past weeks, and

 I think we'll be ready soon to start implementing. Note that since

 we have a bunch of development items we're hoping to land in mid Feb

 already, it's likely that this implementation won't land until late Feb

-or March. This time for sure!</p></em></small>

+or March. This time for sure!</em></small></p>

   </td>

 </tr>

 </table>

@@ -282,7 +282,7 @@ Na przykład, wyłączenie "Uruchamiania przy starcie" ("Run at Startup"), jak p

 <p>Wybierz "Zmień" ("Change"), by zapisać te zmiany w zainstalowanym oprogramowaniu.</p>

-<p><img src="img/change05.png" alt=">Wybierz Zmień, by potwierdzić zmiany" /></p>

+<p><img src="img/change05.png" alt="Wybierz Zmień, by potwierdzić zmiany" /></p>

 <p>I w końcu "Zakończ" ("Finish"), by zamknąć interfejs graficzny instalatora. Żądane zmiany

 zostały teraz wprowadzone.</p>