Bitcoin Sign up or log in to customize your list._ Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top up vote 1 down vote favorite I'm trying to set up Armory with Tor by directing all Armory communications to port 9150 which is the one that I have been told my Tor browser uses.Before I start Armory or the Tor Browser, I activate bitcoind with the terminal command 'bitcoind -proxy=127.0.0.1:9150'.But when I then start Armory, it tells me that I must shut down this instance of the program and allow Armory to start it instead.OK, but there seems to be no way to inject the command line switches into the version Armory starts.If I disable the the Armory checkbox 'Let Armory run bitcoind in the background' then it does not give me that objection message but instead never goes online even if I have started bitcoind manually.There is another thread on this subject but, since I am new here, I don't know if I can just attach a new question to an old thread or must post a new one.

So, I decided to post a new one, sorry if that is not the correct procedure.And, to address the issue of a Wiki brought up in the older thread, the problem seems to keep changing because the functions of Armory and Tor keep changing.For instance, I can't run Vidalia on my system because I run Ubuntu 12.04 and Vidalia is not available for that version.I must run the Tor browser instead to get activation of the Tor network.So perhaps a Wiki would be good.armory tor up vote 1 down vote Having never tried this myself, I can't answer it with my own personal experience./index.php?topic=155717.0 That thread may answer your question, and if not, feel free to ask followup questions there.(There used to be a requirement to be in the newbie forum for a while, but this requirement has since been removed, so all you need to do is create an account on bitcointalk to post questions.)Your Answer Sign up or log in Sign up using Google Sign up using Email and Password Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for?Browse other questions tagged armory tor or ask your own question.Clone this wiki locally The following example security application ideas illustrate the flexibility of the USB armory concept: Hardware Security Module (HSM) file storage with advanced features such as automatic encryption, virus scanning, host authentication and data self-destruct OpenSSH client and agent for untrusted hosts (kiosk) router for end-to-end VPN tunnelling, Tor password manager with integrated web server electronic wallet (e.g.pocket Bitcoin wallet) authentication token portable penetration testing platform low level USB security testing This section is meant to track available software PoC, projects and/or procedures oriented towards implementing such application ideas and any other interesting USB armory usage.If you have tested an interesting use case for for inclusion.See also Host communication for interfacing options.

File encryption The INTERLOCK application is a file encryption front-end, with Signal messaging support, developed for, but not limited to, usage with the USB armory.A Buildroot environment is also available.Bitcoin wallet /) Bitcoin wallet works out of the box on the USB armory, it has been tested with X11 forwarding from Linux as well as Windows hosts.bitcoin etf reviewTor Anonymizing Middlebox Assumptions: host main interface on network 192.168.1.0/24 with default gateway 192.168.1.1 USB armory on network 10.0.0.0/24 with IP address 10.0.0.1 USB armory masqueraded and routed as described in Host communication USB armory setup Launch Tor with the following configuration (/etc/tor/torrc): VirtualAddrNetworkIPv4 10.192.0.0/10 AutomapHostsOnResolve 1 # Transparent proxy TransPort 9040 TransListenAddress 127.0.0.1 TransListenAddress 10.0.0.1 # DNS DNSPort 53 DNSListenAddress 127.0.0.1 DNSListenAddress 10.0.0.1 Launch the following script (based on Transparent Proxy Tor wiki page, IMPORTANT: change the _tor_uid variable accordingly): #!/bin/sh ### set variables #destinations you don't want routed through Tor _non_tor="10.0.0.0/24" #the UID that Tor runs as (varies from system to system) _tor_uid="104" #Tor's TransPort _trans_port="9040" #your internal interface _int_if="usb0" ### flush iptables iptables -F iptables -t nat -F ### set iptables *nat iptables -t nat -A OUTPUT -o lo -j RETURN iptables -t nat -A OUTPUT -m owner --uid-owner $_tor_uid -j RETURN iptables -t nat -A OUTPUT -p udp --dport 53 -j REDIRECT --to-ports 53 #allow clearnet access for hosts in $_non_tor for _clearnet in $_non_tor; do iptables -t nat -A OUTPUT -d $_clearnet -j RETURN iptables -t nat -A PREROUTING -i $_int_if -d $_clearnet -j RETURN done #redirect all other pre-routing and output to Tor iptables -t nat -A OUTPUT -p tcp --syn -j REDIRECT --to-ports $_trans_port iptables -t nat -A PREROUTING -i $_int_if -p udp --dport 53 -j REDIRECT --to-ports 53 iptables -t nat -A PREROUTING -i $_int_if -p tcp --syn -j REDIRECT --to-ports $_trans_port ### set iptables *filter iptables -A OUTPUT -m state --state ESTABLISHED,RELATED -j ACCEPT #allow clearnet access for hosts in $_non_tor for _clearnet in $_non_tor 127.0.0.0/8; do iptables -A OUTPUT -d $_clearnet -j ACCEPT done #allow only Tor output iptables -A OUTPUT -m owner --uid-owner $_tor_uid -j ACCEPT iptables -A OUTPUT -j REJECT Host setup Define the "rt_usbarmory" routing table identifier in /etc/iproute2/rt_tables: # # reserved values # 255 local 254 main 253 default 0 unspec # # local # #hep 1 rt_usbarmory Launch the following commands: # ip rule add from 10.0.0.1/32 table rt_usbarmory # ip route add default via 192.168.1.1 table rt_usbarmory # ip route del default # ip route add default via 10.0.0.1 A successful setup can be tested as follows: $ | grep -E "Sorry|Congratulations" Congratulations.bitcoin yearly return