vincenzopalazzo
/
arti
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
arti/tor-client/Cargo.toml

34 lines
1.2 KiB
TOML
Raw Normal View History

Create a stub for a minimal demo client program. For now, it's set up to just use a chutney network, so I don't cause major drama with the real network. I'll be working on this in parallel with proto and netdir improvements, until it works.
2020-09-08 19:10:15 +01:00
[package]
Rename client-demo to tor-client.
2021-02-02 14:27:38 +00:00
name = "tor-client"
Create a stub for a minimal demo client program. For now, it's set up to just use a chutney network, so I don't cause major drama with the real network. I'll be working on this in parallel with proto and netdir improvements, until it works.
2020-09-08 19:10:15 +01:00
version = "0.0.0"
Add the tor project as an author.
2021-03-17 18:43:40 +00:00
authors = ["The Tor Project, Inc.", "Nick Mathewson <nickm@torproject.org>"]
Create a stub for a minimal demo client program. For now, it's set up to just use a chutney network, so I don't cause major drama with the real network. I'll be working on this in parallel with proto and netdir improvements, until it works.
2020-09-08 19:10:15 +01:00
edition = "2018"
license = "MIT OR Apache-2.0"
publish = false
Give it a homepage everyplace.
2021-03-17 18:13:26 +00:00
homepage = "https://gitlab.torproject.org/tpo/core/arti/-/wikis/home"
Add a description field to all our Cargo.toml files
2021-03-17 18:31:59 +00:00
description = "Library for connecting to the Tor network as an anonymous client"
Add keywords to each Cargo.toml
2021-03-17 18:41:02 +00:00
keywords = [ "tor", "arti", "privacy", "anonymity", "networking" ]
Add appropriate categories to some Cargo.toml files.
2021-03-17 18:49:54 +00:00
categories = [ "network-programming", "cryptography" ]
Create a stub for a minimal demo client program. For now, it's set up to just use a chutney network, so I don't cause major drama with the real network. I'll be working on this in parallel with proto and netdir improvements, until it works.
2020-09-08 19:10:15 +01:00
Port to work with tokio or async-std. This is fairly ugly and I think I'll need to mess around with the feature configuration a while until we get something that's pleasant to develop with. This still seems like a good idea, though, since we _will_ need to be executor-agnostic in the end, or we'll have no way to handle wasm or embedded environments. Later down the road, we'll probably want to use futures::Executor or futures::Spawn more than having global entry points in tor_rtcompat. That would probably make our feature story simpler. Tokio is the default now, since tokio seems to be more heavily used for performance-critical stuff. This patch breaks tests; the next one will fix them, albeit questionably.
2021-03-01 21:14:43 +00:00
[features]
default = [ "tokio" ]
Refactor tokio implpementation in tor-rtcompat. Now other crates don't need any 'ifdef tokio' code, since there are wrappers that implement 'futures' right. Technically, the 'futures' traits are in some ways less good than the tokio ones, but we need a consistent API if we want to support WASM someday and keep support for async_std. I'd rather hold out hope for a future version of futures::io working like tokio than to fix ourselves into the tokioverse forever.
2021-03-23 15:00:09 +00:00
async-std = [ "tor-rtcompat/async-std" ]
tokio = [ "tor-rtcompat/tokio" ]
Port to work with tokio or async-std. This is fairly ugly and I think I'll need to mess around with the feature configuration a while until we get something that's pleasant to develop with. This still seems like a good idea, though, since we _will_ need to be executor-agnostic in the end, or we'll have no way to handle wasm or embedded environments. Later down the road, we'll probably want to use futures::Executor or futures::Spawn more than having global entry points in tor_rtcompat. That would probably make our feature story simpler. Tokio is the default now, since tokio seems to be more heavily used for performance-critical stuff. This patch breaks tests; the next one will fix them, albeit questionably.
2021-03-01 21:14:43 +00:00
Create a stub for a minimal demo client program. For now, it's set up to just use a chutney network, so I don't cause major drama with the real network. I'll be working on this in parallel with proto and netdir improvements, until it works.
2020-09-08 19:10:15 +01:00
[dependencies]
Add a new circuit-manager crate and move path selection there.
2020-11-02 15:44:31 +00:00
tor-circmgr = { path="../tor-circmgr", version= "*" }
Refactor tokio implpementation in tor-rtcompat. Now other crates don't need any 'ifdef tokio' code, since there are wrappers that implement 'futures' right. Technically, the 'futures' traits are in some ways less good than the tokio ones, but we need a consistent API if we want to support WASM someday and keep support for async_std. I'd rather hold out hope for a future version of futures::io working like tokio than to fix ourselves into the tokioverse forever.
2021-03-23 15:00:09 +00:00
tor-chanmgr = { path="../tor-chanmgr", version= "*" }
Initial pass on directory-manager code. This code can now bootstrap from the network, cache the results, and reload from cache. There's lots more work to do here, including a big pile of tidying and refactoring and testing and documentation.
2020-11-19 19:25:02 +00:00
tor-dirmgr = { path="../tor-dirmgr", version="*" }
Create a stub for a minimal demo client program. For now, it's set up to just use a chutney network, so I don't cause major drama with the real network. I'll be working on this in parallel with proto and netdir improvements, until it works.
2020-09-08 19:10:15 +01:00
tor-netdir = { path="../tor-netdir", version= "*" }
tor-netdoc = { path="../tor-netdoc", version= "*" }
tor-proto = { path="../tor-proto", version= "*" }
Port to work with tokio or async-std. This is fairly ugly and I think I'll need to mess around with the feature configuration a while until we get something that's pleasant to develop with. This still seems like a good idea, though, since we _will_ need to be executor-agnostic in the end, or we'll have no way to handle wasm or embedded environments. Later down the road, we'll probably want to use futures::Executor or futures::Spawn more than having global entry points in tor_rtcompat. That would probably make our feature story simpler. Tokio is the default now, since tokio seems to be more heavily used for performance-critical stuff. This patch breaks tests; the next one will fix them, albeit questionably.
2021-03-01 21:14:43 +00:00
tor-rtcompat = { path="../tor-rtcompat", version= "*", default-features=false }
Start a directory client implementation It can send a GET request on a circuit, get an answer, and decompress it with zlib. It will need documentation and tests eventually, as well as serious refactoring.
2020-11-16 20:08:44 +00:00
tor-dirclient = { path="../tor-dirclient", version = "*" }
Initial support for configuration from file and/or command-line.
2021-02-02 18:26:02 +00:00
tor-linkspec = { path="../tor-linkspec", version = "*" }
Pare down and sort dependencies
2020-09-10 00:17:49 +01:00
Upgrade a few dependencies.
2021-01-13 13:14:28 +00:00
anyhow = "1.0.38"
upgrade to newer version of config crate.
2021-03-24 13:44:31 +00:00
config = { version = "0.11.0", default-features = false }
Update to latest futures, once_cell
2021-02-23 20:54:29 +00:00
futures = "0.3.13"
bump serde and log
2021-02-01 21:39:07 +00:00
log = "0.4.14"
Update some dependencies.
2021-02-19 14:39:23 +00:00
thiserror = "1.0.24"