| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
- `tor-ptmgr` has a new `add_unmanaged` function to insert an unmanaged
PT into the `cmethods` table.
- There are many ways to misuse this API and have it blow up in your
face (for example, by overwriting an existing PT's cmethod, etc.)
- It's unclear whether these are worth caring about.
- The `TorClient` gains a new experimental `ptmgr()` function, and the
`PtClientMethod` can now be constructed by user code.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This threads the country codes work through the rest of the codebase:
- `tor-dirmgr` will now enable GeoIP with the embedded database when the
`geoip` future is enabled
- This can be extended later using the `DirMgrConfig` to allow
specifying a custom database; this is not done here, though
- `tor-circmgr`'s `SupportedCircUsage` and `TargetCircUsage` fields gain
new `country_code` members to allow filtering circuits by country
- These are `()` in builds where the `geoip` feature is not enabled --
doing it this way means we don't have to copy and paste huge swathes
of code, since we can't use `#[cfg]` in patterns
- `ExitPathBuilder` gains (hacked-in) support for choosing a relay with
the correct country code
- Due to the lack of conjuction, we just copy and paste a small bit,
pending further refactoring
- `StreamPrefs` now lets you specify a country code, letting embedders
make use of the feature
|
| |\
| |
| |
| |
| | |
tor-hsservice: Don't block the reactor on the descriptor uploads.
See merge request tpo/core/arti!1580
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Currently nothing actually calls the dumping code.
|
| |\ \
| |/
|/|
| |
| | |
Begin working on configuration logic for onion services
See merge request tpo/core/arti!1557
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |\ \
| | |
| | |
| | |
| | | |
Switch to FixedCapacityVec from crates.io
See merge request tpo/core/arti!1563
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Chrono is unmaintained, I think, and uses a version of `time` that
cargo-audit doesn't like.
|
| | | |
| | |
| | |
| | | |
Part of a solution for cargo-audit.
|
| |/ / |
|
| | |
| |
| |
| | |
(Only bump openssl-sys to 0.9.92; I'm having an issue with 0.9.93.)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These are:
```
hashx
equix
tor-async-utils
tor-error
tor-config
tor-rtmock
tor-llcrypto
tor-bytes
tor-hscrypto
tor-hspow
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-netdir
tor-chanmgr
tor-guardmgr
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
arti-client
arti
```
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
These are:
```
tor-dirclient
tor-ptmgr
```
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
| |
This partially implements the descriptor publisher reactor.
The code still has many TODOs and there are no tests.
Partially implements #977
|
| |
|
|
| |
Closes #1013.
|
| |
|
|
|
|
|
| |
Now that [ssh-key 0.6.1] is out, we no longer need the explicit sec1
dependency in tor-keymgr.
[ssh-key 0.6.1]: https://github.com/RustCrypto/SSH/pull/155
|
| | |
|
| | |
|
| |
|
|
| |
There are many TODOs and no tests, but it does compile.
|
| | |
|
| |
|
|
|
| |
This module is perhaps rather more comprehensive than needed right
now. But I found I kept wanting to change which bits of it I used.
|
| |
|
|
| |
We don't actually want to distinguish drop from not-drop.
|
| | |
|
| |
|
|
|
|
|
| |
We need a type that holds a rend_handshake::IntroRequest object
internally, but where we don't materialize that object from the
Introduce2 message inside the MsgHandler, since that's more crypto
than we want to put in that task.
|
| | |
|
| |\
| |
| |
| |
| | |
Resolve (mostly) RUSTSEC-2023-0052
See merge request tpo/core/arti!1534
|
| | | |
|
| |\ \
| |/
|/|
| |
| | |
Upgrade num_enum dependency to 0.7
See merge request tpo/core/arti!1530
|
| | | |
|
| |/
|
|
| |
to remove the use of a pre-built blob
|
| |\
| |
| |
| |
| | |
tor-hsservice errors: Introduce more error types
See merge request tpo/core/arti!1515
|
| | |
| |
| |
| | |
This is what we do elsewhere.
|
| | | |
|
| |/
|
|
|
|
|
|
|
| |
This code has most of what we need to go from an INTRODUCE2 message
we've just received to the point where we've connected to the
rendezvous point and we're waiting for a stream of BEGIN messages.
Unfinished pieces are marked with TODO HSS.
Most of #980.
|
| |\
| |
| |
| |
| | |
Write more of IptEstablisher.
See merge request tpo/core/arti!1510
|
| | |
| |
| |
| |
| | |
It now supports running in a loop, trying to establish an
introduction point, and reporting status.
|
| | | |
|
| | | |
|
| |/
|
|
| |
This brings in the changes from #936.
|
| |
|
|
|
|
|
|
| |
This should be enough now to establish real introduction points,
though there is still a lot of work to do. Part of #976.
This has been rebased and edited to incorporate discussions from
!1465.
|
| | |
|
| |
|
|
| |
We'll use this in crates/arti in a moment.
|