Re: [tor-dev] Request for comments: patch to mark exit traffic for routing and statistical analysis

[teor]

> On 25 Oct. 2016, at 01:24, René Mayrhofer  wrote:
> 
> Am 20.10.2016 um 11:34 schrieb teor:
>> We generally track tor features using the Tor bug tracker:
>> https://trac.torproject.org/projects/tor/newticket
>> Use the Core Tor/Tor component.
>> 
>> We have found that gitlab is useful for making comments on patches.
>> But I am also happy to use GitHub, or any other system you would like.
>> 
>> If you're ok with it, I can set up a branch here on gitlab with your patch:
>> https://gitlab.com/teor/tor/merge_requests
> Certainly - we are in the process of setting up gitlab here for student
> projects, and will therefore use it anyways. Happy to coordinate that way.

Here is the existing enhancement request for this feature:
https://trac.torproject.org/projects/tor/ticket/17975

Tim

> 
> best regards,
> Rene
> ___
> tor-dev mailing list
> tor-dev@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

T

-- 
Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
--








___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

Re: [tor-dev] Call for help on testing core tor releases

[Vinícius Zavam]

2016-10-13 22:48 GMT-03:00, teor :
>
>> On 14 Oct 2016, at 08:03, blacklight .  wrote:
>>
>> I would love to help, but can you also volunteer when cannot give ALL the
>> feedback?
>
>> On 14 Oct 2016, at 11:30, ng0  wrote:
>>
>> Do all these task have to apply to make the test valid/useful for you?
>> On one of my test systems - I contribute to Guix - there is no chance of
>> a (system-specific, unofficial) torbrowser build so far (but I/we keep
>> looking into this).
>> So long story short, I can run tests on some amd64_x86 based
>> gnu-systems, but on one of them I need to exclude torbrowser.
>
> We only do source releases for tor alphas and release candidates.
> (Except for Debian, which has experimental alphas built nightly.)
>
> So you must build tor from source in order to run the tests.
>
> All the other tests are optional, but the more you can do, the better!
>
> If you can't build tor from source, you can still help by giving us
> feedback
> on the Tor Browser alpha series, or the Tor Expert Bundles on Windows.
>
> T
>
> --
> Tim Wilson-Brown (teor)

quick and dirty feedback; 6 relays running well 0.3.0.0-alpha-dev
(>=git-d1bcba19a9790a37) for quite a while (3 in dual stack). 4freebsd
and 2netbsd machines. 5static binary, 1shared (freebsd 10.3-R-p7,
i386).

every single relay that now is running -dev was running 0.2.9.4-alpha
since its release date (or one/two days after it was available on your
distfiles/archives ftp). I was following the releases available on the
ftp, not ports/pkg/pkgsrc/pkgin/... *EXCEPT* for one machine that runs
freebsd10.3r-p7 (i386); it was working good with 0.2.9.2-alpha only
(again, with shared libs).

sorry for not providing proper feedback or patch on Tor's trac. I plan
to do that ASAP.

PS: http://lists.nycbug.org/pipermail/tor-bsd/2016-October/000467.html
might be interesting for those running Tor (security/tor-devel) with
FreeBSD. ty.


-- 
Vinícius Zavam
keybase.io/egypcio/key.asc
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

Re: [tor-dev] handling TLS Session Ticket/Identifier for Android

[Tom Ritter]

The info I gave you was for Tor Browser, the the latter (about session
ID) is actually wrong. TBB disables both.

https://trac.torproject.org/projects/tor/ticket/20447#ticket
https://gitweb.torproject.org/tor-browser.git/tree/security/manager/ssl/nsNSSComponent.cpp?h=tor-browser-45.4.0esr-6.5-1#n724

Also: https://trac.torproject.org/projects/tor/ticket/4099

Core Tor also disables both also AFAICT:
https://gitweb.torproject.org/tor.git/commit/?id=8743080a289a20bfaf0a67d6382ba0c2a6d6534d
https://gitweb.torproject.org/tor.git/tree/src/common/tortls.c#n1164

-tom
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

[tor-dev] handling TLS Session Ticket/Identifier for Android

[Hans-Christoph Steiner]

Hey all,

Since tor devs have thought about how to handle TLS Session Tickets and
Identifiers, I want to capture that approach and stick it into our
NetCipher library, which is also used in Orfox.  As I understand it, the
approach is:

* disable TLS Session Tickets entirely
* reset TLS Session Identifiers on NEWNYM

Any plans to rethink this for TLS v1.3?  Any other TLS tracking issues I
should be addressing in NetCipher?  I'd also appreciate any references
on this topic (yes, I know how to find the relevant RFCs ;), like tor
trac tickets.  My searches have come up with very little.

.hc

-- 
PGP fingerprint: EE66 20C7 136B 0D2C 456C  0A4D E9E2 8DEA 00AA 5556
https://pgp.mit.edu/pks/lookup?op=vindex=0xE9E28DEA00AA5556
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

Re: [tor-dev] Request for comments: patch to mark exit traffic for routing and statistical analysis

[René Mayrhofer]

Am 20.10.2016 um 11:34 schrieb teor:
> We generally track tor features using the Tor bug tracker:
> https://trac.torproject.org/projects/tor/newticket
> Use the Core Tor/Tor component.
>
> We have found that gitlab is useful for making comments on patches.
> But I am also happy to use GitHub, or any other system you would like.
>
> If you're ok with it, I can set up a branch here on gitlab with your patch:
> https://gitlab.com/teor/tor/merge_requests
Certainly - we are in the process of setting up gitlab here for student
projects, and will therefore use it anyways. Happy to coordinate that way.

best regards,
Rene
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev