 Show Posts
|
|
Pages: [1]
|
|
0.5 BTC, drop me a message.
|
|
|
|
Cool subscribing  |
|
|
|
I'm trying to cover all Tor related Darkcoin guides here. If anyone is interested. https://darkcointalk.org/threads/overview-tor-guides-for-darkcoin.4227/Including: - How to run Darkcoin with the Tor Browser Bundle
- How to run Darkcoin with Tor nodes connected only
- How to run a local Darkcoin Tor hidden service
- How to run a full Darkcoin Tor hidden service relay on a server
This is all work in progress. Comments welcome. |
|
|
|
Mirror of darkcoin tor docs in onion land: http://darkcoinie7ghp67.onion/tor.txtSource: https://raw.githubusercontent.com/darkcoin/darkcoin/master/doc/tor.mdTOR SUPPORT IN DARKCOIN
=======================
It is possible to run Darkcoin as a Tor hidden service, and connect to such services.
The following directions assume you have a Tor proxy running on port 9050. Many
distributions default to having a SOCKS proxy listening on port 9050, but others
may not. In particular, the Tor Browser Bundle defaults to listening on a random
port. See [Tor Project FAQ:TBBSocksPort](https://www.torproject.org/docs/faq.html.en#TBBSocksPort)
for how to properly configure Tor.
1. Run darkcoin behind a Tor proxy
----------------------------------
The first step is running Darkcoin behind a Tor proxy. This will already make all
outgoing connections be anonymized, but more is possible.
-socks=5 SOCKS5 supports connecting-to-hostname, which can be used instead
of doing a (leaking) local DNS lookup. SOCKS5 is the default,
but SOCKS4 does not support this. (SOCKS4a does, but isn't
implemented).
-proxy=ip:port Set the proxy server. If SOCKS5 is selected (default), this proxy
server will be used to try to reach .onion addresses as well.
-onion=ip:port Set the proxy server to use for tor hidden services. You do not
need to set this if it's the same as -proxy. You can use -noonion
to explicitly disable access to hidden service.
-listen When using -proxy, listening is disabled by default. If you want
to run a hidden service (see next section), you'll need to enable
it explicitly.
-connect=X When behind a Tor proxy, you can specify .onion addresses instead
-addnode=X of IP addresses or hostnames in these parameters. It requires
-seednode=X SOCKS5. In Tor mode, such addresses can also be exchanged with
other P2P nodes.
-onlynet=tor Only connect to .onion nodes and drop IPv4/6 connections.
An example how to start the client if the Tor proxy is running on local host on
port 9050 and only allows .onion nodes to connect:
./darkcoind -onion=127.0.0.1:9050 -onlynet=tor -listen=0 -addnode=ssapp53tmftyjmjb.onion
In a typical situation, this suffices to run behind a Tor proxy:
./darkcoind -proxy=127.0.0.1:9050
2. Run a darkcoin hidden server
-------------------------------
If you configure your Tor system accordingly, it is possible to make your node also
reachable from the Tor network. Add these lines to your /etc/tor/torrc (or equivalent
config file):
HiddenServiceDir /var/lib/tor/darkcoin-service/
HiddenServicePort 9999 127.0.0.1:9999
HiddenServicePort 19999 127.0.0.1:19999
The directory can be different of course, but (both) port numbers should be equal to
your darkcoind's P2P listen port (9999 by default).
-externalip=X You can tell darkcoin about its publicly reachable address using
this option, and this can be a .onion address. Given the above
configuration, you can find your onion address in
/var/lib/tor/darkcoin-service/hostname. Onion addresses are given
preference for your node to advertize itself with, for connections
coming from unroutable addresses (such as 127.0.0.1, where the
Tor proxy typically runs).
-listen You'll need to enable listening for incoming connections, as this
is off by default behind a proxy.
-discover When -externalip is specified, no attempt is made to discover local
IPv4 or IPv6 addresses. If you want to run a dual stack, reachable
from both Tor and IPv4 (or IPv6), you'll need to either pass your
other addresses using -externalip, or explicitly enable -discover.
Note that both addresses of a dual-stack system may be easily
linkable using traffic analysis.
In a typical situation, where you're only reachable via Tor, this should suffice:
./darkcoind -proxy=127.0.0.1:9050 -externalip=ssapp53tmftyjmjb.onion -listen
(obviously, replace the Onion address with your own). If you don't care too much
about hiding your node, and want to be reachable on IPv4 as well, additionally
specify:
./darkcoind ... -discover
and open port 9999 on your firewall (or use -upnp).
If you only want to use Tor to reach onion addresses, but not use it as a proxy
for normal IPv4/IPv6 communication, use:
./darkcoind -onion=127.0.0.1:9050 -externalip=ssapp53tmftyjmjb.onion -discover
3. List of known darkcoin Tor relays
------------------------------------
* [darkcoinie7ghp67.onion](http://darkcoinie7ghp67.onion/)
* [drktalkwaybgxnoq.onion](http://drktalkwaybgxnoq.onion/)
* [ssapp53tmftyjmjb.onion](http://ssapp53tmftyjmjb.onion/)
|
|
|
|
Mirror of darkcoin tor docs in onion land: http://darkcoinie7ghp67.onion/tor.txtSource: https://raw.githubusercontent.com/darkcoin/darkcoin/master/doc/tor.mdTOR SUPPORT IN DARKCOIN
=======================
It is possible to run Darkcoin as a Tor hidden service, and connect to such services.
The following directions assume you have a Tor proxy running on port 9050. Many
distributions default to having a SOCKS proxy listening on port 9050, but others
may not. In particular, the Tor Browser Bundle defaults to listening on a random
port. See [Tor Project FAQ:TBBSocksPort](https://www.torproject.org/docs/faq.html.en#TBBSocksPort)
for how to properly configure Tor.
1. Run darkcoin behind a Tor proxy
----------------------------------
The first step is running Darkcoin behind a Tor proxy. This will already make all
outgoing connections be anonymized, but more is possible.
-socks=5 SOCKS5 supports connecting-to-hostname, which can be used instead
of doing a (leaking) local DNS lookup. SOCKS5 is the default,
but SOCKS4 does not support this. (SOCKS4a does, but isn't
implemented).
-proxy=ip:port Set the proxy server. If SOCKS5 is selected (default), this proxy
server will be used to try to reach .onion addresses as well.
-onion=ip:port Set the proxy server to use for tor hidden services. You do not
need to set this if it's the same as -proxy. You can use -noonion
to explicitly disable access to hidden service.
-listen When using -proxy, listening is disabled by default. If you want
to run a hidden service (see next section), you'll need to enable
it explicitly.
-connect=X When behind a Tor proxy, you can specify .onion addresses instead
-addnode=X of IP addresses or hostnames in these parameters. It requires
-seednode=X SOCKS5. In Tor mode, such addresses can also be exchanged with
other P2P nodes.
-onlynet=tor Only connect to .onion nodes and drop IPv4/6 connections.
An example how to start the client if the Tor proxy is running on local host on
port 9050 and only allows .onion nodes to connect:
./darkcoind -onion=127.0.0.1:9050 -onlynet=tor -listen=0 -addnode=ssapp53tmftyjmjb.onion
In a typical situation, this suffices to run behind a Tor proxy:
./darkcoind -proxy=127.0.0.1:9050
2. Run a darkcoin hidden server
-------------------------------
If you configure your Tor system accordingly, it is possible to make your node also
reachable from the Tor network. Add these lines to your /etc/tor/torrc (or equivalent
config file):
HiddenServiceDir /var/lib/tor/darkcoin-service/
HiddenServicePort 9999 127.0.0.1:9999
HiddenServicePort 19999 127.0.0.1:19999
The directory can be different of course, but (both) port numbers should be equal to
your darkcoind's P2P listen port (9999 by default).
-externalip=X You can tell darkcoin about its publicly reachable address using
this option, and this can be a .onion address. Given the above
configuration, you can find your onion address in
/var/lib/tor/darkcoin-service/hostname. Onion addresses are given
preference for your node to advertize itself with, for connections
coming from unroutable addresses (such as 127.0.0.1, where the
Tor proxy typically runs).
-listen You'll need to enable listening for incoming connections, as this
is off by default behind a proxy.
-discover When -externalip is specified, no attempt is made to discover local
IPv4 or IPv6 addresses. If you want to run a dual stack, reachable
from both Tor and IPv4 (or IPv6), you'll need to either pass your
other addresses using -externalip, or explicitly enable -discover.
Note that both addresses of a dual-stack system may be easily
linkable using traffic analysis.
In a typical situation, where you're only reachable via Tor, this should suffice:
./darkcoind -proxy=127.0.0.1:9050 -externalip=ssapp53tmftyjmjb.onion -listen
(obviously, replace the Onion address with your own). If you don't care too much
about hiding your node, and want to be reachable on IPv4 as well, additionally
specify:
./darkcoind ... -discover
and open port 9999 on your firewall (or use -upnp).
If you only want to use Tor to reach onion addresses, but not use it as a proxy
for normal IPv4/IPv6 communication, use:
./darkcoind -onion=127.0.0.1:9050 -externalip=ssapp53tmftyjmjb.onion -discover
3. List of known darkcoin Tor relays
------------------------------------
* [darkcoinie7ghp67.onion](http://darkcoinie7ghp67.onion/)
* [drktalkwaybgxnoq.onion](http://drktalkwaybgxnoq.onion/)
* [ssapp53tmftyjmjb.onion](http://ssapp53tmftyjmjb.onion/)
|
|
|
|
So, I have set-up 2 DarkCoin nodes which are running as dual stack i.e. they have connectivity through Tor as well as through the clear (regular) internet. *snip* addnode=33rkrxcfoeduijtb.onion
addnode=hgyvmhd7p2ihasu2.onion
*snip* Hi BitcoinFX, are you still running onion nodes for Darkcoin? Just curious. I couldnt connect to yours. Here are mine: addnode=darkcoinie7ghp67.onion
addnode=ssapp53tmftyjmjb.onion
No sorry. They are down at the moment. I had to cancel the vps hosting account(s) that they were running on. Due to the DRK price being low and with a lack of revenue from the web proxy sites to support the service I could not keep them running at present. I have the keys backed up for the .onion addresses and will look to reinstate the nodes in the future perhaps. I'm operating a darkcoin tor relay, in case anyone needs an addnode. http://darkcoinie7ghp67.onion/An example how to start the client if the Tor proxy is running on local host on port 9050 and only allows .onion nodes to connect: darkcoin-qt -onion=127.0.0.1:9050 -onlynet=tor -listen=0 -addnode=darkcoinie7ghp67.onion Thanks cyrus for sponsoring the node! http://cyruservvvklto2l.onion/blogs/cyrus/onion-darkcoin-node-sponsored-127DCT https://darkcointalk.org/threads/darkcoin-tor-relay.4175/HUB http://thehub7gqe43miyc.onion/index.php?topic=7161.0I also updated the darkcoin docs accordingly. https://github.com/darkcoin/darkcoin/pull/214If you have the resources, please run your own tor relay and publish the address! Has anyone tested instantX using the qt this way? Only tested darksend mixing yet - and that works well. Not sure whether IX is really important over tor, but will test how it works out and report back. v . ._, |_ .,
`-._\/ . \ / |/_
\\ _\, y | \//
_\_.___\\, \\/ -.\||
`7-,--.`._|| / / , /_
/' `-. `./ / |/_.' /( \
| |// \ ` |
|_ / `._|
|- |
| =|
| |
''''''''''''',,,,,,,/ ,,,. \,,,,,,,___
' ` `--._
`. ,-.
I love `. / `'
\, darkcoin. Me too. `.
` , `.
OO ~.. `.
.\\. .77. `.
,/ bb \\ `-.
`-.
`-.
., `--._
`-
\'' |
|
|
|
So, I have set-up 2 DarkCoin nodes which are running as dual stack i.e. they have connectivity through Tor as well as through the clear (regular) internet. *snip* addnode=33rkrxcfoeduijtb.onion
addnode=hgyvmhd7p2ihasu2.onion
*snip* Hi BitcoinFX, are you still running onion nodes for Darkcoin? Just curious. I couldnt connect to yours. Here are mine: addnode=darkcoinie7ghp67.onion
addnode=ssapp53tmftyjmjb.onion
No sorry. They are down at the moment. I had to cancel the vps hosting account(s) that they were running on. Due to the DRK price being low and with a lack of revenue from the web proxy sites to support the service I could not keep them running at present. I have the keys backed up for the .onion addresses and will look to reinstate the nodes in the future perhaps. I'm operating a darkcoin tor relay, in case anyone needs an addnode. http://darkcoinie7ghp67.onion/An example how to start the client if the Tor proxy is running on local host on port 9050 and only allows .onion nodes to connect: darkcoin-qt -onion=127.0.0.1:9050 -onlynet=tor -listen=0 -addnode=darkcoinie7ghp67.onion Thanks cyrus for sponsoring the node! http://cyruservvvklto2l.onion/blogs/cyrus/onion-darkcoin-node-sponsored-127DCT https://darkcointalk.org/threads/darkcoin-tor-relay.4175/HUB http://thehub7gqe43miyc.onion/index.php?topic=7161.0I also updated the darkcoin docs accordingly. https://github.com/darkcoin/darkcoin/pull/214If you have the resources, please run your own tor relay and publish the address! |
|
|
|
So, I have set-up 2 DarkCoin nodes which are running as dual stack i.e. they have connectivity through Tor as well as through the clear (regular) internet. *snip* addnode=33rkrxcfoeduijtb.onion
addnode=hgyvmhd7p2ihasu2.onion
*snip* Hi BitcoinFX, are you still running onion nodes for Darkcoin? Just curious. I couldnt connect to yours. Here are mine: addnode=darkcoinie7ghp67.onion
addnode=ssapp53tmftyjmjb.onion
|
|
|
|
|
