Tor 0.2.1.27 makes relays work with OpenSSL 0.9.8p and 1.0.0.b —
yet another OpenSSL security patch broke its compatibility with Tor.
We also took this opportunity to fix several crash bugs, integrate a
new directory authority, and update the bundled GeoIP database.
If you operate a relay, please upgrade.
https://www.torproject.org/download/download
Changes in version 0.2.1.27 – 2010-11-23
o Major bugfixes:
   – Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
     No longer set the tlsext_host_name extension on server SSL objects;
     but continue to set it on client SSL objects. Our goal in setting
     it was to imitate a browser, not a vhosting server. Fixes bug 2204;
     bugfix on 0.2.1.1-alpha.
   – Do not log messages to the controller while shrinking buffer
     freelists. Doing so would sometimes make the controller connection
     try to allocate a buffer chunk, which would mess up the internals
     of the freelist and cause an assertion failure. Fixes bug 1125;
     fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
   – Learn our external IP address when we’re a relay or bridge, even if
     we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
     where we introduced bridge relays that don’t need to publish to
     be useful. Fixes bug 2050.
   – Do even more to reject (and not just ignore) annotations on
     router descriptors received anywhere but from the cache. Previously
     we would ignore such annotations at first, but cache them to disk
     anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
   – When you’re using bridges and your network goes away and your
     bridges get marked as down, recover when you attempt a new socks
     connection (if the network is back), rather than waiting up to an
     hour to try fetching new descriptors for your bridges. Bugfix on
     0.2.0.3-alpha; fixes bug 1981.
o Major features:
   – Move to the November 2010 Maxmind GeoLite country db (rather
     than the June 2009 ip-to-country GeoIP db) for our statistics that
     count how many users relays are seeing from each country. Now we’ll
     have more accurate data, especially for many African countries.
o New directory authorities:
   – Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
     authority.
o Minor bugfixes:
   – Fix an assertion failure that could occur in directory caches or
     bridge users when using a very short voting interval on a testing
     network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
     0.2.0.8-alpha.
   – Enforce multiplicity rules when parsing annotations. Bugfix on
     0.2.0.8-alpha. Found by piebeer.
   – Allow handshaking OR connections to take a full KeepalivePeriod
     seconds to handshake. Previously, we would close them after
     IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
     were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
     for analysis help.
   – When building with –enable-gcc-warnings on OpenBSD, disable
     warnings in system headers. This makes –enable-gcc-warnings
     pass on OpenBSD 4.8.
o Minor features:
   – Exit nodes didn’t recognize EHOSTUNREACH as a plausible error code,
     and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
     stream ending reason for this case: END_STREAM_REASON_NOROUTE.
     Servers can start sending this code when enough clients recognize
     it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
   – Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
     Patch from mingw-san.
o Removed files:
   – Remove the old debian/ directory from the main Tor distribution.
     The official Tor-for-debian git repository lives at the URL
https://git.torproject.org/debian/tor.git
   – Stop shipping the old doc/website/ directory in the tarball. We
     changed the website format in late 2010, and what we shipped in
     0.2.1.26 really wasn’t that useful anyway.

Specifically, the big flaw in Tor <= 0.2.0.35 is that its list of
directory authorities is out of date, so you’ll find it hard to learn
about the network. We’re signing the network status consensus with the
old signatures for now, but we’re going to stop doing that in a few weeks,
which means your Tor 0.2.0.x will fail to find the current network.

The only exception is people using Debian Lenny — our nice Debian
packager is trying to keep that package maintained for you.

As a bonus, if you move to a newer Tor you’ll get significant performance
boosts as a client, and you’ll improve the performance for others as
a relay.

Thanks,
–Roger

Tor 0.2.1.24 makes Tor work again on the latest OS X — this time
for sure!

The Windows and OS X bundles also come with a newer version of Polipo
that fixes some stability and security problems.

People using Tor as a client should upgrade:
https://www.torproject.org/easy-download

