On Wed, Dec 11, 2013 at 09:33:47PM +, George Kadianakis wrote:
> Do you agree with the changes? If yes, I will merge Ximin's patch for
> #10342, and you will have to update your transport codebase
> appropriately. Please let me know.
For the record, I'm OK with this and replied here:
https://t
Hello Philipp and David,
I'm sending you an email because you are the people who are currently
developing obfsproxy modules.
We are thinking of slightly changing the API of obfsproxy, so that it
becomes more friendly to transport authors (or at least we hope so).
Specifically, we are thinking of
As it currently is this suffers from something like the Byzantine
general's problem.
Attacks may be performed based on the fact that participants don't
necessarily transition between states at the same moment.
Error handling must be carefully considered and the SYNC round made
more robust to compen
Running "test --verbose util/logging/sigsafe_err" gives me an debug-assert in
write(STDERR_FILENO,...). Assert that failed is: "(_osfile(h) & FOPEN)"
Here's the call-stack in WinDbg:
MSVCR100D!_write+0x126
test!tor_log_err_sigsafe_write(char * s = 0x00707290 ".==
===
On Fri, 06 Dec 2013, Nicolas Vigier wrote:
> - a description or ticket number of bugs that you wish could have been
> detected earlier with automated tests
Mike and Georg started tagging tickets that are possible test cases with
keyword tbb-testcase:
https://trac.torproject.org/projects/tor/que
