[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #10030 [Tor bundles/installation]: Tor pluggable transport bundle does not work in OS X Mavericks
#10030: Tor pluggable transport bundle does not work in OS X Mavericks
------------------------------------------+------------------------------
Reporter: msfc | Owner:
Type: defect | Status: needs_review
Priority: normal | Milestone:
Component: Tor bundles/installation | Version: Tor: 0.2.4.16-rc
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
------------------------------------------+------------------------------
Changes (by dcf):
* status: new => needs_review
Comment:
I found a workaround that we can deploy relatively quickly without having
to modify tor.
The problem is that Finder in Mavericks sets the current directory to /,
so relative paths to pluggable transport executables don't work. What we
can do is move `tor` to `tor.real` and then create a shell script `tor`
with something like:
{{{
#!/bin/sh
cd $(dirname $0)
exec ./tor.real $@
}}}
I tested this idea on Mavericks and it works. What do you say?
Vidalia is using the above mentioned `QApplication::applicationDirPath`
([https://gitweb.torproject.org/vidalia.git/blob/dd3a52e6d4ca7522df9773d5997cfa83c50a7421:/src/vidalia/MainWindow.cpp#l1192
see here]), which is why it didn't break with the changed behavior in
Mavericks.
A more permanent fix may be to have tor do this same thing: either set its
current directory or else absolutize the paths to subprograms based on the
executable directory.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10030#comment:20>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs