On Thu, 11 Apr 2013 13:20:57 +
Andrew F wrote:
> When Tor sends out packets over the Tor network, are they always the same
> size? If not is there a max size?
>
> > ... I thought we were talking about exit
> > nodes that are run by people that are sniffing data.
> > Sure would be nice to i
Aaron, Do you know the answer or where I can find the information? a doc
file perhaps?
When Tor sends out packets over the Tor network, are they always the same
size? If not is there a max size?
thanks
On Thu, Apr 11, 2013 at 1:17 PM, Andrew F wrote:
> Aaron, thanks for clarification. I tho
Aaron, thanks for clarification. I thought we were talking about exit
nodes that are run by people that are sniffing data.
Sure would be nice to identify those exit nodes and deal with them.
On Wed, Apr 3, 2013 at 9:15 PM, Aaron wrote:
> On Mon, Apr 1, 2013 at 10:01 PM, Andrew F
> wrote:
> >
On Mon, Apr 1, 2013 at 10:01 PM, Andrew F wrote:
> Why kick of bad exits? If you identify an exit that is gathering data or
> manipulating data, then simply take them out of rotation and feed them
> false connections so that they stay on line and wast resources. Otherwise
> they will shut down a
Why kick of bad exits? If you identify an exit that is gathering data or
manipulating data, then simply take them out of rotation and feed them
false connections so that they stay on line and wast resources. Otherwise
they will shut down and be back up the same day.
If you can lead them on for a
On Sun, Mar 31, 2013 at 4:45 PM, Roc Admin wrote:
> I took another look at the OONI project. Although it's oriented towards
> ISPs etc, isn't this almost exactly what's needed - or at least a start?
> The tests for many of the items that Mike Perry identified in the spec are
> already there.
>
> h
I took another look at the OONI project. Although it's oriented towards
ISPs etc, isn't this almost exactly what's needed - or at least a start?
The tests for many of the items that Mike Perry identified in the spec are
already there.
https://gitweb.torproject.org/ooni-probe.git/blob/16ec7a88d426b
On Sat, Mar 30, 2013 at 4:18 PM, Roc Admin wrote:
>> Does this mean that you're planning to expand the SoaT codebase? Write
>> a revised version? If the project is going to be revived then it would
>> make sense for it to take advantage of one of our newer controller
>> libraries...
>
> Yeah the p
> Does this mean that you're planning to expand the SoaT codebase? Write
> a revised version? If the project is going to be revived then it would
> make sense for it to take advantage of one of our newer controller
> libraries...
Yeah the plan is to do a complete rerwrite of SoaT. That guy was a
b
Roc Admin, glad you're interested in bad relay detection!
> I'm working on an updated version of SnakesOnATor (SOAT) that was used
> to monitor the Tor network for bad exit nodes.
Does this mean that you're planning to expand the SoaT codebase? Write
a revised version? If the project is going to
On Sat, Mar 30, 2013 at 2:44 AM, Roc Admin wrote:
> I'm working on an updated version of SnakesOnATor (SOAT) that was used
> to monitor the Tor network for bad exit nodes.
Great! Is the source available anywhere?
> This is a similar
> function to InspectTor hosted on a .onion site but that page
I'm working on an updated version of SnakesOnATor (SOAT) that was used
to monitor the Tor network for bad exit nodes. This is a similar
function to InspectTor hosted on a .onion site but that page owner has
not been reachable and has not reached out to other Tor folk.
The main problem with InspecT
12 matches
Mail list logo
