[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [Fwd: High-traffic Colluding Tor Routers in Washington, D.C. Confirmed]



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> I would like to contribute some more Tor servers running at different
> providers across Germany (probably not in the same /16 network). My
> current server is a virtual server at 1blu that has a bandwidth of 931
> KB/s which makes it the 71st fastest Tor server in the network. Maybe
> other providers are even faster than 1blu. Just as a comparison: the
> fastest Tor server at the moment has 4533 KB/s.

Hi,

do you run a TOR server on a virtual server without connection faults?
A year ago, I tested a tor server on virtual hardware (Virtuozzo) and I
got many TCP connection faults in "/proc/user_beancounters".

Is a TOR server now ready to run with less then 1024 TCP connections?
Or do you have a virtual server, which does not have low limits for TCP
connections? In this case the offer of 1blu is very nice for TOR.

- - ----- Begin Off-Topic -------
I know, it is a Tor list. But please let me write this:
What do you think about a remailer (Mixmaster or Mixminion), something
like TOR for emails. Emails are more private than surfing in my opinion.
If you did have the power to admin a few tor server, you may run a
remailer too. It may share a server together with TOR. The traffic is
not very high: 5.000 mails per day. It uses at max. 16 TCP connections.
And it can act as a middle-man like TOR. For Mixmaster a working MTA
("exim4" or something else) is required, for a Mixminion middle-man nothing.

The size of the remailer networks decreases in the last 6 month down to
35 nodes for Mixminion and less than 30 nodes for Mixmaster. Hope, we
can stop this trend. Large networks for high anonymity are needed.

I am ready for help, if somebody needed any docs. (in German too)
- - ------ End Off-Topic ----------

Karsten N.
- ---------------
awxcnx@xxxxxx
0x1C10A42F
- - -------------


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iQEVAwUBRiYl2XneknocEKQvAQLHewgAkFpzpcZEExkJ/Eydxog9d6czGX9sPYFY
gFVJ32NXO/qNSQR1WQOYMBesjLhd9+DCOEYQ9tkJqBrCCoEQklRcihFMO+ttDHb4
M0Ktqhizi75VJo36IX0060f0GQ4tT184NdferpLicAOuiGGvOkGAqTSgXvEzWPE1
ExLz7vl9BgSqs4P+wddOr1VSK1stxEUE/vwcbTK01o+C0v6peYEG9fplQq4bw48Z
lplBH3Fb/7ASmwR9faVfYoi8gXqLDtnRC1kHK+H+/JzWRPGZU9BKAADmiw+0+kql
9i0iv1yoPb7OWLofBHnbjuyxHC7gTdMmUyLAgSaK/67uOtp6sdbQ1Q==
=8hj5
-----END PGP SIGNATURE-----