Changes in version 0.2.1.23 – 2010-02-13
 o Major bugfixes (performance):
   - We were selecting our guards uniformly at random, and then weighting
     which of our guards we’d use uniformly at random. This imbalance
     meant that Tor clients were severely limited on throughput (and
     probably latency too) by the first hop in their circuit. Now we
     select guards weighted by currently advertised bandwidth. We also
     automatically discard guards picked using the old algorithm. Fixes
     bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.

 o Major bugfixes:
   - Make Tor work again on the latest OS X: when deciding whether to
     use strange flags to turn TLS renegotiation on, detect the OpenSSL
     version at run-time, not compile time. We need to do this because
     Apple doesn’t update its dev-tools headers when it updates its
     libraries in a security patch.
   - Fix a potential buffer overflow in lookup_last_hid_serv_request()
     that could happen on 32-bit platforms with 64-bit time_t. Also fix
     a memory leak when requesting a hidden service descriptor we’ve
     requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
     by aakova.

 o Minor bugfixes:
   - Refactor resolve_my_address() to not use gethostbyname() anymore.
     Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.

 o Minor features:
   - Avoid a mad rush at the beginning of each month when each client
     rotates half of its guards. Instead we spread the rotation out
     throughout the month, but we still avoid leaving a precise timestamp
     in the state file about when we first picked the guard. Improves
     over the behavior introduced in 0.1.2.17.

Changes in version 0.2.1.24 – 2010-02-21
 o Minor bugfixes:
   - Work correctly out-of-the-box with even more vendor-patched versions
     of OpenSSL. In particular, make it so Debian and OS X don’t need
     customized patches to run/build.

Forbidden City is the most famous place in Beijing, China. You can download this software to experience the Emperor’s home, and their lifes.

In my opioion, the software is too crude. Its pictures is not beyond world of warcraft’s. And it can not control the character by ASDW. You can only use the arrows button. You can not jump the character by press “space”. lol.

But, I suggest you can download and play it. I believe you will love this, love China.

Where I can download it?

Here: http://www.virtualforbiddencity.org/

https://www.torproject.org/download.html

Or use our new https://www.torproject.org/easy-download page.

Changes in version 0.2.0.32 – 2008-11-20
  o Security fixes:
    – The "User" and "Group" config options did not clear the
      supplementary group entries for the Tor process. The "User" option
      is now more robust, and we now set the groups to the specified
      user’s primary group. The "Group" option is now ignored. For more
      detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
      in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
      and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
    – The "ClientDNSRejectInternalAddresses" config option wasn’t being
      consistently obeyed: if an exit relay refuses a stream because its
      exit policy doesn’t allow it, we would remember what IP address
      the relay said the destination address resolves to, even if it’s
      an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.

  o Major bugfixes:
    – Fix a DOS opportunity during the voting signature collection process
      at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.

  o Major bugfixes (hidden services):
    – When fetching v0 and v2 rendezvous service descriptors in parallel,
      we were failing the whole hidden service request when the v0
      descriptor fetch fails, even if the v2 fetch is still pending and
      might succeed. Similarly, if the last v2 fetch fails, we were
      failing the whole hidden service request even if a v0 fetch is
      still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
    – When extending a circuit to a hidden service directory to upload a
      rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
      requests failed, because the router descriptor has not been
      downloaded yet. In these cases, do not attempt to upload the
      rendezvous descriptor, but wait until the router descriptor is
      downloaded and retry. Likewise, do not attempt to fetch a rendezvous
      descriptor from a hidden service directory for which the router
      descriptor has not yet been downloaded. Fixes bug 767. Bugfix
      on 0.2.0.10-alpha.

  o Minor bugfixes:
    – Fix several infrequent memory leaks spotted by Coverity.
    – When testing for libevent functions, set the LDFLAGS variable
      correctly. Found by Riastradh.
    – Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
      bootstrapping with tunneled directory connections. Bugfix on
      0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
    – When asked to connect to A.B.exit:80, if we don’t know the IP for A
      and we know that server B rejects most-but-not all connections to
      port 80, we would previously reject the connection. Now, we assume
      the user knows what they were asking for. Fixes bug 752. Bugfix
      on 0.0.9rc5. Diagnosed by BarkerJr.
    – If we overrun our per-second write limits a little, count this as
      having used up our write allocation for the second, and choke
      outgoing directory writes. Previously, we had only counted this when
      we had met our limits precisely. Fixes bug 824. Patch from by rovv.
      Bugfix on 0.2.0.x.
    – Remove the old v2 directory authority ‘lefkada’ from the default
      list. It has been gone for many months.
    – Stop doing unaligned memory access that generated bus errors on
      sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
    – Make USR2 log-level switch take effect immediately. Bugfix on
      0.1.2.8-beta.

  o Minor bugfixes (controller):
    – Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
      0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.

