28.02.2014 09:53, Yawning Angel:
2.2. Tor Extended SOCKS5 Reply Codes
We introduce the following additional SOCKS5 reply codes to be sent
in the REP field of a SOCKS5 message. Implementations MUST NOT
send any of the extended codes unless the initiator has indicated
that it understands the
On 28 Feb (22:19:39), Roger Dingledine wrote:
On Wed, Feb 26, 2014 at 02:06:25PM +0100, Jeroen Massar wrote:
On 2014-02-26 13:46, Jacob Appelbaum wrote:
I think this is a fine idea - if no one objects, I'll purge it.
No objection per-se, but a recommendation/check-up:
Sounds great to
Hartmut Prochaska:
I changed a function in sandbox.c to not use a goto statement. I didn't
understood what use it had. Attached the patch file.
See https://www.kernel.org/doc/Documentation/CodingStyle, Chapter 7,
“Centralized exiting of functions” for a rationale.
--
Lunar
Hi,
I second Abhiram's opinion, let's see if this comes in handy. Thanks for the
tip, anyway!
Lukas, if you're interested, we generally meet in #tor-dev Wednesdays, 18:00
UTC. Come join in if you want to, we generally talk about what we worked on and
what the next steps are. Feel free to
I met today with some developers of Lantern (https://getlantern.org/,
https://github.com/getlantern/lantern). Lantern acts as an HTTP proxy
and proxies your traffic through trusted friends. We found that we had
the pieces necessary to make Lantern a pluggable transport of Tor; that
is, use Lantern
Hello all,
I have a new release candidate of obfsclient available now.
Notable changes since 0.0.1rc1:
* Use OpenSSL's CSPRNG instead of arc4random rng from libevent
* Use a CTR_DRBG instead of WELL512
* ScrambleSuit session tickets saved to disk also include a timestamp
* ScrambleSuit is
It was great meeting everyone in Reykjavík! February largely went toward GSoC
prep. Thanks to everybody that sent me project ideas!
https://blog.torproject.org/blog/tor-google-summer-code-2014
This left a lot less time than I'd like for coding. The only noteworthy
changes this month were...
*
