summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | | socksproto: Rename SocksHandshake to SocksProxyHandshake.Nick Mathewson2022-09-276-524/+547
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Retain "SocksHandshake" as a deprecated synonym. Also, make an (on-by-default) feature for SocksProxyHandshake. (There is about to be a SocksClientHandshake as well.)
* | | | | Script to list current version of every crate.arti-v1.0.1Nick Mathewson2022-10-031-0/+15
| | | | |
* | | | | Oops: propagate bumps to Cargo.lock.Nick Mathewson2022-10-031-3/+3
| | | | |
* | | | | Bump patchlevels of binary crates.Nick Mathewson2022-10-034-16/+16
| | | | | | | | | | | | | | | | | | | | | | | | | Since these don't expose any Runtime-based APIs, they don't have a breaking change.
* | | | | Bump minor version of tor-rtcompat and most of its dependentsNick Mathewson2022-10-0315-65/+65
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (Since the APIs for the `Schedule::sleep*` functions changed, this is a breaking change in tor-rtcompat. Therefore, the Runtime trait in tor-rtcompat is now a different trait. Therefore, anything that uses the Runtime trait in its APIs has also broken.)
* | | | | Bump crates that have had backward compatible API changes.Nick Mathewson2022-10-0319-46/+46
| | | | |
* | | | | Bump crates that have had no API changes.Nick Mathewson2022-10-036-6/+6
| | | | |
* | | | | Merge branch 'changelog-typos-2022-10' into 'main'Nick Mathewson2022-10-031-3/+3
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | CHANGELOG: fix some typos See merge request tpo/core/arti!751
| * | | | | CHANGELOG: fix some typoseta2022-10-031-3/+3
|/ / / / /
* | | | | changed_crates: output crates in toposort order.Nick Mathewson2022-10-031-1/+1
| | | | |
* | | | | Finish filling in the changelog for 1.0.1Nick Mathewson2022-10-031-2/+38
| | | | |
* | | | | Merge branch 'upgrade-20220930' into 'main'Nick Mathewson2022-09-305-137/+247
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Upgrade various things in preparation for monday release See merge request tpo/core/arti!750
| * | | | | Update README.md files.Nick Mathewson2022-09-303-0/+61
| | | | | |
| * | | | | Run cargo update in preparation for upcoming release.Nick Mathewson2022-09-301-122/+128
| | | | | |
| * | | | | Upgrade dependencies in preparation for upcoming releaseNick Mathewson2022-09-302-15/+58
| | |_|_|/ | |/| | |
* / | | | Start a changelog for Arti 1.0.1Nick Mathewson2022-09-301-0/+63
|/ / / /
* | | | Merge branch 'from_bool_fix' into 'main'Nick Mathewson2022-09-304-18/+23
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | Work around a new nightly clippy warning See merge request tpo/core/arti!749
| * | | | Work around a new nightly clippy warningNick Mathewson2022-09-304-18/+23
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The warning `clippy::bool_to_int_with_if` is meant to shout at you when you say `if x { 1 } else { 0 }` and instead suggest that you say `inttype::from(x)`. I agreed with this for the case in tor-cert, where we are literally converting a boolean into a flag. I don't agree with this in tor-netdoc, where we are using a boolean to decide how many fields to skip in a given document format. So for this case, I decided to clean up the code a little by renaming "skip" to "n_skip", and changing the boolean to use an enum instead.
* | | | Merge branch 'bridge-apis-are-experimental' into 'main'Ian Jackson2022-09-297-1/+68
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | Mark all bridge and pt features as experimental for now. Closes #588 See merge request tpo/core/arti!748
| * | | Mark all bridge and pt features as experimental for now.Nick Mathewson2022-09-297-1/+68
|/ / / | | | | | | | | | | | | | | | Also, document the features. Closes #588.
* | | Merge branch 'pt-name' into 'main'Ian Jackson2022-09-273-16/+77
|\ \ \ | |/ / |/| | | | | | | | pt: Introduce PtTransportName See merge request tpo/core/arti!743
| * | pt: Reject a pluggable transport named BridgeIan Jackson2022-09-271-0/+5
| | | | | | | | | | | | https://gitlab.torproject.org/tpo/core/torspec/-/merge_requests/91
| * | Remove docsrs thing which is in wrong place?Ian Jackson2022-09-271-1/+0
| | |
| * | pt: Try to fix docsrs problemIan Jackson2022-09-272-1/+2
| | |
| * | pt: Use PtTransportName in PtTargetIan Jackson2022-09-271-1/+1
| | |
| * | pt: Use PtTransportName in TransportIdIan Jackson2022-09-271-2/+2
| | |
| * | pt: PtTransportName: Provide TryFrom, into_inner, AsRefIan Jackson2022-09-271-4/+27
| | | | | | | | | | | | This seems a minimal API for such a thing.
| * | pt: tor-linkspec: Shorten some names with useIan Jackson2022-09-271-12/+17
| | | | | | | | | | | | This repetition was getting repetitive.
| * | pt: Introduce PtTransportNameIan Jackson2022-09-272-5/+33
|/ / | | | | | | | | The config parsing wants this. Also there are some anomalies in the types here that ought to be tidied up.
* | Merge branch 'always_safelog_on_console' into 'main'Ian Jackson2022-09-261-30/+10
|\ \ | | | | | | | | | | | | | | | | | | Enforce SafeLogging on the console. Closes #553 See merge request tpo/core/arti!742
| * | Enforce SafeLogging on the console.Nick Mathewson2022-09-261-30/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously we always assumed that the console was ephemeral, and so we disabled safe logging. But the console can be piped to journald. And even if we enforce isatty there's no guarantee that the user isn't using some kind of terminal that logs to disk or something. Best just to enable SafeLogging unconditionally. I've added a note about where and how we might re-enable this. Closes #553.
* | | Merge branch 'pt-client-api-part-2' into 'main'Nick Mathewson2022-09-2612-0/+221
|\ \ \ | |/ / |/| | | | | | | | | | | | | | Remaining bridge-and-pt APIs Closes #543 See merge request tpo/core/arti!741
| * | Add the necessary APIs for bridge-based circuit construction.Nick Mathewson2022-09-262-0/+11
| | |
| * | GuardMgr/DirMgr: Add APIs for bridge descriptor listsNick Mathewson2022-09-266-3/+116
| | |
| * | Make RouterDesc implement Clone and Debug.Nick Mathewson2022-09-262-0/+3
| | | | | | | | | | | | Their omission was an oversight.
| * | GuardMgr: Add TODOs for bridge support.Nick Mathewson2022-09-262-0/+29
| | | | | | | | | | | | | | | | | | This covers only the most basic notions of working with bridges: that we need a separate set of guards, and that they have to come from the list of known bridges.
| * | A basic configuration type for a bridge.Nick Mathewson2022-09-265-1/+66
|/ / | | | | | | | | | | | | This type goes in tor-guardmgr, since that's where decisions about circuits' first hops are made. There are a lot of "todo"s here for us to resolve.
* | Merge branch 'cell-introduce2' into 'main'Ian Jackson2022-09-263-16/+67
|\ \ | | | | | | | | | | | | Implement Introduce2 tor cell See merge request tpo/core/arti!736
| * | Implement Introduce2 tor cellYuan Lyu2022-09-213-16/+67
| | | | | | | | | | | | | | | Reuse the same Introduce inner body implementation of Introduce1.
* | | Merge branch 'pt-client-api-part-1' into 'main'Nick Mathewson2022-09-2319-2/+798
|\ \ \ | | | | | | | | | | | | | | | | Add sketched-out pluggable transport APIs (part 1) See merge request tpo/core/arti!740
| * | | Add a few comments based on review.Nick Mathewson2022-09-232-0/+11
| | | |
| * | | Clarify and combine PtTargetAddr constructors.Nick Mathewson2022-09-231-16/+23
| | | |
| * | | Rename various Transport* types to Pt*.Nick Mathewson2022-09-233-44/+43
| | | | | | | | | | | | | | | | | | | | This clarifies that the types apply to pluggable transports only, and not (typically) to the default plain-old-TCP transport.
| * | | Clarify note on "none" transport ID.Ian Jackson2022-09-231-0/+3
| | | |
| * | | Add the skeleton of a tor-ptmgr crateNick Mathewson2022-09-236-0/+257
| | | | | | | | | | | | | | | | | | | | When complete, this crate will handle launching and using pluggable transports on demand.
| * | | ChanMgr: new (unimplemented) APIs for pluggable transportsNick Mathewson2022-09-236-0/+152
| | | |
| * | | Add a HasChanMethods trait, with a bunch of open TODO questions.Nick Mathewson2022-09-233-2/+24
| | | | | | | | | | | | | | | | We'll need to sort these out as we implement pluggable transports.
| * | | New data types to describe transport targets.Nick Mathewson2022-09-233-1/+59
| | | | | | | | | | | | | | | | | | | | I've tried to name and structure these for consistency, and comment reasonably well. We'll still probably want to make changes.
| * | | Add TransportTargetAddr as the target address for a PT-using channelNick Mathewson2022-09-232-1/+118
| | | | | | | | | | | | | | | | | | | | | | | | As with `TransportId`, this type only gets complicated when `pt-client` is enabled: it's meant to stay simple for relays and non-PT-using clients.
| * | | Create an API for TransportIdNick Mathewson2022-09-235-0/+170
|/ / /
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-27 14:47:47 +0000