Re: I exclude all bloxortsipt nodes in my tor use

2010-01-04 Thread Olaf Selke 
Roger Dingledine schrieb:
 
 You might instead ask about blutmagie, which at an advertised 41200 KB
 is 3% of the Tor network.

I'm pushing hard with all kind of gcc/icc compiler optimizations but at
about 170 MBit/s throughput the E8600 cpu is running at its limits.
Unfortunately server bios doesn't come up with overclocking features.

Nevertheless I catch Roger's point. Is it a good idea exiting so
much/many (never really understood the difference ;-)) tor traffic thru
one exit gw? If it is not, I'm certainly going to reduce exit capacity
by torrc config.

https://torstatus.blutmagie.de/index.php?SR=BandwidthSO=Desc

Olaf
***
To unsubscribe, send an e-mail to majord...@torproject.org with
unsubscribe or-talkin the body. http://archives.seul.org/or/talk/

Re: I exclude all bloxortsipt nodes in my tor use

2009-12-05 Thread Roger Dingledine 
On Fri, Dec 04, 2009 at 12:18:39PM -0500, swinglowswingh...@safe-mail.net wrote:
 all bloxortsipt## nodes, filling their entries with odd names within the 
 downloaded descriptors files.
 
 And just what is that person doing running that large number of (stupidly 
 named) Tor nodes?
 
 A.) Helping us all, because he loves us all so dearly
 B.) Some type of Tor study, which almost always invovles breaking it,
 more often than not at some college(s)

Indeed.

 I don't know about you all, but I don't want anyone seeing that large
of a percent of my total Tor traffic.

I've been keeping an eye on the bloxortsipt nodes off and on.

Looking at my cached-consensus file, there are 7 of them running currently
(2 of which are offering 0 bandwidth so clients will mostly ignore
them). Of those 5, they're offering a total bandwidth of 102 KB.

The total bandwidth mentioned in cached-consensus is 1354016 KB.

So that large of a percent of my total Tor traffic is in this
case 102/1354016 = .0075% of the Tor network.

You might instead ask about blutmagie, which at an advertised 41200 KB
is 3% of the Tor network.

The other thing to note is that none of the bloxortsipt nodes have either
the Exit or the Guard flag. So for normal circuits, they're never going
to see you or your destinations.

So I'm going to go with Helping us all, because he loves us all so
dearly.

 If they did fix the Family line,
what's the point in running so many nodes?

What's wrong with the Family line? It's long, but it looks well-formed
to me.

 They're not normal Tor nodes,
something odd is going on that I don't know fully about.

Yep.

 This alone is
enough for me to Exclude

I think this is a bad idea. Whenever your behavior is different from
the hundreds of thousands of other Tor users, you stand out and open
up ways that an attacker can recognize you. In this case the difference
in behavior is trivial, so not a big deal. But still it's something to
think harder about.

Rather than just excluding them and hoping that doesn't burn you, why
not contact him and ask what's up? Perhaps he's bundled a Tor relay with
some other software or hardware he maintains.

--Roger

***
To unsubscribe, send an e-mail to majord...@torproject.org with
unsubscribe or-talkin the body. http://archives.seul.org/or/talk/

I exclude all bloxortsipt nodes in my tor use

2009-12-04 Thread swinglowswinghigh 
Weird shit:

bloxortsipt
supp...@truxton.com
74.240.51.79
74.238.241.32
74.238.240.47
69.40.11.93
68.90.41.105
64.90.29.217
209.169.89.26
(and other IPs)

here's a snippet of the garbage:

family $43B6440D38F8E366EC8E06ADC7DD3B2503A1470A 
$571880416AE63A5072CAB7A1EC463CE637D4A29F 
$B25E88D8429FDF84370C6F276ABC0B73B61F1505 
$CDFE7F8DE3753F9FA593D3C2AEF5FF4F183D926C 
$D5DB86D4372C51950F82BF25920076B836DB9540 bloxortsipt1 bloxortsipt10 
bloxortsipt100 bloxortsipt101 bloxortsipt102 bloxortsipt103 bloxortsipt104 
bloxortsipt105 bloxortsipt106 bloxortsipt107 bloxortsipt108 bloxortsipt109 
bloxortsipt11 bloxortsipt110 bloxortsipt111 bloxortsipt112 bloxortsipt113 
bloxortsipt114 bloxortsipt115 bloxortsipt116 bloxortsipt117 bloxortsipt118 
bloxortsipt119 bloxortsipt12 bloxortsipt120 bloxortsipt121 bloxortsipt122 
bloxortsipt123 bloxortsipt124 bloxortsipt125 bloxortsipt126 bloxortsipt127 
bloxortsipt128 bloxortsipt129 bloxortsipt13 bloxortsipt130 bloxortsipt131 
bloxortsipt132 bloxortsipt133 bloxortsipt134 bloxortsipt135 bloxortsipt136 
bloxortsipt137 bloxortsipt138 bloxortsipt139 bloxortsipt14 bloxortsipt140 
bloxortsipt141 bloxortsipt142 bloxortsipt143 bloxortsipt144 bloxortsipt145 
bloxortsipt146 bloxortsipt147 bloxortsipt148 bloxortsipt149 bloxortsipt15 
bloxortsipt150 bloxortsipt151 bloxortsipt152 bloxortsipt153 bloxortsipt154 
bloxortsipt155 bloxortsipt156 bloxortsipt157 bloxortsipt158 bloxortsipt159 
bloxortsipt16 bloxortsipt160 bloxortsipt161 bloxortsipt162 bloxortsipt163 
bloxortsipt164 bloxortsipt165 bloxortsipt166 bloxortsipt167 bloxortsipt168 
bloxortsipt169 bloxortsipt17 bloxortsipt170 bloxortsipt171 bloxortsipt172 
bloxortsipt173 bloxortsipt174 bloxortsipt175 bloxortsipt176 bloxortsipt177 
bloxortsipt178 bloxortsipt179 bloxortsipt18 bloxortsipt180 bloxortsipt181 
bloxortsipt182 bloxortsipt183 bloxortsipt184 bloxortsipt185 bloxortsipt186 
bloxortsipt187 bloxortsipt188 bloxortsipt189 bloxortsipt19 bloxortsipt190 
bloxortsipt191 bloxortsipt192 bloxortsipt193 bloxortsipt194 bloxortsipt195 
bloxortsipt196 bloxortsipt197 bloxortsipt198 bloxortsipt199 bloxortsipt2 
bloxortsipt20 bloxortsipt200 bloxortsipt21 bloxortsipt22 bloxortsipt23 
bloxortsipt24 bloxortsipt25 bloxortsipt26 bloxortsipt27 bloxortsipt28 
bloxortsipt29 bloxortsipt31 bloxortsipt32 bloxortsipt33 bloxortsipt34 
bloxortsipt35 bloxortsipt36 bloxortsipt37 bloxortsipt39 bloxortsipt4 
bloxortsipt41 bloxortsipt42 bloxortsipt43 bloxortsipt44 bloxortsipt45 
bloxortsipt46 bloxortsipt47 bloxortsipt48 bloxortsipt49 bloxortsipt5 
bloxortsipt50 bloxortsipt51 bloxortsipt52 bloxortsipt53 bloxortsipt54 
bloxortsipt55 bloxortsipt56 bloxortsipt57 bloxortsipt59 bloxortsipt6 
bloxortsipt60 bloxortsipt61 bloxortsipt62 bloxortsipt63 bloxortsipt64 
bloxortsipt65 bloxortsipt66 bloxortsipt67 bloxortsipt68 bloxortsipt69 
bloxortsipt7 bloxortsipt70 bloxortsipt72 bloxortsipt73 bloxortsipt74 
bloxortsipt75 bloxortsipt76 bloxortsipt77 bloxortsipt78 bloxortsipt79 
bloxortsipt8 bloxortsipt80 bloxortsipt81 bloxortsipt82 bloxortsipt83 
bloxortsipt84 bloxortsipt85 bloxortsipt86 bloxortsipt87 bloxortsipt88 
bloxortsipt89 bloxortsipt9 bloxortsipt90 bloxortsipt91 bloxortsipt92 
bloxortsipt93 bloxortsipt94 bloxortsipt95 bloxortsipt96 bloxortsipt97 
bloxortsipt98 bloxortsipt99

all bloxortsipt## nodes, filling their entries with odd names within the 
downloaded descriptors files.

And just what is that person doing running that large number of (stupidly 
named) Tor nodes?

A.) Helping us all, because he loves us all so dearly
B.) Some type of Tor study, which almost always invovles breaking it,
more often than not at some college(s)

I don't know about you all, but I don't want anyone seeing that large of a 
percent of my total Tor traffic. If they did fix the Family line, what's the 
point in running so many nodes? They're not normal Tor nodes, something odd is 
going on that I don't know fully about. This alone is enough for me to Exclude 
(if it works this time, unlike on the Washington DC PSI nodes which 
mysteriously get around that and fill my firewall logs every time I run 
Tor).

I mean, C'mon, some 200 nodes and nothing fishy is going on? Suure. Here's 
a little help bloxor'ing him:

ExcludeNodes bloxortsipt1, bloxortsipt10, bloxortsipt100, bloxortsipt101, 
bloxortsipt102, bloxortsipt103, bloxortsipt104, bloxortsipt105, bloxortsipt106, 
bloxortsipt107, bloxortsipt108, bloxortsipt109, bloxortsipt11, bloxortsipt110, 
bloxortsipt111, bloxortsipt112, bloxortsipt113, bloxortsipt114, bloxortsipt115, 
bloxortsipt116, bloxortsipt117, bloxortsipt118, bloxortsipt119, bloxortsipt12, 
bloxortsipt120, bloxortsipt121, bloxortsipt122, bloxortsipt123, bloxortsipt124, 
bloxortsipt125, bloxortsipt126, bloxortsipt127, bloxortsipt128, bloxortsipt129, 
bloxortsipt13, bloxortsipt130, bloxortsipt131, bloxortsipt132, bloxortsipt133, 
bloxortsipt134, bloxortsipt135, bloxortsipt136, bloxortsipt137, bloxortsipt138, 
bloxortsipt139, bloxortsipt14, bloxortsipt140, bloxortsipt141, bloxortsipt142,

Re: I exclude all bloxortsipt nodes in my tor use

2009-12-04 Thread Brian Mearns 
2009/12/4  swinglowswingh...@safe-mail.net:
 Weird shit:

 bloxortsipt
 supp...@truxton.com
 74.240.51.79
 74.238.241.32
 74.238.240.47
 69.40.11.93
 68.90.41.105
 64.90.29.217
 209.169.89.26
 (and other IPs)

[snip]

Did you try emailing supp...@truxton.com, find out what the deal is?

-- 
Feel free to contact me using PGP Encryption:
Key Id: 0x3AA70848
Available from: http://keys.gnupg.net
***
To unsubscribe, send an e-mail to majord...@torproject.org with
unsubscribe or-talkin the body. http://archives.seul.org/or/talk/

Re: I exclude all bloxortsipt nodes in my tor use

2009-12-04 Thread Andrew Lewman 
On 12/04/2009 12:18 PM, swinglowswingh...@safe-mail.net wrote:
 Weird shit:
 
 bloxortsipt
 supp...@truxton.com

http://archives.seul.org/or/talk/Jul-2009/msg00376.html

Someone should post that to onionforum.

-- 
Andrew Lewman
The Tor Project
pgp 0x31B0974B

Website: https://torproject.org/
Blog: https://blog.torproject.org/
Identi.ca: torproject
***
To unsubscribe, send an e-mail to majord...@torproject.org with
unsubscribe or-talkin the body. http://archives.seul.org/or/talk/