Changes in version 0.2.1.8-alpha - 2008-12-08
+ Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
+ builds better on unusual platforms like Solaris and old OS X, and
+ fixes a variety of other issues.
+
o Major features:
- New DirPortFrontPage option that takes an html file and publishes
it as "/" on the DirPort. Now relay operators can provide a
Changes in version 0.2.0.32 - 2008-11-20
+ Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
+ packages (and maybe other packages) noticed by Theo de Raadt, fixes
+ a smaller security flaw that might allow an attacker to access local
+ services, further improves hidden service performance, and fixes a
+ variety of other issues.
+
o Security fixes:
- The "User" and "Group" config options did not clear the
supplementary group entries for the Tor process. The "User" option
Changes in version 0.2.1.7-alpha - 2008-11-08
+ Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
+ packages (and maybe other packages) noticed by Theo de Raadt, fixes
+ a smaller security flaw that might allow an attacker to access local
+ services, adds better defense against DNS poisoning attacks on exit
+ relays, further improves hidden service performance, and fixes a
+ variety of other issues.
+
o Security fixes:
- The "ClientDNSRejectInternalAddresses" config option wasn't being
consistently obeyed: if an exit relay refuses a stream because its
each development snapshot, see the ChangeLog file.
Changes in version 0.2.0.32 - 2008-11-20
+ Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
+ packages (and maybe other packages) noticed by Theo de Raadt, fixes
+ a smaller security flaw that might allow an attacker to access local
+ services, further improves hidden service performance, and fixes a
+ variety of other issues.
+
o Security fixes:
- The "User" and "Group" config options did not clear the
supplementary group entries for the Tor process. The "User" option
To avoid being trivially distinguished from servers, client-only Tor
instances are encouraged but not required to use a two-certificate chain
- as well. Clients SHOULD NOT use keep using the same certificates when
- their IP changes. Clients MAY send no certificates at all.
+ as well. Clients SHOULD NOT keep using the same certificates when
+ their IP address changes. Clients MAY send no certificates at all.
3. Cell Packet format