Bug 11904

Summary:	torify fails: torsocks not found
Product:	Mageia	Reporter:	Hartmut Goebel <h.goebel>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	fundawang
Version:	3	Keywords:	Triaged
Target Milestone:	Mageia 3
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	tor-0.2.3.25-3.mga3.src.rpm	CVE:
Status comment:

Description Hartmut Goebel 2013-12-06 21:14:27 CET

Can not run torify:

$ torify sh
/usr/bin/torify: torsocks not found in your PATH.  Perhaps it isn't installed?  (tsocks is no longer supported, for security reasons.)

Setting severity to "major" since this is disabling the major privacy-tool tor.

How to reproduce:

su - -c 'urpmi tor'
torify sh

Comment 1 Hartmut Goebel 2013-12-06 21:28:21 CET

Sorry, I was to fast with submitting the bug. More details:

* torsocks is not contained in any package of tor, tsocks or lib64tsocks1
* urpmf torsocks does not find any matching package
* current Cauldron release still requires tsocks (see <http://svnweb.mageia.org/packages/cauldron/tor/current/SPECS/tor.spec?revision=522686&view=markup>)
* torsocks is not available at <http://svnweb.mageia.org/packages/updates/3/>, but at <http://svnweb.mageia.org/packages/cauldron/torsocks/>

* torsocks from cauldron compiles for mga3, but fails to run: The symbol res_send() was not found in any shared library with the reported error: Not Found!

Comment 2 Manuel Hiebel 2013-12-22 13:44:46 CET

Hi, thanks for reporting this bug.
As there is no maintainer for this package I added the committers in CC.

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
CC: (none) => boklm, fundawang

Nicolas Vigier 2014-03-24 10:52:46 CET

CC: boklm => (none)

Comment 3 Marja Van Waes 2015-03-31 16:04:37 CEST

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD