RationalSpeculator (OP)
Sr. Member
 Offline
Activity: 294
Merit: 250
This bull will try to shake you off. Hold tight!
|
 |
March 21, 2013, 02:10:50 AM |
|
When you create blockchain wallets through Tor and manage them only through Tor, I understood you are very anonymous. (ofcourse you need to make sure not to receive or send coins on that address that comes from people or companies that know who you are.)
But how do I achieve the same anonymity with Armory?
I'm not technically advanced but do I understand correctly that when using Armory it's comparable to using blockchain wallet via normal browser (ie: not very anonymous since your ip can be known)?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
"If you don't want people to know you're a scumbag then don't be a scumbag." -- margaritahuyan
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
Lethos
|
|
March 21, 2013, 02:34:06 AM |
|
From what I understand Armory, needs the standard bitcoin client to be running.
I could be wrong, but if that is running via Tor, it would also apply for Armory.
I've never tested it, I never considered trying to using it via Tor, but you have given me an idea to test it.
|
|
|
|
justusranvier
Legendary
Offline
Activity: 1400
Merit: 1009
|
|
March 21, 2013, 02:37:01 AM |
|
Armory uses bitcoin-qt to broadcast transactions for it, so if you've configured the standard client to connect via Tor then any transactions Armory creates will be anonymized.
|
|
|
|
|
RationalSpeculator (OP)
Sr. Member
Offline
Activity: 294
Merit: 250
This bull will try to shake you off. Hold tight!
|
|
March 21, 2013, 02:58:20 AM |
|
Armory uses bitcoin-qt to broadcast transactions for it, so if you've configured the standard client to connect via Tor then any transactions Armory creates will be anonymized.
Thanks a lot  |
|
|
|
|
RationalSpeculator (OP)
Sr. Member
Offline
Activity: 294
Merit: 250
This bull will try to shake you off. Hold tight!
|
|
March 21, 2013, 03:24:07 AM |
|
Armory uses bitcoin-qt to broadcast transactions for it, so if you've configured the standard client to connect via Tor then any transactions Armory creates will be anonymized.
I succeeded in connecting bitcoin-qt through the Tor network. But Armory opens in 'offline mode' because 'bitcoin-qt is not running'. However, bitcoin-qt is running and even shows the green checkmark and says it's connected via 8 active connections. Do you or anyone else have an idea how to solve this? |
|
|
|
|
|
Lethos
|
|
March 21, 2013, 11:52:31 AM |
|
That sounds like the same issue I had during testing.
I'm not sure if I set it up right.
|
|
|
|
|
ErebusBat
|
|
March 21, 2013, 12:07:31 PM |
|
You need to add listen=1 to your bitcoin.conf file.
Prudence would suggest that you make sure that other machines can't see your PC, but you should be behind a nat router anyway. Just disable a port forward if you have one.
|
|
|
|
|
Lethos
|
|
March 21, 2013, 01:42:17 PM |
|
Thanks for the Tip, it does indeed work now, with Armory.
|
|
|
|
etotheipi
Legendary
Offline
Activity: 1428
Merit: 1093
Core Armory Developer
|
|
April 02, 2013, 01:29:13 AM
Last edit: April 02, 2013, 02:06:04 AM by etotheipi |
|
So do I understand correctly that for people using proxies (mainly for Tor), you *may* have to do any of the following: - (1) Create a bitcoin.conf file with listen=1 (C:\Users\username\AppData\Roaming\Bitcoin\bitcoin.conf or /home/user/.bitcoin/bitcoin.conf)
- (2) Start Armory with --skip-online-check
- (3) In some cases, change the port that Armory connects to (usually 8333, might be 9050 with Tor)
Does this cover it? What else should I add to my list? |
|
|
|
RationalSpeculator (OP)
Sr. Member
Offline
Activity: 294
Merit: 250
This bull will try to shake you off. Hold tight!
|
|
April 04, 2013, 03:30:25 PM |
|
You need to add listen=1 to your bitcoin.conf file.
Prudence would suggest that you make sure that other machines can't see your PC, but you should be behind a nat router anyway. Just disable a port forward if you have one.
Thank you so much! That worked. Your second tip is chinese to me. How do I know that I am behind a nat router? I don't even know where to check that. Let alone disable a port forward. Do I have to somehow connect to my router, the box from my internet service provider? |
|
|
|
|
Bitcoinfly
Newbie
Offline
Activity: 30
Merit: 0
|
|
May 26, 2013, 10:58:06 AM |
|
So do I understand correctly that for people using proxies (mainly for Tor), you *may* have to do any of the following: - (1) Create a bitcoin.conf file with listen=1 (C:\Users\username\AppData\Roaming\Bitcoin\bitcoin.conf or /home/user/.bitcoin/bitcoin.conf)
- (2) Start Armory with --skip-online-check
- (3) In some cases, change the port that Armory connects to (usually 8333, might be 9050 with Tor)
Does this cover it? What else should I add to my list? Thanks, I did 1 and 2, seems 3 is must. But how can I change the port connection when don't see it in setting options? |
|
|
|
|
Bitcoinfly
Newbie
Offline
Activity: 30
Merit: 0
|
|
May 26, 2013, 11:18:23 AM |
|
Ah, figured it out. Seems it's running!
|
|
|
|
|
Rampion
Legendary
Offline
Activity: 1148
Merit: 1018
|
|
January 02, 2014, 10:22:30 AM |
|
You need to add listen=1 to your bitcoin.conf file.
Prudence would suggest that you make sure that other machines can't see your PC, but you should be behind a nat router anyway. Just disable a port forward if you have one.
Very sorry to necro this thread guys, but I just recently started to run Bitcoin-QT through Tor to protect myself especially while using public WIFIs, etc. and I had to add the listen=1 line to the bitcoin.conf file to get armory to work with it... Erebus, you say that "prudence would suggest that you make sure that other machines can't see your PC", but anyhow Bitcoin-QT listen to external connections by default unless a proxy (like Tor) is configured - right? Thus, adding listen=1 would just take Bitcoin-QT to its "default" behaviour regarding external connections... Did I get it right? |
|
|
|
goatpig
Moderator
Legendary
 Online
