summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | | | tor-hsservice: Initial work towards mocking RendRequest.Wesley Aptekar-Cassels2025-07-231-24/+39
| | | | | |
| * | | | | tor-hsservice: Allow mocking PowManager.Wesley Aptekar-Cassels2025-07-231-4/+16
| | | | | |
| * | | | | tor-hsservice: Enforce maximum RendRequest queue size.Wesley Aptekar-Cassels2025-07-231-0/+12
| | | | | |
| * | | | | tor-hsservice: Update suggested effort in PowManager main loop.Wesley Aptekar-Cassels2025-07-231-1/+51
| | | | | |
| * | | | | tor-hsservice: Add suggested effort update function.Wesley Aptekar-Cassels2025-07-231-0/+63
| | | | | |
| * | | | | tor-hsservice: Give PowManager reference to RendRequestReceiver.Wesley Aptekar-Cassels2025-07-231-3/+8
| | | | | |
| * | | | | tor-hsservice: Allow constructing RendRequestReceiver without spawning.Wesley Aptekar-Cassels2025-07-231-19/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This will allow the PowManager to have a copy of RendRequestReceiver, which is important to allow the PowManager update loop to control the suggseted_effort updating.
| * | | | | tor-hsservice: Add state for prop362 update loop.Wesley Aptekar-Cassels2025-07-231-1/+45
| | | | | |
| * | | | | tor-hsservice: Change storage of PoW suggested_effort.Wesley Aptekar-Cassels2025-07-231-4/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This makes the suggested_effort value a Arc<RwLock<Effort>>, which is shared between the PowManager (as a reader) and the RendRequestReceiver (as a writer), since the RendRequestReceiver has the information needed to update the suggested_effort value.
| * | | | | tor-hsservice: Implement PoW queue with BTreeSet.Wesley Aptekar-Cassels2025-07-231-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The updated PoW control loop in prop362 requires this data structure to be double ended, which BinaryHeap is not. I benchmarked [email protected] against BTreeSet on a synthetic benchmark based on what I expected typical load to look like, and found that BTreeSet performed much better. It is additionally in the standard library, and is maintained, which no third-party double ended priority queue crate seems to be. Given that, BTreeSet seems like a reasonable thing to build on, although we should provide metrics on the performance of this queue so operators can let us know if it seems to be a problem in real-world use.
| * | | | | tor-hsservice: RendRequestOrdByEffort use time as tiebreaker.Wesley Aptekar-Cassels2025-07-231-5/+15
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since this will be used in a BTreeSet, we need to ensure that in practice no two requests will be equal. Ordering by a combination of effort and time received should be sufficient for this, and gives us the behaviour we want.
* | | | | Merge branch 'cgo-integration' into 'main'Nick Mathewson2025-07-2310-82/+222
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Negotiate and use CGO. Closes #1947 and #1945 See merge request tpo/core/arti!3069
| * | | | | tor-proto: Temporary measure to disable CGO.Nick Mathewson2025-07-231-1/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit prevents us from ever deciding that another relay supports CGO, which prevents us from trying to negotiate it. It also adds an assertion to make sure that we haven't tried to negotiate it. We can remove this once we're ready to have CGO turned on: right now it's blocked on being able to negotiate CC. I'm adding this so we can merge this branch (so that I can stop rebasing it.)
| * | | | | Downgrade an XXXX to a TODO.Nick Mathewson2025-07-231-1/+3
| | | | | |
| * | | | | Remove now-needless allow(unused).Nick Mathewson2025-07-231-1/+0
| | | | | |
| * | | | | Refactor/simplify HopSettings constructionNick Mathewson2025-07-232-60/+108
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We now take an enum describing whether we are doing no negotiation, HsV3 negotiation, or full negotiation. This lets us do away with the notions of default relay crypto, and of declaring post-facto that no negotiation has occurred.
| * | | | | Rename and invert the sense of requires_stream_level_sendmes.Nick Mathewson2025-07-232-5/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead call it compatible_with_cgo, which is what we actually care about in this context.
| * | | | | proto: Send extensions as appropriate to negotiate CGO.Nick Mathewson2025-07-233-1/+54
| | | | | | | | | | | | | | | | | | | | | | | | Let's see if it works!
| * | | | | proto: Construct CGO instances if that is what is selected.Nick Mathewson2025-07-232-2/+15
| | | | | |
| * | | | | proto: Take format+crypto settings from HopSettingsNick Mathewson2025-07-237-54/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since these will be negotiated (or determined as part of negotiation) they belong in HopSettings.
| * | | | | protover: Allocate a capability number for RELAY_CRYPT_CGO.Nick Mathewson2025-07-231-0/+7
| | | | | |
* | | | | | Merge branch 'ticket_2050' into 'main'Nick Mathewson2025-07-233-4/+4
|\ \ \ \ \ \ | |/ / / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Apply tcyrus's patches from #2050 Closes #2050 See merge request tpo/core/arti!3104
| * | | | | tor-llcrypto: fix typotcyrus2025-07-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `tor_llcrypto::pk::ed25519::PublicKey` is based on `ed25519_dalek::VerifyingKey` and not `ed25519_dalek::SigningKey`.
| * | | | | tor-hscrypto: fix typostcyrus2025-07-232-3/+3
|/ / / / /
* | | | | Merge branch 'add-err-variant' into 'main'gabi-2502025-07-232-2/+9
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | tor-keymgr: Add err::Error::KeystoreNotConfigured See merge request tpo/core/arti!3103
| * | | | | tor-keymgr: Add err::Error::KeystoreNotFoundhjrgrn2025-07-232-2/+9
|/ / / / /
| | * | | hyper-examples: Put private key for tests backnield2025-08-041-0/+8
| | | | | | | | | | | | | | | | | | | | This was somehow accidentally deleted.
| | * | | hyper-examples: Use native-tls instead of rustlsnield2025-07-213-198/+15
| | | | |
| | * | | hyper-examples: Delete folder remaining after rebasenield2025-07-203-50/+166
| | | | |
| | * | | Merge branch 'hyper-examples' of gitlab.torproject.org:nield/arti into ↵nield2025-07-200-0/+0
| | |\ \ \ | | | | | | | | | | | | | | | | | | hyper-examples
| | | * | | hyper-examples: Typonield2025-06-241-1/+1
| | | | | |
| | | * | | hyper-examples: rustfmtnield2025-06-241-4/+7
| | | | | |
| | | * | | hyper-examples: Clarify comment regarding `is_fully_reachable`nield2025-06-241-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | Previous comment was not clear. `is_fully_reachable` only gives false negatives, not false positives.
| | | * | | hyper-examples: Simplify code for timeoutnield2025-06-241-51/+15
| | | | | | | | | | | | | | | | | | | | | | | | We removed the while loop.
| | | * | | hyper-examples: Print messages to stderrnield2025-06-241-6/+6
| | | | | |
| | | * | | hyper-examples: Add comment why we use rustls and manual set root_certnield2025-06-241-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The reason we prefer `rustls` in this case is because `rustls` provides better portability then `native-tls` due to not being dependent on the system. We have to explicitely set the root_cert because `rustls` does not use the system CA Certs to remain portable.
| | | * | | hyper-examples: Print messages to stderrnield2025-06-241-2/+2
| | | | | |
| | | * | | hyper-examples: Allow cli argument for test-urlnield2025-06-241-1/+4
| | | | | |
| | | * | | hyper-examples: Remove hyper-custom-connector-examplenield2025-06-044-268/+3
| | | | | | | | | | | | | | | | | | | | | | | | We will make a separate library for this.
| | | * | | hyper-examples: Typonield2025-04-161-1/+1
| | | | | |
| | | * | | hyper-examples: Fix example hyper-http-hs-examplenield2025-04-161-13/+67
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This example previously remained stuck in the while loop without any output, seeming as if this example is not working. This because the method `is_fully_reachable` is no guarantee for the actual status of the onion service. It might return false while the service is actually reachable. We added a timeout to not remain stuck in the loop.
| | | * | | hyper-examples: Rename example directorynield2025-04-167-29/+29
| | | | | | | | | | | | | | | | | | | | | | | | This directory had to be renamed because otherwise it would cause conflicts with the actual hyper crate in the CI pipeline.
| | | * | | hyper-examples: Fix example hyper-http-client examplenield2025-04-161-14/+22
| | | | | | | | | | | | | | | | | | | | | | | | This example previously had errors trying to make a connection, this is solved now.
| | | * | | hyper-examples: Cargo fmtnield2025-04-161-1/+1
| | | | | |
| | | * | | hyper-examples: Add README.mdnield2025-04-151-0/+40
| | | | | |
| | | * | | hyper-examples: Remove subdirectories from examplenield2025-04-1511-132/+62
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This example directory had a separate directory for each example. We can simplify this by using binaries.
| | | * | | hyper-examples: Remove unsafe test url form hyper-http-client-examplenield2025-04-151-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | This example made a request to a website which could deanonymize the user. We now use check.torproject.org instead.
| | | * | | hyper-examples: Example creating custom ArtiHttpConnector for hypernield2025-04-154-0/+300
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This example demonstrates how to create a custom connector which can be injected into a hyper client, to use hyper for Tor requests.
| | * | | | hyper-examples: Typonield2025-07-201-1/+1
| | | | | |
| | * | | | hyper-examples: rustfmtnield2025-07-201-4/+7
| | | | | |