| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
behavior for getinfo addr-mappings/*. this is because
the code and spec have been mismatched since at least
0.1.1.x, so i would be surprised if nobody at all is
relying on the current behavior.
backport candidate.
backbackport candidate.
svn:r9823
|
|
|
|
|
|
|
|
|
|
| |
it a GUARD event. standardize on GUARD, but support people
asking for GUARDS too. reported by daejees.
backport candidate.
svn:r9817
|
|
|
|
| |
svn:r9816
|
|
|
|
|
|
|
|
| |
to proposal 110. the proposals that were around before the proposals
scheme got started still don't have dates.
svn:r9815
|