Activity: 3668
Merit: 1345
Armory Developer
|
|
January 04, 2014, 12:04:11 AM |
|
That's an interesting point. You should try bind=127.0.0.1 instead of listen=1
Also, I would personally use Tails rather than just Tor, to guaranty all traffic goes through Tor.
|
|
|
|
Rampion
Legendary
Offline
Activity: 1148
Merit: 1018
|
|
January 05, 2014, 05:13:38 PM
Last edit: January 05, 2014, 11:40:46 PM by Rampion |
|
That's an interesting point. You should try bind=127.0.0.1 instead of listen=1
Also, I would personally use Tails rather than just Tor, to guaranty all traffic goes through Tor.
Thanks for the advice, will try and report. Tails is indeed the best solution, but IMO its not really conceived as a fully persistent distro. It needs to be run from USB which makes it very impractical to run a full node as I do. Right now I use this solution when I want "full system going through tor": I route all my OS X traffic through tor using the Proxy settings on System Preferences/Advanced/Proxies. I've found it pretty good, meaning that everything really goes through Tor - to avoid any third party software "phoning home" without going through Tor I use Little Snitch, with which I block all connections that are not routed through Tor. Summing up: Tor proxy in advanced network settings + Little Snitch works very well on OS X. |
|
|
|
Rampion
Legendary
Offline
Activity: 1148
Merit: 1018
|
|
January 09, 2014, 08:08:51 PM |
|
The bind=127.0.0.1 thing did not work - the only way I've managed to run Bitcoin + armory + Tor is to start Bitcoin with the listen=1 argument.
|
|
|
|
goatpig
Moderator
Legendary
Online
Activity: 3668
Merit: 1345
Armory Developer
|
|
January 11, 2014, 04:05:52 AM |
|
The bind=127.0.0.1 thing did not work - the only way I've managed to run Bitcoin + armory + Tor is to start Bitcoin with the listen=1 argument.
Interesting, it works for me without using Tor. Try bind=localhost, maybe your host file resolves localhost to something else (IPv6?) |
|
|
|
TierNolan
Legendary
Offline
Activity: 1232
Merit: 1083
|
|
January 11, 2014, 07:43:38 PM |
|
I think bind=127.0.0.1 would have the added advantage that only local connections would be possible. External connections can't "see" localhost on another machine.
Activating listen mode would be required.
|
1LxbG5cKXzTwZg9mjL3gaRE835uNQEteWF
|
|
|
Rampion
Legendary
Offline
Activity: 1148
Merit: 1018
|
|
January 13, 2014, 11:30:59 AM |
|
I think bind=127.0.0.1 would have the added advantage that only local connections would be possible. External connections can't "see" localhost on another machine.
Activating listen mode would be required.
I tried bind=localhost and didn't work, Bitcoin-QT couldn't resolve it. Bind=127.0.0.1 didn't work for armory, but I tried it alone - maybe I have also to enable to listen=1 for bind=127.0.0.1 to work? Will try that... |
|
|
|
TierNolan
Legendary
Offline
Activity: 1232
Merit: 1083
|
|
January 13, 2014, 12:07:42 PM |
|
Bind=127.0.0.1 didn't work for armory, but I tried it alone - maybe I have also to enable to listen=1 for bind=127.0.0.1 to work? Will try that...
Bind = 127.0.0.1 should mean that only local processes can connect to your node. This means that you can use listen=1 without having to worry about incoming connections. You are guaranteed to have 8 outgoing connections and the 1 incoming connection from Armory. |
1LxbG5cKXzTwZg9mjL3gaRE835uNQEteWF
|
|
|
|
