mirrors/arti.git/Cargo.toml, branch arti-v1.1.13mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.132024-01-25T16:40:10Ztest-temp-dir: New crate2024-01-25T16:40:10ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-25T16:28:00Zurn:sha1:f8e218ca508697c43fd7e7a1a00f44c2d5f3ff35
Introduce the crate, move the code motion, and make minimal necessary
changes.
fslock-guard: sketch implementation2024-01-21T21:51:25ZNick Mathewsonnickm@torproject.org2024-01-21T21:46:27Zurn:sha1:70815226d086473152ec98a5ae8341ef4d067be3
This is not yet "correct", since it will rely on
https://github.com/brunoczim/fslock/pull/15
(Conceivably, it might be better to make the `fslock` crate rm-safe.)
Examples using hyper v12024-01-11T10:34:59Zramidzkhramidzkh@gmail.com2024-01-11T10:34:59Zurn:sha1:5cea7626e41a101986346e788403aade4dd52d81New tor-log-ratelim crate2023-11-16T19:31:15ZNick Mathewsonnickm@torproject.org2023-10-28T21:07:30Zurn:sha1:ca7899a602b307889870dabafd9e7709583a0c24
This crate is meant to provide rate-limited log messages
to tell users about problems that can happen too frequently
to log individually.
This version is based off an earlier design, and off of
conversations with @diziet. It still needs tests.
Merge branch 'hss_config' into 'main'2023-09-07T14:34:06ZNick Mathewsonnickm@torproject.org2023-09-07T14:34:06Zurn:sha1:38bf85ea33f5fdf4362ee9639a88e656793eda3e
Begin working on configuration logic for onion services
See merge request tpo/core/arti!1557Create a tor-hsrproxy crate to handle "proxy to local port".2023-09-07T13:56:24ZNick Mathewsonnickm@torproject.org2023-08-28T12:45:17Zurn:sha1:01f954d3782df57a4ac1d2cd1d323584ccaaac76
I'm calling this a "reverse proxy" since I think a lot of folks like
that terminology, though I'm not personally a huge fan. Calling it
"`tor-hsproxy`" would IMO confuse people more about what kind of proxy
it was.
This is a separate crate from `tor-hsservice` because it's logically
at a different level: if you're writing a little embedded onion
service, you don't need this code.
Right now there is only configuration logic here.
Move examples to examples/gsoc20232023-09-06T02:34:56ZNick Mathewsonnickm@torproject.org2023-08-30T18:47:29Zurn:sha1:0fc24b8373073fd6dc19663ae55f9a2859a9ce98fix: add examples to main Cargo.toml2023-09-06T02:33:52ZSaksham Mittalgotlouemail@gmail.com2023-08-29T16:22:43Zurn:sha1:1c33d690d3e0be5b922ed82a2efcbe21b446c05fInclude debug symbols in "bench" profile2023-07-27T14:20:14ZMicah Elizabeth Scottbeth@torproject.org2023-07-05T21:03:29Zurn:sha1:3e8b8d035a110a8f55100029638246a179586597
Including full debug symbols makes the benchmark builds useful for
profiling too.
Start implementing Proposal 3272023-07-27T14:20:14ZMicah Elizabeth Scottbeth@torproject.org2023-06-28T22:15:17Zurn:sha1:e7aa1d6b6251102f9b2b0e382ad2a1f7b5b47ee5
This adds a new tor-hspow crate with the first layers of support in
place for onion service client puzzles as described in Proposal 327.
The API here is experimental, and it's currently only implementing
the self-contained parts of the client puzzle. So, it can verify and
solve puzzles, but it has no event loop integration or nonce replay
tracking or prioritization code yet. These things seem like they would
eventually live in the same crate.
Signed-off-by: Micah Elizabeth Scott <beth@torproject.org>