| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- demand options->Bridges and options->TunnelDirConns if
options->UseBridges is set.
- after directory fetches, accept descriptors that aren't referenced by
our networkstatuses, *if* they're for a configured bridge.
- delay directory fetching until we have at least one bridge descriptor.
- learn how to build a one-hop circuit when we have neither routerinfo
nor routerstatus for our destination.
- teach directory connections how to pick a bridge as the destination
directory when doing non-anonymous fetches.
- tolerate directory commands for which the dir_port is 0.
- remember descriptors when the requested_resource was "authority",
rather than just ignoring them.
- put bridges on our entry_guards list once we have a descriptor for them.
When UseBridges is set, only pick entry guards that are bridges. Else
vice versa.
svn:r10571
|
| |
|
|
|
|
|
| |
Clarify what we mean by digest, for people who ignore "as signed" and who don't read section 1.3.
svn:r10568
|
| |
|
|
|
|
|
|
| |
PathlenCoinWeight-style implementation (for fingerprinting resistance).
svn:r10508
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"Who will enable this option?" section towards the top of the proposal, to
attempt to get everyone on the same page right away as far as assumptions
go.
Also, added section on "Consideration of risks for node operators" where
the additional risk of should-be-3-but-actually-2 hop users pose to node
operators is discussed. Upon consideration of this, determined that two hop
users should be made to rotate guards with some frequency on the order of
days (basically, long enough to help scan the network for active adversary
guards, and then move on).
Please re-flame if you feel these or other issues have not been adequately
addressed.
svn:r10498
|
| |
|
|
|
|
|
| |
Adapt code to parse v3 networkstatus votes so it can also parse a consensus. Make networkstatus_vote_t the catch-all type for votes and conensuses. Correct/clarify the second argument to directory-signature.
svn:r10491
|
| |
|
|
|
|
|
| |
Start of code to compute consensus network-status stuff from a bunch of votes. Strangely, it does not yet feel like an enormous ugly hack.
svn:r10489
|
| |
|
|
|
|
|
|
|
|
|
| |
reliable and not rotate as much for dialup, mobile, or transient network
users, and what if users were actually notified more visibly who their guards
were and came to trust the guard nodes they have? Some effects of this are
considered.
svn:r10470
|
| |
|
|
|
|
|
| |
First cut at code to parse and validate v3 networkstatus votes.
svn:r10461
|
| |
|
|
| |
svn:r10435
|
| |
|
|
|
|
|
| |
to read karsten's distributed-storage proposal
svn:r10430
|
| |
|
|
| |
svn:r10415
|
| |
|
|
| |
svn:r10413
|
| |
|
|
| |
svn:r10374
|
| |
|
|
|
|
|
| |
Make caches-extra-info lines parseable.
svn:r10215
|
| |
|
|
|
|
|
| |
Note that we do not permit you to exit to port 0, no matter what. Closes bug 409.
svn:r10211
|
| |
|
|
|
|
|
| |
More work on merging stuff into dir-spec.txt
svn:r10207
|
| |
|
|
| |
svn:r10182
|
| |
|
|
|
|
|
| |
Checkpoint some more dir-spec.txt edits.
svn:r10165
|
| |
|
|
|
|
|
|
| |
network-status but we don't want to keep it. Otherwise we'll keep fetching
it and keep not wanting to keep it. Fixes part of bug 422.
svn:r10153
|
| |
|
|
| |
svn:r10126
|
| |
|
|
| |
svn:r10110
|
| |
|
|
|
|
| |
of the world as of 0.1.2.13. Start revising dir-spec.txt to incorporate proposals 101, 103, and 104.
svn:r10109
|
| |
|
|
|
|
|
| |
Note that extensions to the directory protocol should begin their item keywords with "x-" or "X-".
svn:r10108
|
| |
|
|
|
|
|
| |
Document the nonpersistent controller-only options.
svn:r10107
|
| |
|
|
|
|
|
| |
Fix dir-spec: there is not actually any such item as link-key. (Found by Benedikt.)
svn:r10095
|
| |
|
|
|
|
|
| |
Add an expiry date to key certificates.
svn:r10079
|
| |
|
|
|
|
|
| |
Changes to 103 based on or-dev mail from arma.
svn:r10065
|
| |
|
|
|
|
|
| |
Misc cleanup and bulletproofing on r10056.
svn:r10058
|
| |
|
|
|
|
|
| |
so we can exit from the middle of the circuit.
svn:r10056
|
| |
|
|
| |
svn:r10055
|
| |
|
|
| |
svn:r10050
|
| |
|
|
| |
svn:r10022
|
| |
|
|
| |
svn:r10001
|
| |
|
|
|
|
|
| |
The ten thousandth Tor commit: add two new proposals (one from Mike Perry about randomized path length, and one from me about simplifyin authority operation) and expand and/or refine serveral older ones. Most notable there are changes to 103 that will allow us to make authorities more resistant to key compromise.
svn:r10000
|
| |
|
|
|
|
|
| |
Describe a simpler implementation for proposal 108, and note some limitations in the proposal.
svn:r9993
|
| |
|
|
|
|
|
| |
Mark proposal 104 accepted
svn:r9974
|
| |
|
|
| |
svn:r9973
|
| |
|
|
|
|
|
| |
Document multiplicity on some router elements better.
svn:r9964
|
| |
|
|
|
|
|
| |
Initial code to parse extra-info documents as described in proposal 104. This is making me realize that the parsing code in routerparse.c is a little daft.
svn:r9963
|
| |
|
|
|
|
|
| |
Clarify some points in proposal 104, mostly based on mail from arma on or-dev.
svn:r9955
|
| |
|
|
|
|
|
| |
Try to clarify window verbiage a little in tor-spec.
svn:r9954
|
| |
|
|
| |
svn:r9893
|
| |
|
|
| |
svn:r9892
|
| |
|
|
|
|
|
| |
Incorporate ideas from or-dev discussion.
svn:r9891
|
| |
|
|
|
|
|
| |
Add specification to proposal 104; settle on "extra info" approach rather than "long descriptor" approach.
svn:r9890
|
| |
|
|
|
|
|
| |
Merge or-dev discussion into 109; mark 109 accepted.
svn:r9864
|
| |
|
|
| |
svn:r9854
|
| |
|
|
|
|
|
| |
Add proposal 111: Prioritizing local traffic over relayed traffic.
svn:r9830
|
| |
|
|
|
|
|
| |
Clarify section of dir-spec.txt that explains how "v" resolution happens.
svn:r9829
|
| |
|
|
| |
svn:r9824
|