On 10/28/14, s7r wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Seth,
>
> Totally agree about undermining decentralization by having to trust a
> single provider. Nobody recommended that, the addresses were for
> informative purpose only, to be used in parallel with other nodes run
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Seth,
Totally agree about undermining decentralization by having to trust a
single provider. Nobody recommended that, the addresses were for
informative purpose only, to be used in parallel with other nodes run
by other operators / organizations. No u
s7r writes:
> All use Bitcoin default port 8333. These servers are up all the time
> and very fast.
>
> Hidden services are end-to-end encrypted so the risk of MITM between
> nodes does not exist. Also, if you run bitcoin in such a way with
> onlynet=tor enabled in config, nobody listening your w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here are some Bitcoin reliable nodes sponsored by Thomas (TheCthulhu)
accessible via Tor hidden services:
h2vlpudzphzqxutd.onion
sbow7bnje2f4gcvt.onion
dioq2yg3l5ptgpge.onion
All use Bitcoin default port 8333. These servers are up all the time
and
Here is my problem:
The network administrator of my job search the firewall's (squid) log for
anything strange, so when tor connects using a bridge, the firewall's log
show:
...
mail.google.com
www.frootvpn.com
23.54.23.32 <- bridge's ip
bits.wikimedia.org
startpage.com
...
I get the d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I didn't realise my nodes didn't allow the bitcoin port. I'll get
right on it.
Also, if anyone in the Tor community has spare capacity, you can also
setup a full bitcoin node on the same server you use as an
exit/relay/bridge and it doesn't take up a
On Thu, Oct 23, 2014 at 7:35 PM, Erik de Castro Lopo
wrote:
http://arxiv.org/pdf/1410.6079v1.pdf
> Could this situation be improved if people ran limited exit nodes that only
> alloed the bitcoin p2p protocol to exit? I for one don't have enough
There are about ten exit nodes that do only this
> On Fri, Oct 24, 2014 at 1:35 AM, Nathan Freitas wrote:
>> This means we can support SIP calling over Tor, video conference and
>> streaming, among other applications...
Tor as a client also needs support for inbound binds for some apps, at
least at the single per port level when interacting wi
On Fri, Oct 24, 2014 at 1:35 AM, Nathan Freitas wrote:
> Is there any reason we shouldn't consider supporting UDP over Tor with
> Orbot, by tunneling the packets using the combination of badvpn's
> tun2socks and udpgw ("udp gateway") feature?
There's no reason raw IP itself (any/none of its numbe
On Mon, Oct 27, 2014 at 09:48:55AM +0100, Gigi Bigio wrote:
> as far as I understand, recent Firefox releases do not support anymore
>Vidalia and its related possibility to browse anonymously. Though the
>"onion" button is still present on the top left corner, it will not work,
>as you know.
Vidal
registered user
bigi...@cheapnet.it
Dear Sirs,
as far as I understand, recent Firefox releases do not support anymore Vidalia
and its related possibility to browse anonymously. Though the "onion" button is
still present on the top left corner, it will not work, as you know.
The alternati
11 matches
Mail list logo
