Anzeigen der neuesten Beiträge
0 Mitglieder und 5 Gäste betrachten dieses Thema.
Tor 0.2.2.38 fixes a rare race condition that can crash exit relays; fixes a remotely triggerable crash bug; and fixes a timing attack that could in theory leak path information.o Security fixes:- Avoid read-from-freed-memory and double-free bugs that could occur when a DNS request fails while launching it. Fixes bug 6480; bugfix on 0.2.0.1-alpha.- Avoid an uninitialized memory read when reading a vote or consensus document that has an unrecognized flavor name. This read could lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.- Try to leak less information about what relays a client is choosing to a side-channel attacker. Previously, a Tor client would stop iterating through the list of available relays as soon as it had chosen one, thus finishing a little earlier when it picked a router earlier in the list. If an attacker can recover this timing information (nontrivial but not proven to be impossible), they could learn some coarse-grained information about which relays a client was picking (middle nodes in particular are likelier to be affected than exits). The timing attack might be mitigated by other factors (see bug 6537 for some discussion), but it's best not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
A security update to the Pidgin-OTR plugin for Pidgin Portable has been released. We don't normally announce plugin updates on the homepage and RSS, but as this is a rather important security update fixing a possible remote code execution bug in the plugin, we decided we wanted to be sure our users know. The updated plugin is available from the Pidgin Portable homepage. Just install it over your current install to update. All users who use Pidgin-OTR should upgrade immediately.
A regression that slipped into 1.1.14 final has been corrected; thanks to all the people who submitted crash telemetry so quickly. We apologize for the incovenience.