Hi all. Here's a proposal for ticket #5548. Let's discuss!
Filename: 203-https-frontend.txt
Title: Avoiding censorship by impersonating an HTTPS server
Author: Nick Mathewson
Created: 24 Jun 2012
Status: Draft
Overview:
One frequently proposed approach for censorship resistance is that
Hi Damian,
Megan and I have finished a first run at writing unit tests for the proc
utilities in stem. The code may be found on Megan's Github at:
https://github.com/meganchang/Stem/blob/proc-tests/test/unit/util/proc.py.
Until we hear back on a code review, we'll move on to the integration
tests
> OpenSSL 1.0.1c has been build with:
> ./Configure debian-mipsel shared enable-tlsext zlib-dynamic no-ssl2
I've never been able to compile openssl statically such that I could use
the resultant binary, dynlib and statlib it everywhere needed. Nor does
zlib play right in that. More on the ssl mail
Strange it happens all the time with OpenSSL 1.0.1c
Even with the non-debian version.
I tried the vanilla OpenSSL with only the patch for "linux-mipsel" in
Configure.
When it performs it's handshake it will still spawn the message:
Jun 25 20:57:31.000 [warn] TLS error while creating tor_tls_t obje
Hello
I have been working on Stem's general controller class. I have
completed implementing the methods that handle the GETCONF, SETCONF
and the RESETCONF (for the most part, I haven't put some of the code
up for review yet). I'm currently working on implementing the
SAVECONF, LOADCONF, SIGNAL met