I used a relatively large number of QQ is the Remote Assistance, simple and practical. However, QQ Remote Assistance can not be typing on a computer in each other.

Here recommend a good software-TeamViewer.

After downloaded TeamViewer, you can choose to “install” or “Run” means that it can be installed or direct run. After the operation, such as the right.

Please wait a while just to run (about Several Seconds), which often have been found to generate ID and password, at this time, the ID and password can tell you friends, so that you can be friends on the right side of the Create Session enter your ID, after connecting a password, you can carry out long-range assistance.
TeamViewer has the advantage of: 1. Easy to use and can be installed directly to run free. 2. Do not have any complicated settings. 3. To break down the firewall, within a computer network is also very easy to connect. Not because of any port design, is ideal for use in local area networks. 4. Remote Assistance feature from time to time to chat. 5. VPN functions are. 6. For free.
Official Web site address (English): http://www.teamviewer.com/download/index.aspx

https://www.torproject.org/download.html

Changes in version 0.1.2.19 – 2008-01-17
  o Security fixes:
    – Exit policies now reject connections that are addressed to a
      relay’s public (external) IP address too, unless
      ExitPolicyRejectPrivate is turned off. We do this because too
      many relays are running nearby to services that trust them based
      on network address.

  o Major bugfixes:
    – When the clock jumps forward a lot, do not allow the bandwidth
      buckets to become negative. Fixes bug 544.
    – Fix a memory leak on exit relays; we were leaking a
cached_resolve_t
      on every successful resolve. Reported by Mike Perry.
    – Purge old entries from the “rephist” database and the hidden
      service descriptor database even when DirPort is zero.
    – Stop thinking that 0.1.2.x directory servers can handle
“begin_dir”
      requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
      crashing or mis-answering these requests.
    – When we decide to send a 503 response to a request for servers,
do
      not then also send the server descriptors: this defeats the whole
      purpose. Fixes bug 539.

  o Minor bugfixes:
    – Changing the ExitPolicyRejectPrivate setting should cause us to
      rebuild our server descriptor.
    – Fix handling of hex nicknames when answering controller requests
for
      networkstatus by name, or when deciding whether to warn about
      unknown routers in a config option. (Patch from mwenge.)
    – Fix a couple of hard-to-trigger autoconf problems that could
result
      in really weird results on platforms whose sys/types.h files
define
      nonstandard integer types.
    – Don’t try to create the datadir when running –verify-config or
      –hash-password. Resolves bug 540.
    – If we were having problems getting a particular descriptor from
the
      directory caches, and then we learned about a new descriptor for
      that router, we weren’t resetting our failure count. Reported
      by lodger.
    – Although we fixed bug 539 (where servers would send HTTP status
503
      responses _and_ send a body too), there are still servers out
there
      that haven’t upgraded. Therefore, make clients parse such bodies
      when they receive them.
    – Run correctly on systems where rlim_t is larger than unsigned
long.
      This includes some 64-bit systems.
    – Run correctly on platforms (like some versions of OS X 10.5)
where
      the real limit for number of open files is OPEN_FILES, not
rlim_max
      from getrlimit(RLIMIT_NOFILES).
    – Avoid a spurious free on base64 failure.
    – Avoid segfaults on certain complex invocations of
      router_get_by_hexdigest().
    – Fix rare bug on REDIRECTSTREAM control command when called with
no
      port set: it could erroneously report an error when none had
      happened.

