SelekTOR 3.12e for Linux Released

This release has a fix for an issue that prevented SelekTOR from starting up on some Debian based distros such as Siduction and SolydXK.
It doesn’t fix the error  but brings up a warning dialog indicating that you are missing the package libglib2.0-bin which needs to be installed for SelekTOR to function correctly.

So if you receive the error shown below on startup in the console on older releases of SelekTOR then install the package libglib2.0-bin.

Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
at lib.OSFunction.getGnome3Pref(
at client.PacFactory.backupProxyPrefs(

Once that package is installed SelekTOR should be good go.



SelekTOR 3.12d Released

See changelog for fixes.


SelekTOR 3.12c For Linux Released

Some minor fixes, see changelog.


SelekTOR 3.12b For Windows Released

This is a 5 day limited trial version with some functionality restrictions.

I will try to synch future releases to the Linux version but since they are now separate code bases this may not always be possible.



SelekTOR 3.12b For Linux Released

Added back in the Default HTTP Proxy feature as requested, it can now be found under Network Settings on the Advanced Preferences tab.


SelekTOR 3.12a Released

Fixed some minor issues related to the Tor Client monitor, see changelog for details.

Windows Trial version is progressing well, it will definitely be ready tomorrow.


SelekTOR V3.12 Released

Lots of changes on this one all related to improving SelekTOR’s transparency and safety.

New preferences and preferences panel layout, due to the major modifications on preferences, your preferences will be reset to the safer defaults when you first run this new version.
Those who run mostly in Proxy by Pattern mode for bypassing web blocks might want to enable “Use 2 hop circuits” for improved latency but remember this will reduce your anonymity, this is only active in Proxy by Pattern mode, switching back to Proxy All traffic mode will use the Tor default of 3 hop circuits at all times.

The Windows version will be released tomorrow, and I have relented, so it will be a 5 day trial version on release.

Due to the number of significant changes on this please let me know if you have any issues so I can get them fixed asap.


SelekTOR Progress Update

The work on latest SelekTOR release is progressing well, this release will implement the features I was talking about in my previous SelekTOR News  post.

Here are some screenshots of what I have so far, all the stuff shown has been implemented and are working but I may add some more such as “Wipe Tor Cache on Exit” although i’m not strictly convinced that this is necessary as their is nothing of interest within the cache files and the only thing they indicate is that you use Tor which is pretty obvious anyways, plus it slows down Tor startup but it is still under consideration and nothing has been ruled out, if folks would like to see other Tor client specific features added then just add a comment by clicking the comment bubble to this post.


Not sure when I will have all this ready as a lot of peripheral stuff still needs to be done such as language translations and updated help file, but at least you know what’s in the pipeline.


IMPORTANT: SelekTOR News Update

I have had some comments regarding SelekTOR, basically amounting to folks being worried or unsure as to what settings SelekTOR uses to run the Tor client, this is understandable when privacy issues are involved and even though the source code is available to all to see, not everyone can read code.

SelekTOR for the moment when run in the “Proxy all traffic” mode runs fairly safely using mostly the Tor client recommended defaults the exceptions to this is the SafeSocks flag which is set to enabled and the StrictNodes flag is also enabled.
Strictnodes is used by Tor to ensure only specified nodes is/are used and SafeSocks tells Tor to reject any connections using unsafe DNS lookups ie they will reject an ip address as it means the DNS lookup was not done via Tor and therefore your ip is being leaked because the DNS lookup was done externally.

Currently when running in “Proxy by pattern” mode anonymity is reduced, as only 2 hops to an exit node instead of the Tor default of 3 is used in an effort to improve latency therefore this mode should only be used for geo-blocks and not privacy.
The next version of SelekTOR will allow you to enforce the Tor default of 3 regardless of proxy modes or let SelekTOR set it based on proxy mode.

As to logging currently the Tor defaults are used and therefore logs are not written to disk, all output at notice level or above is written to the console.
SelekTOR itself will only log to disk if started with one of the –debug-all or –debug-warn command line options otherwise the only thing written to disk by SelekTOR is the preferences file and an empty torrc file.

I am working on adding a bunch of new features making SelekTOR more transparent regarding what settings it passes to the Tor client and making more of the Tor client settings accessible to the advanced user.
The advance user will also be able to add extra arguments that are not covered by the GUI itself.

I will also be endeavouring to make sure that SelekTOR’s simplicity and user friendliness remains intact as this was one of my original goals with SelekTOR.

I hope folks will be happy with the steps I intend to take to improve SelekTOR’s future transparency.


SelekTOR for Windows Released

See the main SelekTOR page for downloading and purchasing details.


DMCA Compliance