[tor-dev] botnets in tor

Hi everyone, am new and not very sure about rules here,hope its not off-topic. im master student researcher and i am working on botnet detection. it would be appreciated if anyone can help me with : I. anyway to detect botnet trafic out of normal tor traffic? II. is this solution possible to apply

Re: [tor-dev] Understanding bwauth data in Stem?

Hi there, On 21 Nov 2014, at 23:44, Damian Johnson wrote: >> In other words, if I sorted the descriptors by "measured" value, what would >> that order mean? > > I *think* that would be the ordering of 'relays who receive the most tor > client traffic due to having a more highly weighted heuristi

Re: [tor-dev] Understanding bwauth data in Stem?

Hi Anna. Glad you're interested in digging in to the directory authorities! This is certainly a space that could use some love. > I'm working off the "Votes by Bandwidth Authorities" example on the Stem > webpage > (https://stem.torproject.org/tutorials/examples/votes_by_bandwidth_authorities.htm

[tor-dev] Understanding bwauth data in Stem?

I'm trying to understand how the bandwidth authorities work, and reading the spec [0] got me only partway to an understanding, so I'm trying to use Stem to see what the bwauth measurements look like in practice. I'm working off the "Votes by Bandwidth Authorities" example on the Stem webpage [1].

Re: [tor-dev] New documentation for Tor Metrics website

Dear Dr. Loesing, I have a concern about the consensus_weight. The definition of it seems that the consensus_weight is a completely measured value by the authorities. However, from the Bandwidth Scanner Specification, if I understand correctly, it looks like a combination of observed bandwidth and

Re: [tor-dev] Using Shadow to increase agility of Sponsor R deliverables

> On Nov 21, 2014, at 1:06 PM, David Goulet wrote: > > On 21 Nov (12:59:43), Rob Jansen wrote: >> >>> On Nov 21, 2014, at 10:40 AM, David Goulet wrote: >>> >>> Please see https://trac.torproject.org/projects/tor/ticket/13802 about >>> the instrumentation part. We'll definitely have to talk mo

[tor-dev] New documentation for Tor Metrics website

Dear list, writing documentation is hard work. I'm sure you already knew that, but let me re-assure you that I now believe it, too. At least until I forget it again and carelessly start documenting something else that looks tiny and friendly and trivial to document. Anyway, I spent the last day

Re: [tor-dev] Using Shadow to increase agility of Sponsor R deliverables

On 21 Nov (12:59:43), Rob Jansen wrote: > > > On Nov 21, 2014, at 10:40 AM, David Goulet wrote: > > > > Please see https://trac.torproject.org/projects/tor/ticket/13802 about > > the instrumentation part. We'll definitely have to talk more on the > > integration of Shadow and a userspace tracer

Re: [tor-dev] Using Shadow to increase agility of Sponsor R deliverables

> On Nov 21, 2014, at 10:40 AM, David Goulet wrote: > > Please see https://trac.torproject.org/projects/tor/ticket/13802 about > the instrumentation part. We'll definitely have to talk more on the > integration of Shadow and a userspace tracer but of what I got from > Nick, it sounds totally doa

[tor-dev] Stem roadmap, and ideas for the interpreter?

Hi Nick. While sipping my morning coffee I just realized that you might not be aware of my sinister long schemes, and that might be to the detriment of us both. The roadmap I have for myself goes something like... Step 1: Write Stem so we have a well tested, stable controller library. (Done [1])

Re: [tor-dev] Using Shadow to increase agility of Sponsor R deliverables

On 21 Nov (10:14:23), Rob Jansen wrote: > > > On Nov 20, 2014, at 4:59 PM, David Goulet wrote: > > > > On 20 Nov (14:45:12), Rob Jansen wrote: > >> > >> Are there other HS performance improvements that we think may be ready by > >> January? > > > > > On my part, I have a chutney network with

Re: [tor-dev] Feedback on obfuscating hidden-service statistics

> Roger's branch was a PoC that wrote stats on the log file. I don't > think we have newer data than what is in #13192. It's unclear whether > the relays stopped collecting statistics, or they just haven't updated > the trac ticket. If we could check on that and get that data, that would be really

Re: [tor-dev] Feedback on obfuscating hidden-service statistics

> On Nov 21, 2014, at 9:39 AM, George Kadianakis wrote: > > I also believe that some of these extra stats (e.g. "How many > failures/anomalies do we observe?") should first be done on a privnet > instead of the real network. That can give us some preliminary > results, and then we can consider d

Re: [tor-dev] Using Shadow to increase agility of Sponsor R deliverables

> On Nov 20, 2014, at 4:59 PM, David Goulet wrote: > > On 20 Nov (14:45:12), Rob Jansen wrote: >> >> Are there other HS performance improvements that we think may be ready by >> January? > > On my part, I have a chutney network with an HS and clients that fetch > data on it. I'm currently wo

Re: [tor-dev] Feedback on obfuscating hidden-service statistics

"A. Johnson" writes: > A response to George’s comment: "The timeline here is that we are hoping the > proposal _and_ the > implementation to be ready by mid-December… I'm currently OK with the two > statistics in: > … I >

Re: [tor-dev] Feedback on obfuscating hidden-service statistics

A response to George’s comment: "The timeline here is that we are hoping the proposal _and_ the implementation to be ready by mid-December… I'm currently OK with the two statistics in: … I feel that any other statistics wil

Re: [tor-dev] Hidden Service authorization UI

On 09/11/14 12:50, George Kadianakis wrote: > Hidden Service authorization is a pretty obscure feature of HSes, that > can be quite useful for small-to-medium HSes. > > Basically, it allows client access control during the introduction > step. If the client doesn't prove itself, the Hidden Service

[tor-dev] torsocks-2.0: NetBSD mmap patch

Hi! Please apply the attached patch to fix torsocks-2.0 on NetBSD. Thanks, Thomas $NetBSD$ handle_mmap() is needed in order to correctly build torsocks. --- src/lib/syscall.c.orig 2014-08-11 16:44:46.0 + +++ src/lib/syscall.c @@ -68,7 +68,7 @@ static LIBC_CONNECT_RET_TYPE hand

[tor-dev] tor-0.2.5.10: weird test failure

Hi! I'm currently trying to update tor in pkgsrc (www.pkgsrc.org) to 0.2.5.10. When I run the self tests with 'make check', I see: .../work/tor-0.2.5.10> make check make check-TESTS check-local PASS: src/test/test make all-am