We’ve been hard at work building the foundation for Windows Live Messenger 9.0, we’d like to give you a look at what we’ve built and ask what you think. We’re running a small private beta to get early feedback on the new features we’ve built and get wider test coverage of the build.

As a beta tester you’ll have access to an early 9.0 build, a private newsgroup just for Windows Live Messenger beta testers, and the ability to send bugs directly to the product team. The build you’ll be beta testing with is a very early build, so it may be less stable than beta builds you’ve tried in the past. We’re telling you this upfront so you know what you’re getting into. If you’re not sure about trying a not-quite polished build, maybe this beta isn’t for you. If you’re ready to dig in and explore this build with us, follow the below instructions to nominate yourself.

1. Go to http://connect.microsoft.com
2. Click “Invitation” in the left nav pane
3. Enter this invitation ID: B0-WBH8-FY44
4. Click Go
5. Fill out the nomination survey

We’ll review all survey responses and accept as many people into the beta as we can. Look for mail from us soon!

We look forward to hearing from you!
The Windows Live Messenger Team

We also modified the default Privoxy config files in the bundles to avoid some security problems, so make sure to leave “install Privoxy” checked when you upgrade.
Bundle users should upgrade. People using Privoxy in other contexts should make sure to follow the configuration advice at
https://www.torproject.org/docs/tor-doc-unix#privoxy
The Tor 0.1.1.x branch is now officially obsolete and unsupported.

https://www.torproject.org/download.html

Changes in version 0.1.2.18 – 2007-10-28
o Major bugfixes (crashes):
- If a connection is shut down abruptly because of something that happened inside connection_flushed_some(), do not call connection_finished_flushing(). Should fix bug 451:
“connection_stop_writing: Assertion conn->write_event failed”

Bugfix on 0.1.2.7-alpha.
- Fix possible segfaults in functions called from rend_process_relay_cell().

o Major bugfixes (hidden services):
- Hidden services were choosing introduction points uniquely by hexdigest, but when constructing the hidden service descriptor they merely wrote the (potentially ambiguous) nickname.
- Clients now use the v2 intro format for hidden service connections: they specify their chosen rendezvous point by identity digest rather than by (potentially ambiguous) nickname. These changes could speed up hidden service connections dramatically.

o Major bugfixes (other):
- Stop publishing a new server descriptor just because we get a HUP signal. This led (in a roundabout way) to some servers getting dropped from the networkstatus lists for a few hours each day.
- When looking for a circuit to cannibalize, consider family as well as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced circuit cannibalization).
- When a router wasn’t listed in a new networkstatus, we were leaving the flags for that router alone — meaning it remained Named, Running, etc — even though absence from the networkstatus means that it shouldn’t be considered to exist at all anymore. Now we clear all the flags for routers that fall out of the networkstatus consensus. Fixes bug 529.

o Minor bugfixes:
- Don’t try to access (or alter) the state file when running
–list-fingerprint or –verify-config or –hash-password.
Resolves
bug 499.
- When generating information telling us how to extend to a given router, do not try to include the nickname if it is absent. (Resolves bug 467.)
- Fix a user-triggerable segfault in expand_filename(). (There isn’t a way to trigger this remotely.)
- When sending a status event to the controller telling it that an OR address is readable, set the port correctly. (Previously we were reporting the dir port.)
- Fix a minor memory leak whenever a controller sends the
PROTOCOLINFO
command. Bugfix on 0.1.2.17.
- When loading bandwidth history, do not believe any information in the future. Fixes bug 434.
- When loading entry guard information, do not believe any information in the future.
- When we have our clock set far in the future and generate an onion key, then re-set our clock to be correct, we should not stop the onion key from getting rotated.
- On some platforms, accept() can return a broken address. Detect this more quietly, and deal accordingly. Fixes bug 483.
- It’s not actually an error to find a non-pending entry in the DNS cache when canceling a pending resolve. Don’t log unless stuff is fishy. Resolves bug 463.
- Don’t reset trusted dir server list when we set a configuration option. Patch from Robert Hogan.