Greetings,
a few days ago we integrated ScrambleSuit to obfsproxy. ScrambleSuit is a pluggable transport by Philipp Winter; you can find more about it at: http://www.cs.kau.se/philwint/scramblesuit/
If you are running a bridge, please consider upgrading your obfsproxy to the latest version (0.2.6) by using pip or fetching the latest git master. Unfortunately, we don't have Linux packages yet, but we will hopefully have some soon. In the meanwhile, we would appreciate some testing :)
After you upgrade obfsproxy, please change your ServerTransportPlugin line from: ServerTransportPlugin obfs2,obfs3 exec /usr/bin/obfsproxy managed to: ServerTransportPlugin obfs3,scramblesuit exec /usr/bin/obfsproxy managed
This will disable obfs2 [0] and enable scramblesuit.
It's also important to know that scramblesuit is a password-based pluggable transport, which means that each scramblesuit bridge has a password and if the user doesn't know the password he/she can't connect to the bridge. If you publishing your bridge to BridgeDB, Tor will automatically send the ScrambleSuit password to BridgeDB so that clients can get it. By default ScrambleSuit will generate a random password; if you want to specify your own password, you can use a torrc line like this: ServerTransportOptions scramblesuit password=LLDNOWV7I4P6RKFJMDEMIY2GNU2IQISA
By the way, expect not to see any scramblesuit users in the beginning. After a few people have set up scramblesuit bridges, we will roll out a Tor Browser Bundle with scramblesuit enabled.
Feel free to ask any questions you have!
Thanks!
PS: If you are running a bridge without any pluggable transports, please consider installing obfsproxy [1]. Normal bridges are not hard to block these days and we are working on increasing the number of obfuscated bridges out there.
[0]: https://trac.torproject.org/projects/tor/ticket/10314 [1]: https://www.torproject.org/projects/obfsproxy.html.en
On Mon, Feb 10, 2014 at 5:04 PM, George Kadianakis desnacked@riseup.net wrote:
Greetings,
a few days ago we integrated ScrambleSuit to obfsproxy. ScrambleSuit is a pluggable transport by Philipp Winter; you can find more about it at: http://www.cs.kau.se/philwint/scramblesuit/
If you are running a bridge, please consider upgrading your obfsproxy to the latest version (0.2.6) by using pip or fetching the latest git master. Unfortunately, we don't have Linux packages yet, but we will hopefully have some soon. In the meanwhile, we would appreciate some testing :)
After you upgrade obfsproxy, please change your ServerTransportPlugin line from: ServerTransportPlugin obfs2,obfs3 exec /usr/bin/obfsproxy managed to: ServerTransportPlugin obfs3,scramblesuit exec /usr/bin/obfsproxy managed
This will disable obfs2 [0] and enable scramblesuit.
It's also important to know that scramblesuit is a password-based pluggable transport, which means that each scramblesuit bridge has a password and if the user doesn't know the password he/she can't connect to the bridge. If you publishing your bridge to BridgeDB, Tor will automatically send the ScrambleSuit password to BridgeDB so that clients can get it. By default ScrambleSuit will generate a random password; if you want to specify your own password, you can use a torrc line like this: ServerTransportOptions scramblesuit password=LLDNOWV7I4P6RKFJMDEMIY2GNU2IQISA
By the way, expect not to see any scramblesuit users in the beginning. After a few people have set up scramblesuit bridges, we will roll out a Tor Browser Bundle with scramblesuit enabled.
Feel free to ask any questions you have!
I just installed version 0.2.6 and tried to make my normal bridge a bridge with obfsproxy, but it fails to start it. In Tor log all i see is the below
Feb 10 18:30:44.000 [warn] The communication stream of managed proxy '/usr/bin/obfsproxy' is 'closed'. Most probably the managed proxy stopped running. This might be a bug of the managed proxy, a bug of Tor, or a misconfiguration. Please enable logging on your managed proxy and check the logs for errors.
My torrc config contains the following:
ServerTransportPlugin obfs3,scramblesuit exec /usr/bin/obfsproxy managed
Running obfsproxy from CLI works just fine
Please advise
Thanks!
PS: If you are running a bridge without any pluggable transports, please consider installing obfsproxy [1]. Normal bridges are not hard to block these days and we are working on increasing the number of obfuscated bridges out there.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Grozdan neutrino8@gmail.com writes:
On Mon, Feb 10, 2014 at 5:04 PM, George Kadianakis desnacked@riseup.net wrote:
Greetings,
a few days ago we integrated ScrambleSuit to obfsproxy. ScrambleSuit is a pluggable transport by Philipp Winter; you can find more about it at: http://www.cs.kau.se/philwint/scramblesuit/
If you are running a bridge, please consider upgrading your obfsproxy to the latest version (0.2.6) by using pip or fetching the latest git master. Unfortunately, we don't have Linux packages yet, but we will hopefully have some soon. In the meanwhile, we would appreciate some testing :)
After you upgrade obfsproxy, please change your ServerTransportPlugin line from: ServerTransportPlugin obfs2,obfs3 exec /usr/bin/obfsproxy managed to: ServerTransportPlugin obfs3,scramblesuit exec /usr/bin/obfsproxy managed
This will disable obfs2 [0] and enable scramblesuit.
It's also important to know that scramblesuit is a password-based pluggable transport, which means that each scramblesuit bridge has a password and if the user doesn't know the password he/she can't connect to the bridge. If you publishing your bridge to BridgeDB, Tor will automatically send the ScrambleSuit password to BridgeDB so that clients can get it. By default ScrambleSuit will generate a random password; if you want to specify your own password, you can use a torrc line like this: ServerTransportOptions scramblesuit password=LLDNOWV7I4P6RKFJMDEMIY2GNU2IQISA
By the way, expect not to see any scramblesuit users in the beginning. After a few people have set up scramblesuit bridges, we will roll out a Tor Browser Bundle with scramblesuit enabled.
Feel free to ask any questions you have!
I just installed version 0.2.6 and tried to make my normal bridge a bridge with obfsproxy, but it fails to start it. In Tor log all i see is the below
Feb 10 18:30:44.000 [warn] The communication stream of managed proxy '/usr/bin/obfsproxy' is 'closed'. Most probably the managed proxy stopped running. This might be a bug of the managed proxy, a bug of Tor, or a misconfiguration. Please enable logging on your managed proxy and check the logs for errors.
My torrc config contains the following:
ServerTransportPlugin obfs3,scramblesuit exec /usr/bin/obfsproxy managed
Hm.
Can you make sure that obfsproxy is in /usr/bin/obfsproxy? Depending on how you installed obfsproxy-0.2.6, the executable might be in /usr/local/bin/ or elsewhere.
If that doesn't work, try this torrc line instead: ServerTransportPlugin obfs3,scramblesuit exec /usr/local/bin/obfsproxy --log-min-severity=debug --log-file=/home/user/obfs.log managed
this will turn on logging for obfsproxy and create a logfile in your home directory (fix the /home/user/obfs.log path). Please start up Tor again and check out the log file. If the log file doesn't get created it means that obfsproxy failed before writing the log file (this might be a permissions problem, or something else).
On Mon, Feb 10, 2014 at 6:54 PM, George Kadianakis desnacked@riseup.net wrote:
Grozdan neutrino8@gmail.com writes:
On Mon, Feb 10, 2014 at 5:04 PM, George Kadianakis desnacked@riseup.net wrote:
Greetings,
a few days ago we integrated ScrambleSuit to obfsproxy. ScrambleSuit is a pluggable transport by Philipp Winter; you can find more about it at: http://www.cs.kau.se/philwint/scramblesuit/
If you are running a bridge, please consider upgrading your obfsproxy to the latest version (0.2.6) by using pip or fetching the latest git master. Unfortunately, we don't have Linux packages yet, but we will hopefully have some soon. In the meanwhile, we would appreciate some testing :)
After you upgrade obfsproxy, please change your ServerTransportPlugin line from: ServerTransportPlugin obfs2,obfs3 exec /usr/bin/obfsproxy managed to: ServerTransportPlugin obfs3,scramblesuit exec /usr/bin/obfsproxy managed
This will disable obfs2 [0] and enable scramblesuit.
It's also important to know that scramblesuit is a password-based pluggable transport, which means that each scramblesuit bridge has a password and if the user doesn't know the password he/she can't connect to the bridge. If you publishing your bridge to BridgeDB, Tor will automatically send the ScrambleSuit password to BridgeDB so that clients can get it. By default ScrambleSuit will generate a random password; if you want to specify your own password, you can use a torrc line like this: ServerTransportOptions scramblesuit password=LLDNOWV7I4P6RKFJMDEMIY2GNU2IQISA
By the way, expect not to see any scramblesuit users in the beginning. After a few people have set up scramblesuit bridges, we will roll out a Tor Browser Bundle with scramblesuit enabled.
Feel free to ask any questions you have!
I just installed version 0.2.6 and tried to make my normal bridge a bridge with obfsproxy, but it fails to start it. In Tor log all i see is the below
Feb 10 18:30:44.000 [warn] The communication stream of managed proxy '/usr/bin/obfsproxy' is 'closed'. Most probably the managed proxy stopped running. This might be a bug of the managed proxy, a bug of Tor, or a misconfiguration. Please enable logging on your managed proxy and check the logs for errors.
My torrc config contains the following:
ServerTransportPlugin obfs3,scramblesuit exec /usr/bin/obfsproxy managed
Hm.
Can you make sure that obfsproxy is in /usr/bin/obfsproxy? Depending on how you installed obfsproxy-0.2.6, the executable might be in /usr/local/bin/ or elsewhere.
If that doesn't work, try this torrc line instead: ServerTransportPlugin obfs3,scramblesuit exec /usr/local/bin/obfsproxy --log-min-severity=debug --log-file=/home/user/obfs.log managed
this will turn on logging for obfsproxy and create a logfile in your home directory (fix the /home/user/obfs.log path). Please start up Tor again and check out the log file. If the log file doesn't get created it means that obfsproxy failed before writing the log file (this might be a permissions problem, or something else).
I was missing a package here (pyptlib) which I installed and now it appears to work
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Grozdan neutrino8@gmail.com writes:
On Mon, Feb 10, 2014 at 6:54 PM, George Kadianakis desnacked@riseup.net wrote:
Grozdan neutrino8@gmail.com writes:
On Mon, Feb 10, 2014 at 5:04 PM, George Kadianakis desnacked@riseup.net wrote:
Greetings,
a few days ago we integrated ScrambleSuit to obfsproxy. ScrambleSuit is a pluggable transport by Philipp Winter; you can find more about it at: http://www.cs.kau.se/philwint/scramblesuit/
If you are running a bridge, please consider upgrading your obfsproxy to the latest version (0.2.6) by using pip or fetching the latest git master. Unfortunately, we don't have Linux packages yet, but we will hopefully have some soon. In the meanwhile, we would appreciate some testing :)
After you upgrade obfsproxy, please change your ServerTransportPlugin line from: ServerTransportPlugin obfs2,obfs3 exec /usr/bin/obfsproxy managed to: ServerTransportPlugin obfs3,scramblesuit exec /usr/bin/obfsproxy managed
This will disable obfs2 [0] and enable scramblesuit.
It's also important to know that scramblesuit is a password-based pluggable transport, which means that each scramblesuit bridge has a password and if the user doesn't know the password he/she can't connect to the bridge. If you publishing your bridge to BridgeDB, Tor will automatically send the ScrambleSuit password to BridgeDB so that clients can get it. By default ScrambleSuit will generate a random password; if you want to specify your own password, you can use a torrc line like this: ServerTransportOptions scramblesuit password=LLDNOWV7I4P6RKFJMDEMIY2GNU2IQISA
By the way, expect not to see any scramblesuit users in the beginning. After a few people have set up scramblesuit bridges, we will roll out a Tor Browser Bundle with scramblesuit enabled.
Feel free to ask any questions you have!
I just installed version 0.2.6 and tried to make my normal bridge a bridge with obfsproxy, but it fails to start it. In Tor log all i see is the below
Feb 10 18:30:44.000 [warn] The communication stream of managed proxy '/usr/bin/obfsproxy' is 'closed'. Most probably the managed proxy stopped running. This might be a bug of the managed proxy, a bug of Tor, or a misconfiguration. Please enable logging on your managed proxy and check the logs for errors.
My torrc config contains the following:
ServerTransportPlugin obfs3,scramblesuit exec /usr/bin/obfsproxy managed
Hm.
Can you make sure that obfsproxy is in /usr/bin/obfsproxy? Depending on how you installed obfsproxy-0.2.6, the executable might be in /usr/local/bin/ or elsewhere.
If that doesn't work, try this torrc line instead: ServerTransportPlugin obfs3,scramblesuit exec /usr/local/bin/obfsproxy --log-min-severity=debug --log-file=/home/user/obfs.log managed
this will turn on logging for obfsproxy and create a logfile in your home directory (fix the /home/user/obfs.log path). Please start up Tor again and check out the log file. If the log file doesn't get created it means that obfsproxy failed before writing the log file (this might be a permissions problem, or something else).
I was missing a package here (pyptlib) which I installed and now it appears to work
Hm, out of curiosity, how did you install obfsproxy? Because if you used git, the setup.py script should have installed pyptlib for you. If you used pip, pip should have installed pyptlib for you.
Is there a bug somewhere?
On Mon, Feb 10, 2014 at 7:26 PM, George Kadianakis desnacked@riseup.net wrote:
Grozdan neutrino8@gmail.com writes:
On Mon, Feb 10, 2014 at 6:54 PM, George Kadianakis desnacked@riseup.net wrote:
Grozdan neutrino8@gmail.com writes:
On Mon, Feb 10, 2014 at 5:04 PM, George Kadianakis desnacked@riseup.net wrote:
Greetings,
a few days ago we integrated ScrambleSuit to obfsproxy. ScrambleSuit is a pluggable transport by Philipp Winter; you can find more about it at: http://www.cs.kau.se/philwint/scramblesuit/
If you are running a bridge, please consider upgrading your obfsproxy to the latest version (0.2.6) by using pip or fetching the latest git master. Unfortunately, we don't have Linux packages yet, but we will hopefully have some soon. In the meanwhile, we would appreciate some testing :)
After you upgrade obfsproxy, please change your ServerTransportPlugin line from: ServerTransportPlugin obfs2,obfs3 exec /usr/bin/obfsproxy managed to: ServerTransportPlugin obfs3,scramblesuit exec /usr/bin/obfsproxy managed
This will disable obfs2 [0] and enable scramblesuit.
It's also important to know that scramblesuit is a password-based pluggable transport, which means that each scramblesuit bridge has a password and if the user doesn't know the password he/she can't connect to the bridge. If you publishing your bridge to BridgeDB, Tor will automatically send the ScrambleSuit password to BridgeDB so that clients can get it. By default ScrambleSuit will generate a random password; if you want to specify your own password, you can use a torrc line like this: ServerTransportOptions scramblesuit password=LLDNOWV7I4P6RKFJMDEMIY2GNU2IQISA
By the way, expect not to see any scramblesuit users in the beginning. After a few people have set up scramblesuit bridges, we will roll out a Tor Browser Bundle with scramblesuit enabled.
Feel free to ask any questions you have!
I just installed version 0.2.6 and tried to make my normal bridge a bridge with obfsproxy, but it fails to start it. In Tor log all i see is the below
Feb 10 18:30:44.000 [warn] The communication stream of managed proxy '/usr/bin/obfsproxy' is 'closed'. Most probably the managed proxy stopped running. This might be a bug of the managed proxy, a bug of Tor, or a misconfiguration. Please enable logging on your managed proxy and check the logs for errors.
My torrc config contains the following:
ServerTransportPlugin obfs3,scramblesuit exec /usr/bin/obfsproxy managed
Hm.
Can you make sure that obfsproxy is in /usr/bin/obfsproxy? Depending on how you installed obfsproxy-0.2.6, the executable might be in /usr/local/bin/ or elsewhere.
If that doesn't work, try this torrc line instead: ServerTransportPlugin obfs3,scramblesuit exec /usr/local/bin/obfsproxy --log-min-severity=debug --log-file=/home/user/obfs.log managed
this will turn on logging for obfsproxy and create a logfile in your home directory (fix the /home/user/obfs.log path). Please start up Tor again and check out the log file. If the log file doesn't get created it means that obfsproxy failed before writing the log file (this might be a permissions problem, or something else).
I was missing a package here (pyptlib) which I installed and now it appears to work
Hm, out of curiosity, how did you install obfsproxy? Because if you used git, the setup.py script should have installed pyptlib for you. If you used pip, pip should have installed pyptlib for you.
I used git for both. after running setup.py install, it appears it wasn't successful. It installed the python scripts in /usr/bin but I had to manually copy the obfsproxy dir to /usr/lib/python-2.7/site-packages (else it complained about failed import of some scripts). I had to repeat the same for pyptlib
Is there a bug somewhere? _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Grozdan neutrino8@gmail.com writes:
On Mon, Feb 10, 2014 at 7:26 PM, George Kadianakis desnacked@riseup.net wrote:
Grozdan neutrino8@gmail.com writes:
On Mon, Feb 10, 2014 at 6:54 PM, George Kadianakis desnacked@riseup.net wrote:
Grozdan neutrino8@gmail.com writes:
On Mon, Feb 10, 2014 at 5:04 PM, George Kadianakis desnacked@riseup.net wrote:
Greetings,
<snip>
home directory (fix the /home/user/obfs.log path). Please start up Tor again and check out the log file. If the log file doesn't get created it means that obfsproxy failed before writing the log file (this might be a permissions problem, or something else).
I was missing a package here (pyptlib) which I installed and now it appears to work
Hm, out of curiosity, how did you install obfsproxy? Because if you used git, the setup.py script should have installed pyptlib for you. If you used pip, pip should have installed pyptlib for you.
I used git for both. after running setup.py install, it appears it wasn't successful. It installed the python scripts in /usr/bin but I had to manually copy the obfsproxy dir to /usr/lib/python-2.7/site-packages (else it complained about failed import of some scripts). I had to repeat the same for pyptlib
I see.
If you ever learn why setup.py failed, please tell me. :)
On 2014-02-10 19:26, George Kadianakis wrote:
Grozdan neutrino8@gmail.com writes:
On Mon, Feb 10, 2014 at 6:54 PM, George Kadianakis desnacked@riseup.net wrote:
Grozdan neutrino8@gmail.com writes:
On Mon, Feb 10, 2014 at 5:04 PM, George Kadianakis desnacked@riseup.net wrote:
Greetings,
a few days ago we integrated ScrambleSuit to obfsproxy. ScrambleSuit is a pluggable transport by Philipp Winter; you can find more about it at: http://www.cs.kau.se/philwint/scramblesuit/
If you are running a bridge, please consider upgrading your obfsproxy to the latest version (0.2.6) by using pip or fetching the latest git master. Unfortunately, we don't have Linux packages yet, but we will hopefully have some soon. In the meanwhile, we would appreciate some testing :)
After you upgrade obfsproxy, please change your ServerTransportPlugin line from: ServerTransportPlugin obfs2,obfs3 exec /usr/bin/obfsproxy managed to: ServerTransportPlugin obfs3,scramblesuit exec /usr/bin/obfsproxy managed
This will disable obfs2 [0] and enable scramblesuit.
It's also important to know that scramblesuit is a password-based pluggable transport, which means that each scramblesuit bridge has a password and if the user doesn't know the password he/she can't connect to the bridge. If you publishing your bridge to BridgeDB, Tor will automatically send the ScrambleSuit password to BridgeDB so that clients can get it. By default ScrambleSuit will generate a random password; if you want to specify your own password, you can use a torrc line like this: ServerTransportOptions scramblesuit password=LLDNOWV7I4P6RKFJMDEMIY2GNU2IQISA
By the way, expect not to see any scramblesuit users in the beginning. After a few people have set up scramblesuit bridges, we will roll out a Tor Browser Bundle with scramblesuit enabled.
Feel free to ask any questions you have!
I just installed version 0.2.6 and tried to make my normal bridge a bridge with obfsproxy, but it fails to start it. In Tor log all i see is the below
Feb 10 18:30:44.000 [warn] The communication stream of managed proxy '/usr/bin/obfsproxy' is 'closed'. Most probably the managed proxy stopped running. This might be a bug of the managed proxy, a bug of Tor, or a misconfiguration. Please enable logging on your managed proxy and check the logs for errors.
My torrc config contains the following:
ServerTransportPlugin obfs3,scramblesuit exec /usr/bin/obfsproxy managed
Hm.
Can you make sure that obfsproxy is in /usr/bin/obfsproxy? Depending on how you installed obfsproxy-0.2.6, the executable might be in /usr/local/bin/ or elsewhere.
If that doesn't work, try this torrc line instead: ServerTransportPlugin obfs3,scramblesuit exec /usr/local/bin/obfsproxy --log-min-severity=debug --log-file=/home/user/obfs.log managed
this will turn on logging for obfsproxy and create a logfile in your home directory (fix the /home/user/obfs.log path). Please start up Tor again and check out the log file. If the log file doesn't get created it means that obfsproxy failed before writing the log file (this might be a permissions problem, or something else).
I was missing a package here (pyptlib) which I installed and now it appears to work
Hm, out of curiosity, how did you install obfsproxy? Because if you used git, the setup.py script should have installed pyptlib for you. If you used pip, pip should have installed pyptlib for you.
Is there a bug somewhere?
I updated a minority of our bridges. Sadly I can't install them on all of our servers as most of our bridges a running in a KVM with minimal ressources (1 GB HDD Space).
Greetings Sam Grüneisen - FVDE (enn.lu)
George Kadianakis:
a few days ago we integrated ScrambleSuit to obfsproxy. ScrambleSuit is a pluggable transport by Philipp Winter; you can find more about it at: http://www.cs.kau.se/philwint/scramblesuit/
If you are running a bridge, please consider upgrading your obfsproxy to the latest version (0.2.6) by using pip or fetching the latest git master. Unfortunately, we don't have Linux packages yet, but we will hopefully have some soon. In the meanwhile, we would appreciate some testing :)
obfsproxy 0.2.6-1 has entered Debian unstable: http://packages.qa.debian.org/o/obfsproxy/news/20140210T183324Z.html
I also have sucessfully used the package on Wheezy systems.
George Kadianakis desnacked@riseup.net writes:
Greetings,
a few days ago we integrated ScrambleSuit to obfsproxy. ScrambleSuit is a pluggable transport by Philipp Winter; you can find more about it at: http://www.cs.kau.se/philwint/scramblesuit/
If you are running a bridge, please consider upgrading your obfsproxy to the latest version (0.2.6) by using pip or fetching the latest git master. Unfortunately, we don't have Linux packages yet, but we will hopefully have some soon. In the meanwhile, we would appreciate some testing :)
After you upgrade obfsproxy, please change your ServerTransportPlugin line from: ServerTransportPlugin obfs2,obfs3 exec /usr/bin/obfsproxy managed to: ServerTransportPlugin obfs3,scramblesuit exec /usr/bin/obfsproxy managed
This will disable obfs2 [0] and enable scramblesuit.
It's also important to know that scramblesuit is a password-based pluggable transport, which means that each scramblesuit bridge has a password and if the user doesn't know the password he/she can't connect to the bridge. If you publishing your bridge to BridgeDB, Tor will automatically send the ScrambleSuit password to BridgeDB so that clients can get it. By default ScrambleSuit will generate a random password; if you want to specify your own password, you can use a torrc line like this: ServerTransportOptions scramblesuit password=LLDNOWV7I4P6RKFJMDEMIY2GNU2IQISA
By the way, expect not to see any scramblesuit users in the beginning. After a few people have set up scramblesuit bridges, we will roll out a Tor Browser Bundle with scramblesuit enabled.
Feel free to ask any questions you have!
Thanks!
Hello people,
I forgot to mention that if you upgraded obfsproxy to support scramblesuit, you should also upgrade Tor to use a version fresher than 0.2.5.1. Otherwise scramblesuit will not function properly (even though it might seem like it does [0]).
I think currently the only way to get tor-0.2.5.1 is to use the git master. Feel free to ask any questions you have.
[0]: https://lists.torproject.org/pipermail/tor-dev/2014-February/006213.html
George Kadianakis:
I think currently the only way to get tor-0.2.5.1 is to use the git master. Feel free to ask any questions you have.
You are forgetting the automated Debian package builds (thanks weasel!).
Putting the following in /etc/apt/sources.list will do it:
deb http://deb.torproject.org/torproject.org tor-nightly-master-wheezy main
Replace “wheezy” by one of precise, quantal, raring, saucy, squeeze, jessie, sid depending on your distribution.
tor-relays@lists.torproject.org
-
George Kadianakis -
Grozdan -
Lunar -
Tyler Durden