Tor was updated to fix one logging privacy issue. Reproducible: Steps to Reproduce:
CC: (none) => jani.valimaaSee Also: (none) => https://bugzilla.suse.com/show_bug.cgi?id=943362
Proposed advisory ################# Tor was updated to fix one logging privacy issue. The following issue was fixed: * Malformed hostnames in socks5 requests were written to the log regardless of SafeLogging option References: https://bugzilla.suse.com/show_bug.cgi?id=943362 https://trac.torproject.org/projects/tor/ticket/16891 https://bugs.mageia.org/show_bug.cgi?id=16729
Mageia 5 RPM/SRPM: tor-0.2.5.12-1.1.mga5 Mageia 4 RPM/SRPM: tor-0.2.4.27-1.1.mga4
Whiteboard: (none) => MGA4TOO
See Also: (none) => https://trac.torproject.org/projects/tor/ticket/16891
URL: (none) => http://lwn.net/Vulnerabilities/656901/
Started tor as previously installed and did a search using packaged tor browser. Changed repo to update-testing. installed 2.5.12. This did not update the browser from 4.5.2, only the connection client. Restarted the tor-browser, repeated the search. No obvious issues.
CC: (none) => vzawalin1Whiteboard: MGA4TOO => MGA4TOO MGA5-64-OK
Testing complete mga4 32 Started tor service and configured firefox to use socks proxy of localhost with port 9050. Check it was connecting through tor at https://check.torproject.org
Whiteboard: MGA4TOO MGA5-64-OK => MGA4TOO MGA5-64-OK mga4-32-ok
Validating. Advisory uploaded from comment 1 & comment 2. Please push to 4 & 5 updates Thanks
Keywords: (none) => validated_updateWhiteboard: MGA4TOO MGA5-64-OK mga4-32-ok => MGA4TOO has_procedure advisory MGA5-64-OK mga4-32-okCC: (none) => sysadmin-bugs
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2015-0124.html
Status: NEW => RESOLVEDResolution: (none) => FIXED