> 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
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?
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#n72
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 Ide
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 an
