summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | tor-proto: comment fixes and more TODO hsNick Mathewson2023-01-242-2/+18
| | | |
| * | | tor-proto: Draft API to handle incoming BEGIN requests.Nick Mathewson2023-01-173-0/+98
| | | | | | | | | | | | | | | | Onion services (and later, exits and caches) will need this.
| * | | tor-proto: Expose support for doing onion service handshakesNick Mathewson2023-01-174-17/+79
| | | | | | | | | | | | | | | | | | | | | | | | This is a little tricky, but I think that we're not actually exposing too much here. I expect we'll need to tweak this stuff between now and our final version.
| * | | tor-proto: Draft APIs for handling control messagesNick Mathewson2023-01-172-1/+54
| | | | | | | | | | | | | | | | | | | | We will need these for onion services, to send and receive messages of types not handled directly by the tor-proto crate.
| * | | tor-proto: Rename "hs" experimental feature to "onion-common"Nick Mathewson2023-01-172-3/+6
| | | | | | | | | | | | | | | | (For consistency with other crates)
* | | | Merge branch 'onion-service-key-note' into 'main'Nick Mathewson2023-01-241-0/+112
|\ \ \ \ | |_|_|/ |/| | | | | | | | | | | Add a note about key storage in onion services and clients See merge request tpo/core/arti!974
| * | | Try to be less ambigous about "maybe offline"...Nick Mathewson2023-01-241-9/+15
| | | | | | | | | | | | | | | | | | | | | | | | ...by defining "offline" as "maybe online". @diziet is this what you had in mind?
| * | | Try to specify which keys are whichNick Mathewson2023-01-241-13/+20
| | | | | | | | | | | | | | | | Use the terminology in the current draft torspec!105 MR.
| * | | Add a note about key storage in onion services and clientsNick Mathewson2023-01-241-0/+99
| | |/ | |/|
* | | Merge branch 'bug736' into 'main'eta2023-01-241-0/+12
|\ \ \ | |/ / |/| | | | | | | | Prop304: Add extended SOCKS result codes for onion services See merge request tpo/core/arti!978
| * | Prop304: Add extended SOCKS result codes for onion servicesNeel Chauhan2023-01-181-0/+12
| | |
* | | Merge branch 'ignore' into 'main'Nick Mathewson2023-01-207-7/+0
|\ \ \ | | | | | | | | | | | | | | | | Do not .gitignore crates/*/fuzz/corpus See merge request tpo/core/arti!982
| * | | Do not .gitignore crates/*/fuzz/corpusIan Jackson2023-01-207-7/+0
| | | | | | | | | | | | | | | | | | | | These are symlinks which are actually checked in. They should not be ignored. (This caused trouble for some of my privsep tooling...)
* | | | Merge branch 'warnings' into 'main'Nick Mathewson2023-01-201-0/+7
|\ \ \ \ | |/ / / |/| | | | | | | | | | | tor-llcrypto: Tolerate some warnings See merge request tpo/core/arti!983
| * | | tor-llcrypto: Tolerate some warnings (fmt)Ian Jackson2023-01-201-1/+4
| | | |
| * | | tor-llcrypto: Tolerate some warningsIan Jackson2023-01-201-0/+4
|/ / / | | | | | | | | | | | | | | | Without this, cargo +stable clippy -p tor-netdoc --all-features produces warnings.
* | | Merge branch 'netdoc-builder' into 'main'Ian Jackson2023-01-201-0/+246
|\ \ \ | | | | | | | | | | | | | | | | RFC netdoc builder API See merge request tpo/core/arti!969
| * | | netdoc-builder api: Write down the correctness (non)-guaranteesIan Jackson2023-01-201-0/+10
| | | |
| * | | netdoc-builder api: Make object() take selfIan Jackson2023-01-201-3/+3
| | | | | | | | | | | | | | | | | | | | As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/969#note_2869594
| * | | netdoc-builder api: Change object multiplicity to 0 or 1Ian Jackson2023-01-201-5/+5
| | | |
| * | | netdoc-builder api: Provide raw methodsIan Jackson2023-01-201-0/+27
| | | |
| * | | netdoc-builder api: Fix typoIan Jackson2023-01-201-1/+1
| | | |
| * | | netdoc-builder api: Clarify ItemEncoder.objects contentIan Jackson2023-01-201-0/+4
| | | |
| * | | netdoc-builder api: In internal notes don't promise not to eagerly addIan Jackson2023-01-201-1/+2
| | | |
| * | | netdoc-builder api: Rename internal Builder to EncoderIan Jackson2023-01-201-15/+16
| | | | | | | | | | | | | | | | | | | | This seems clearer now and also it solves the name clash with the `NetdocBuilder` trait.
| * | | netdoc-builder api: Get rid of Item, and error reworkIan Jackson2023-01-201-6/+45
| | | |
| * | | netdoc-builder api: Add example of useIan Jackson2023-01-201-0/+18
| | | |
| * | | NetdocBuilder: Improvements apropos reviewIan Jackson2023-01-201-4/+30
| | | |
| * | | Improved pseudocode commentaryNick Mathewson2023-01-201-2/+3
| | | |
| * | | RFC netdoc builder APIIan Jackson2023-01-201-0/+119
|/ / /
* | | Merge branch 'updates_20210119' into 'main'Nick Mathewson2023-01-2016-89/+65
|\ \ \ | |/ / |/| | | | | | | | Update a few crate dependencies See merge request tpo/core/arti!981
| * | Upgrade to latest rsa crate.Nick Mathewson2023-01-203-18/+23
| | |
| * | Upgrade to latest async-broadcastNick Mathewson2023-01-202-3/+3
| | | | | | | | | | | | | | | (We don't yet use the code that uses it, but we might as well have our unused code be up-to-date.)
| * | upgrade to latest serial_testNick Mathewson2023-01-202-32/+7
| | |
| * | Complete our migration to base64ct.Nick Mathewson2023-01-2012-31/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | This is in lieu of upgrading to the latest base64 crate, which has a different API from the old one. Since we have to migrate either way, we might as well use base64ct everywhere. I don't think that most of these cases _require_ constant-time base64, but it won't hurt.
| * | Upgrade to latest rlimit crate.Nick Mathewson2023-01-192-5/+5
|/ /
* | Merge branch 'make-set-connect-prefs-public' into 'main'Nick Mathewson2023-01-181-4/+1
|\ \ | |/ |/| | | | | made TorClient::set_stream_prefs public See merge request tpo/core/arti!977
| * made TorClient::set_stream_prefs publicMichael van Straten2023-01-181-4/+1
|/
* Merge branch 'ffi-rpc-sketch' into 'main'Nick Mathewson2023-01-171-0/+241
|\ | | | | | | | | Sketch for some options and design issues around FFI/RPC See merge request tpo/core/arti!973
| * Update comments based on feedbackNick Mathewson2023-01-171-4/+17
| |
| * Apply 1 suggestion(s) to 1 file(s)Ian Jackson2023-01-131-0/+4
| |
| * Apply 1 suggestion(s) to 1 file(s)Ian Jackson2023-01-131-0/+4
| |
| * Sketch for some options and design issues around FFI/RPCNick Mathewson2023-01-131-0/+220
| | | | | | | | | | | | This is just a beginning, but hopefully we can expand it with more information and options, and then use it to get everybody in our nascent FFI/RPC working group on the same page.
* | Merge branch 'onion-api-client-toplevel' into 'main'eta2023-01-175-5/+27
|\ \ | | | | | | | | | | | | Make a top-level API for connecting to onion services. See merge request tpo/core/arti!971
| * | Make a top-level API for connecting to onion services.Nick Mathewson2023-01-125-5/+27
| |/ | | | | | | Fortunately, it adds very little to the arti-client API surface.
* | Merge branch 'bump_ed25519_153' into 'main'Nick Mathewson2023-01-161-2/+2
|\ \ | |/ |/| | | | | Bump Cargo.lock to ed25519 1.5.3 to fix CI. See merge request tpo/core/arti!975
| * Bump Cargo.lock to ed25519 1.5.3 to fix CI.Nick Mathewson2023-01-161-2/+2
|/ | | | ed25519 1.5.2 has been yanked.
* Merge branch 'onion-netdir-apis' into 'main'Nick Mathewson2023-01-1111-33/+346
|\ | | | | | | | | Add onion service APIs to tor-netdir See merge request tpo/core/arti!966
| * Adjust onion service ring APIs in light of prop#342Nick Mathewson2023-01-114-38/+99
| | | | | | | | | | | | | | | | | | | | * It is the NetDir's responsibility to tell the caller what the time period is. * There can be up to two secondary time periods. * Each time period has a single SRV. * Secondary time periods only apply for onion services, when they publish. * When publishing, the correct input is a time period.
| * Sketch APIs for the onion service directory ring.Nick Mathewson2023-01-115-4/+233
| | | | | | | | | | | | | | | | | | These are a bit complex internally, but the API they present is pretty simple. I've left some discussion of points where the design isn't totally fleshed out, and where we need to look harder at the spec. Part of #716.