| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2017-03-01 | Merge branch 'maint-0.3.0' into release-0.3.0tor-0.3.0.4-rc | Nick Mathewson | |
| 2017-03-01 | Restore correct behavior of 0.3.0.4-rc with bridges+ipv6-min | Nick Mathewson | |
| In that chutney test, the bridge client is configured to connect to the same bridge at 127.0.0.1:5003 _and_ at [::1]:5003, with no change in transports. That meant, I think, that the descriptor is only assigned to the first bridge when it arrives, and never the second. | |||
| 2017-03-01 | Pick a date | Nick Mathewson | |
| 2017-03-01 | Remove 21581 changes file: "bugfix not on any released Tor" | Nick Mathewson | |
| 2017-03-01 | Reflow changelog | Nick Mathewson | |
| 2017-03-01 | Fold in changelog of bug 21415 | Nick Mathewson | |
| 2017-03-01 | Make it clear that we fixed 2 cases of 20711 | Nick Mathewson | |
| 2017-03-01 | Remove changes files that got merged to 0.3.0.4-rc changelog | Nick Mathewson | |
| 2017-03-01 | Merge branch 'maint-0.3.0' into release-0.3.0 | Nick Mathewson | |
| 2017-03-01 | Improve descriptor checks in the new guard algorithm. | George Kadianakis | |
| - Make sure we check at least two guards for descriptor before making circuits. We typically use the first primary guard for circuits, but it can also happen that we use the second primary guard (e.g. if we pick our first primary guard as an exit), so we should make sure we have descriptors for both of them. - Remove BUG() from the guard_has_descriptor() check since we now know that this can happen in rare but legitimate situations as well, and we should just move to the next guard in that case. | |||
| 2017-03-01 | Merge branch 'maint-0.3.0' into release-0.3.0 | Nick Mathewson | |
| 2017-03-01 | Merge branch 'maint-0.2.9' into maint-0.3.0 | Nick Mathewson | |
| "Ours" merge to avoid version bump | |||
| 2017-03-01 | Bump to 0.2.9.10-dev | Nick Mathewson | |
| 2017-03-01 | Port 0.2.9.10 changelog and releasenotes to release-0.3.0 | Nick Mathewson | |
| 2017-03-01 | Merge branch 'maint-0.3.0' into release-0.3.0 | Nick Mathewson | |
| 2017-03-01 | Remove the space before the interpreter name in test-network.sh | teor | |
| Apparently some unixes don't like this. Part of #21581. | |||
| 2017-02-28 | Merge branch 'maint-0.3.0' into release-0.3.0 | Nick Mathewson | |
| 2017-03-01 | Remove a spurious test-network-all warning that triggers when sh is not bash | teor | |
| Part of 21581. | |||
| 2017-03-01 | Restore support for test-network.sh on BSD and other systems without bash | teor | |
| (But use bash if it's available.) This is a workaround until we remove bash-specific code in 19699. Fixes bug 21581; bugfix on 21562, not in any released version of tor. | |||
| 2017-02-28 | Merge branch 'maint-0.3.0' into release-0.3.0 | Nick Mathewson | |
| 2017-02-28 | bump version to 0.3.0.4-rc | Nick Mathewson | |
| 2017-02-28 | Merge branch 'maint-0.2.9' into maint-0.3.0 | Nick Mathewson | |
| This is an "ours" merge to avoid a version bump. | |||
| 2017-02-28 | bump version to 0.2.9.10 | Nick Mathewson | |
| 2017-02-28 | Merge branch 'maint-0.2.8' into maint-0.2.9 | Nick Mathewson | |
| This is an "ours" merge to avoid taking a version bump | |||
| 2017-02-28 | Merge branch 'maint-0.2.7-redux' into maint-0.2.8 | Nick Mathewson | |
| This is an "ours" merge to avoid taking a version bump, and to avoid replaying the post-0.2.7.6 history of "maint-0.2.7-redux" onto maint-0.2.8, which already included the relevant changes. | |||
| 2017-02-28 | bump version to 0.2.8.13 | Nick Mathewson | |
| 2017-02-28 | Bump version to 0.2.7.7 | Nick Mathewson | |
| 2017-02-28 | Merge branch 'maint-0.2.6' into maint-0.2.7-redux | Nick Mathewson | |
| "ours" merge to avoid version bumps | |||
| 2017-02-28 | bump to 0.2.6.11 | Nick Mathewson | |
| 2017-02-28 | Merge branch 'maint-0.2.5' into maint-0.2.6 | Nick Mathewson | |
| "ours" merge to avoid version bumps | |||
| 2017-02-28 | Bump version to 0.2.5.13 | Nick Mathewson | |
| 2017-02-28 | Merge branch 'maint-0.2.4' into maint-0.2.5 | Nick Mathewson | |
| "ours" merge to avoid bumping version | |||
| 2017-02-28 | Bump to 0.2.4.28 | Nick Mathewson | |
| 2017-02-28 | More changelog edits | Nick Mathewson | |
| 2017-02-28 | rewrite a little. | Nick Mathewson | |
| 2017-02-28 | Reflow 0.3.0.4-rc changelog | Nick Mathewson | |
| 2017-02-28 | sort changes into 0.3.0.4-rc changelog | Nick Mathewson | |
| 2017-02-28 | appease lintchanges | Nick Mathewson | |
| 2017-02-28 | Merge remote-tracking branch 'public/bug21007_case2_030' into maint-0.3.0 | Nick Mathewson | |
| 2017-02-28 | Merge branch 'bug21027_v2_squashed' into maint-0.3.0 | Nick Mathewson | |
| 2017-02-28 | Change approach to preventing duplicate guards. | Nick Mathewson | |
| Previously I'd made a bad assumption in the implementation of prop271 in 0.3.0.1-alpha: I'd assumed that there couldn't be two guards with the same identity. That's true for non-bridges, but in the bridge case, we allow two bridges to have the same ID if they have different addr:port combinations -- in order to have the same bridge ID running multiple PTs. Fortunately, this assumption wasn't deeply ingrained: we stop enforcing the "one guard per ID" rule in the bridge case, and instead enforce "one guard per <id,addr,port>". We also needed to tweak our implementation of get_bridge_info_for_guard, since it made the same incorrect assumption. Fixes bug 21027; bugfix on 0.3.0.1-alpha. | |||
| 2017-02-27 | Merge remote-tracking branch 'teor/feature21570-030' into maint-0.3.0 | Nick Mathewson | |
| 2017-02-27 | Merge branch 'bug21369_check_029_squashed' into maint-0.3.0 | Nick Mathewson | |
| 2017-02-27 | Merge branch 'bug21420_029_squashed' into maint-0.3.0 | Nick Mathewson | |
| 2017-02-27 | Revise the logic for picking the start time for link certs | Nick Mathewson | |
| Since 0.2.4.11-alpha (in 0196647970a91d) we've tried to randomize the start time to up to some time in the past. But unfortunately we allowed the start time to be in the future as well, which isn't really legit. The new behavior lets the start time be be up to MAX(cert_lifetime-2days, 0) in the past, but never in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha. | |||
| 2017-02-27 | Merge remote-tracking branch 'teor/bug20711' into maint-0.3.0 | Nick Mathewson | |
| 2017-02-28 | Use bash in src/test/test-network.sh | teor | |
| This ensures we reliably call chutney's newer tools/test-network.sh when available. Fixes bug 21562; bugfix on tor-0.2.9.1-alpha. | |||
| 2017-02-28 | Reserve a test-network.sh exit status of 2 for unknown arguments | teor | |
| Part of 21570. | |||
| 2017-02-28 | Log tor warnings during 'make test-network-all' | teor | |
| Requires the chutney changes from 21572. (Otherwise, asks users to upgrade their chutney.) Implements 21570. | |||
| 2017-02-27 | Add one other BUG check to try to fix/solve 21369. | Nick Mathewson | |
| Teor thinks that this connection_dirserv_add_dir_bytes_to_outbuf() might be the problem, if the "remaining" calculation underflows. So I'm adding a couple of checks there, and improving the casts. | |||
 |
index : tor | |
| Transit encryption and privacy out of the box | The Tor Project |
| summaryrefslogtreecommitdiff |