summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* r14021@Kushana: nickm | 2007-08-14 16:16:58 -0400Nick Mathewson2007-08-14
| | | | | | | Document http status codes svn:r11111
* r14017@Kushana: nickm | 2007-08-14 15:13:14 -0400Nick Mathewson2007-08-14
| | | | | | | Enable more code for v3 voting timing information. Also, spec clarification. svn:r11107
* add draft 119-controlport-auth proposalRoger Dingledine2007-08-14
| | | | svn:r11106
* add a sketch for an 'advertising multiple orports' proposalRoger Dingledine2007-08-13
| | | | svn:r11082
* updated implementation statuses, included non-consecutive replication to ↵Karsten Loesing2007-08-11
| | | | | | descriptor format svn:r11080
* r13952@Kushana: nickm | 2007-08-08 07:40:04 -0700Nick Mathewson2007-08-08
| | | | | | | Note *how* obsolete v0 really is. svn:r11064
* tell proposal 110 its proposal numberRoger Dingledine2007-08-07
| | | | svn:r11054
* christian tells me that a student of his is working on implementingRoger Dingledine2007-08-05
| | | | | | | proposal 110 this summer svn:r11047
* backward compatibility with control protocol v0 no longer specifiedRoger Dingledine2007-08-02
| | | | | | | to work svn:r11040
* r13920@Kushana: nickm | 2007-08-02 11:00:05 -0700Nick Mathewson2007-08-02
| | | | | | | Document new authentication behavior in control-spec.txt svn:r11039
* r14016@catbus: nickm | 2007-07-30 13:45:55 -0400Nick Mathewson2007-07-30
| | | | | | | More documentation svn:r10992
* Be even more aggressive about separating local traffic from relayedRoger Dingledine2007-07-29
| | | | | | | traffic when RelayBandwidthRate is set. (Refines proposal 111.) svn:r10974
* r13982@catbus: nickm | 2007-07-29 01:31:53 -0400Nick Mathewson2007-07-29
| | | | | | | Actually, we missed a rule about what routers to prefer: first prefer authority to non-authority, *then* running, *then* bandwidth. svn:r10969
* r13979@catbus: nickm | 2007-07-29 01:20:20 -0400Nick Mathewson2007-07-29
| | | | | | | Implement proposal 109: As an authority, never call more than 3 servers per IP Running and Valid. Prefer Running servers to non-running ones; then prefer high-bandwidth to low-bandwidth. Needs testing. svn:r10968
* r13977@catbus: nickm | 2007-07-29 00:09:52 -0400Nick Mathewson2007-07-29
| | | | | | | Add compatibility note to control-spec.txt svn:r10966
* r13972@catbus: nickm | 2007-07-29 00:01:38 -0400Nick Mathewson2007-07-29
| | | | | | | Make our control events for multi-line async replies conform to our old grammar. Change back to the old grammar (which got "corrected" in r10931). svn:r10964
* r13959@catbus: nickm | 2007-07-28 18:09:56 -0400Nick Mathewson2007-07-28
| | | | | | | Use the correct formula to calculate exit weights. svn:r10956
* r13906@catbus: nickm | 2007-07-25 18:49:50 -0400Nick Mathewson2007-07-25
| | | | | | | Patch from tup: correct grammar for asynchonous reply lines in control-spec.txt svn:r10931
* r13905@catbus: nickm | 2007-07-25 18:48:44 -0400Nick Mathewson2007-07-25
| | | | | | | ADDRMAP events should never have specified local time. Extend them to have the proper gmt time, and make GETINFO address-mappings always do the right thing (since it is new in this version). svn:r10930
* clarify that when we say 'above the median' we mean 'at leastRoger Dingledine2007-07-22
| | | | | | | the median' svn:r10899
* Directory authorities now call routers Fast if their bandwidth isRoger Dingledine2007-07-21
| | | | | | | | | at least 100KB/s, and consider their bandwidth adequate to be a Guard if it is at least 250KB/s. This fix complements proposal 107. [Bugfix on 0.1.2.x] svn:r10897
* r13854@catbus: nickm | 2007-07-20 13:40:45 -0400Nick Mathewson2007-07-20
| | | | | | | Patches to proposal 117 from coderman (from or-dev, 18 Jun) svn:r10892
* r13801@catbus: nickm | 2007-07-17 13:49:12 -0400Nick Mathewson2007-07-17
| | | | | | | More tweaks to dir-spec.txt; not complete, but closing in. svn:r10856
* r13777@catbus: nickm | 2007-07-16 12:58:08 -0400Nick Mathewson2007-07-16
| | | | | | | Patch from tup: new address-mappings/ GETINFO that includes expiry times. svn:r10844
* some cleanups on phrasing in proposal 114Roger Dingledine2007-07-12
| | | | svn:r10821
* admit that our rend spec was lying. sorry karsten!Roger Dingledine2007-07-12
| | | | svn:r10798
* r13674@catbus: nickm | 2007-07-10 13:27:30 -0400Nick Mathewson2007-07-10
| | | | | | | Re-wrap proposal 117 so it fits in 80 columns. svn:r10784
* r13672@catbus: nickm | 2007-07-10 13:17:08 -0400Nick Mathewson2007-07-10
| | | | | | | Add IPv6 exit proposal from coderman. svn:r10783
* r13667@catbus: nickm | 2007-07-10 13:12:52 -0400Nick Mathewson2007-07-10
| | | | | | | Patch from tup: add GETINFO status/enough-dir-info svn:r10782
* r13666@catbus: nickm | 2007-07-10 13:10:00 -0400Nick Mathewson2007-07-10
| | | | | | | Get the RESOLVE controller code working. svn:r10781
* incorporated suggestions by Roger, added status of specification and ↵Karsten Loesing2007-07-09
| | | | | | implementation for upcoming GSoC mid-term evaluation svn:r10773
* r13451@kushana: nickm | 2007-06-20 09:43:26 -0400Nick Mathewson2007-07-05
| | | | | | | Fix typos and clarify points in dir-spec. Patch from Karsten. svn:r10736
* the non-controversial changes i found in my sandboxRoger Dingledine2007-07-02
| | | | svn:r10729
* r13594@catbus: nickm | 2007-07-02 15:53:35 -0400Nick Mathewson2007-07-02
| | | | | | | dir-spec.txt clarifications suggested by Lee Fisher. svn:r10725
* set svn propertiesKarsten Loesing2007-06-26
| | | | svn:r10685
* r13524@catbus: nickm | 2007-06-26 17:48:39 -0400Nick Mathewson2007-06-26
| | | | | | | Update 108 based on conversation with Roger. I think this is the version to build. svn:r10684
* r13522@catbus: nickm | 2007-06-26 17:37:43 -0400Nick Mathewson2007-06-26
| | | | | | | Add proposal 116 from Mike Lieberman: Two hop paths from entry guards. svn:r10683
* r13463@catbus: nickm | 2007-06-17 11:10:17 -0400Nick Mathewson2007-06-17
| | | | | | | Add a SOURCE_ADDR field to STREAM NEW events so that controllers can match requests to applications. (Patch from Robert Hogan.) svn:r10639
* r13437@catbus: nickm | 2007-06-15 14:29:56 -0400Nick Mathewson2007-06-17
| | | | | | | Incorporate comments [from april, ugh] into proposal 108. svn:r10636
* r13419@catbus: nickm | 2007-06-14 14:05:17 -0400Nick Mathewson2007-06-17
| | | | | | | Clarify some rules about svn:r10635
* unified svn properties and keywords for proposals and address specKarsten Loesing2007-06-16
| | | | svn:r10625
* last attempt before reading the manualKarsten Loesing2007-06-16
| | | | svn:r10622
* attempt to fix revision and date tagsKarsten Loesing2007-06-16
| | | | svn:r10620
* More work towards making bridge users able to connect via bridges:Roger Dingledine2007-06-12
| | | | | | | | | | | | | | | | | | | | | - 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
* r13366@catbus: nickm | 2007-06-11 20:38:38 -0400Nick Mathewson2007-06-12
| | | | | | | Clarify what we mean by digest, for people who ignore "as signed" and who don't read section 1.3. svn:r10568
* Fix some typos, clarify some minor semantics, change phases to reflectMike Perry2007-06-06
| | | | | | | | PathlenCoinWeight-style implementation (for fingerprinting resistance). svn:r10508
* Attempt to address points brought up in #tor flamewar. In particular, movedMike Perry2007-06-05
| | | | | | | | | | | | | | | | | | | | "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
* r13250@catbus: nickm | 2007-06-04 18:28:55 -0400Nick Mathewson2007-06-04
| | | | | | | 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
* r13243@catbus: nickm | 2007-06-04 15:17:15 -0400Nick Mathewson2007-06-04
| | | | | | | 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
* Think a little harder about guard nodes. What if they could be made to beMike Perry2007-06-03
| | | | | | | | | | | 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
generated by cgit v1.2.1 (git 2.18.0) at 2024-02-08 07:42:15 +0000