| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
| |
we can't make them totally obsolete yet but we can get closer.
svn:r12626
|
|
|
|
|
|
|
| |
server-side code (for when v2 negotiation occurred) to check for renegotiation and adjust client ID info accordingly. server-side of new TLS code is now implemented, but needs testing and debugging.
svn:r12624
|
|
|
|
|
|
|
| |
Add support to get a callback invoked when the client renegotiate a connection. Also, make clients renegotiate. (not enabled yet, until they detect that the server acted like a v2 server)
svn:r12623
|
|
|
|
|
|
|
| |
Start getting freaky with openssl callbacks in tortls.c: detect client ciphers, and if the list doesn't look like the list current Tors use, present only a single cert do not ask for a client cert. Also, support for client-side renegotiation. None of this is enabled unless you define V2_HANDSHAKE_SERVER.
svn:r12622
|
|
|
|
| |
svn:r12621
|
|
|
|
|
|
|
| |
should happen in practice. but now they really won't.
svn:r12620
|
|
|
|
| |
svn:r12619
|
|
|
|
| |
svn:r12618
|
|
|
|
|
|
|
| |
Do not keep a string representation of every single addr_policy_t lying around. This might save a few hundred K.
svn:r12617
|
|
|
|
|
|
|
| |
Log *useful* information from dmalloc. (Unfreed pointers, not total of freed and unfreed).
svn:r12616
|
|
|
|
| |
svn:r12615
|
|
|
|
| |
svn:r12614
|
|
|
|
|
|
|
| |
When using dmalloc, dump the top ten memory consumers to the _DMALLOC_ logfile when we get a SIGUSR1. Hint: it is not what you would think.
svn:r12613
|
|
|
|
| |
svn:r12612
|
|
|
|
| |
svn:r12610
|
|
|
|
| |
svn:r12609
|
|
|
|
| |
svn:r12608
|
|
|
|
| |
svn:r12607
|
|
|
|
| |
svn:r12606
|
|
|
|
|
|
|
|
| |
better *not* publish a cosmetically similar descriptor within 12
hours of the last one.
svn:r12605
|
|
|
|
| |
svn:r12604
|
|
|
|
| |
svn:r12603
|
|
|
|
| |
svn:r12602
|
|
|
|
| |
svn:r12601
|
|
|
|
| |
svn:r12600
|
|
|
|
| |
svn:r12599
|
|
|
|
| |
svn:r12598
|
|
|
|
| |
svn:r12580
|
|
|
|
|
|
|
|
|
|
| |
that have no introduction points. But Tor crashed when we tried
to build a descriptor with no intro points (and it would have
crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
by Karsten Loesing.
svn:r12579
|
|
|
|
| |
svn:r12572
|
|
|
|
| |
svn:r12571
|
|
|
|
|
|
|
|
|
|
| |
enough directory information. This was causing us to always pick
two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
causing us to discard all our guards on startup if we hadn't been
running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
svn:r12570
|
|
|
|
| |
svn:r12566
|
|
|
|
| |
svn:r12562
|
|
|
|
| |
svn:r12555
|
|
|
|
|
|
|
| |
tested. Update torbutton version in TorPostFlight.
svn:r12554
|
|
|
|
| |
svn:r12552
|
|
|
|
|
|
|
| |
changed *to*.
svn:r12551
|
|
|
|
|
|
|
| |
PublishServerDescriptor.
svn:r12550
|
|
|
|
|
|
|
|
| |
PublishServerDescriptor config option. Reported by Matt Edman;
bugfix on 0.2.0.9-alpha.
svn:r12549
|
|
|
|
| |
svn:r12528
|
|
|
|
| |
svn:r12527
|
|
|
|
| |
svn:r12526
|
|
|
|
| |
svn:r12523
|
|
|
|
|
|
|
|
| |
consensus documents when there are too many relays at a single
IP address. Now clear it in v2 network status documents too.
svn:r12522
|
|
|
|
| |
svn:r12516
|
|
|
|
|
|
|
|
|
|
|
|
| |
When authorities detected more than two relays running on the same
IP address, they were clearing all the status flags but forgetting
to clear the "hsdir" flag. So clients were being told that a
given relay was the right choice for a v2 hsdir lookup, yet they
never had its descriptor because it was marked as 'not running'
in the consensus.
svn:r12515
|
|
|
|
|
|
|
|
| |
chosen exit is in the same family as all our bridges/entry guards,
then be flexible about families.
svn:r12514
|
|
|
|
| |
svn:r12513
|
|
|
|
|
|
|
|
|
| |
the bridge authority could help us (for example, we don't know
a digest, or there is no bridge authority), don't be so eager to
fall back to asking the bridge authority.
svn:r12512
|