y.st./source/pages/en/weblog/2015/08-August/16.xhtml

<?php
/**
 * <https://y.st./>
 * Copyright © 2015 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'title' => 'A bug in the <code>torsocks</code> and <code>torify</code> commands',
	'body' => <<<END
<p>
	Someone on the <a href="ircs://irc.oftc.net:6697/%23Tor">$a[Tor] channel</a> was having trouble getting their graphical $a[IRC] client to work through $a[Tor], but having no trouble getting a text-based client to connect over $a[Tor].
	They cited the difference being that with the text-based client, they could run &quot;torsocks {client&quot;&quot; to start the command line client and force the connection through $a[Tor].
	I pointed out that the same can be done for graphical clients as well, you just have to start the graphical client from the command line.
	While trying to get this set up, we ran into an interesting bug in the <code>torsocks</code> command, a bug also present in the <code>torify</code> command.
	It appears that even if the application to be run through torsocks/torify has its path delimited by quotation marks, these two commands are unable to run applications that include spaces in their file paths.
	It seems though that this bug may only pertain to the parsing of the input to the command though, not the handling in the file system, as making a symbolic link to the path with spaces allows you to use the symbolic link as the input path to <code>torsocks</code>/<code>torify</code>, provided the path of the symbolic link itself has no spaces.
</p>
<p>
	My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
</p>
END
);