summaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
...
* tor-keymgr: Use ParsedEd25519Cert when decoding certs.Gabriela Moldovan2025-01-133-12/+13
| | | | | | | This helps us get rid of our uses of `KeyUnknownCert`. Needed because `KeyUnknownCert` can't readily be converted back to `EncodedEd25519Cert` (while `ParsedEd25519Cert` *can* -- see the `certs` module from `tor-relay-crypto`).
* tor-relay-crypto: Use the new cert_type() function to get the cert type.Gabriela Moldovan2025-01-131-2/+8
|
* tor-relay-crypto: Use the high-level cert types instead of EncodedEd25519Cert.Gabriela Moldovan2025-01-131-2/+4
| | | | | | | This will come in handy later on, when we start using these function in conjunction with `KeyMgr::get_or_generate_key_and_cert`, which expects the `make_certificate` callback to return a type that implements `ToEncodableCert`.
* tor-relay-crypto: Implement ToEncodableCert for the relay cert types.Gabriela Moldovan2025-01-132-0/+92
| | | | Closes #1777
* tor-relay-crypto: Add high-level cert types.Gabriela Moldovan2025-01-132-1/+41
| | | | | | These will be the `ToEncodableCert`s we write to the keystore. Part of #1777
* tor-key-forge: Implement ItemType for ParsedEd25519Cert.Gabriela Moldovan2025-01-131-0/+9
| | | | | This will enable us to retrieve it from the keystore as an `ErasedKey` (side note, we should rename `ErasedKey` to `ErasedItem`).
* tor-key-forge: Add wrappers for various cert types.Gabriela Moldovan2025-01-132-3/+115
|
* tor-key-forge: Fill out the InvalidCertError type.Gabriela Moldovan2025-01-132-1/+20
| | | | We'll soon use this.
* tor-cert: Add experimental API for building EncodedEd25519Certs.Gabriela Moldovan2025-01-131-0/+17
| | | | | | | | | | | | | | | | This will enable us to deserialize byte slices as `EncodedEd25519Certs`. Needed because this type will be used to representing a parsed + validated cert retrieved from the keystore. Technically, we *could* do without this function by defining a separate newtype wrapper over `Vec<u8>` to represent the validated cert data, but IMO adding a second encoded ed25519 cert type in another crate might be confusing later down the line (because the two types will be nearly identical, and are bound to eventually diverge in terms of API and implementation). Part of #1137
* tor-keymgr: Fix cert handling tests.Gabriela Moldovan2025-01-133-25/+64
| | | | | | This updates and reenables the cert management tests. Part of #1768
* tor-key-forge: Fix typo in doc comment.Gabriela Moldovan2025-01-131-1/+1
|
* tor-cert: Remove no-longer-needed experimental API.Gabriela Moldovan2025-01-131-12/+0
| | | | Part of #1768
* tor-keymgr: Use Ed25519Cert::decode to parse the certs.Gabriela Moldovan2025-01-134-4/+18
|
* tor-keymgr: Add cert parse error variant.Gabriela Moldovan2025-01-134-2/+20
| | | | | | | This will soon be used, when we modify the `ArtiNativeKeystore` cert lookup code to actually parse certificates before returning them. Part of #1768
* tor-key-forge: Add ItemType impl for KeyUnknownCert.Gabriela Moldovan2025-01-131-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `KeyUnknownCert` will soon be used as the `ToEncodableCert::ParsedCert` type for Tor ed25519 certs. For example, the `ToEncodableCert` impl for `RelaySigningKeyCert` will look like this: ```rust pub struct RelaySigningKeyCert(EncodedEd25519Cert); impl ToEncodableCert<RelaySigningKeypair> for RelaySigningKeyCert { type ParsedCert = KeyUnknownCert; type EncodableCert = EncodedEd25519Cert; type SigningKey = RelayIdentityKeypair; fn validate( cert: Self::ParsedCert, subject: &RelaySigningKeypair, signed_with: &Self::SigningKey, ) -> Result<Self, InvalidCertError> { // TODO: validate `KeyUnknownCert` // and convert it to an EncodedEd25519Cert // (we don't yet an easy way to perform this conversion) } fn to_encodable_cert(self) -> Self::EncodableCert { self.0 } } ```
* tor-key-forge: Split out ItemType as a separate trait.Gabriela Moldovan2025-01-137-28/+57
| | | | | | | | This is necessary because `ParsedCert`s will not be `EncodableItem`s. This is because we cannot (and don't want to) write certificates that have not yet been validated to the keystore. They do need to be retrievable from the keystore though, so we also change `ErasedKey` to be `Box<dyn ItemType>` instead.
* tor-key-forge: Distinguish between parsed certs and encodable certs.Gabriela Moldovan2025-01-132-12/+16
| | | | | | | | | | | | | | | We need two different types to represent * certs that have been parsed, but not yet validated (`KeyUnknownCert`) * newly generated encodable certs (`EncodedEd25519Cert`) Currently, we don't use `KeyUnknownCert` anywhere, and instead use `EncodedEd25519Cert` to represent "parsed" but not-yet-validated certs. This approach is wrong and relies on a broken (no-op) `EncodedEd25519Cert::from_bytes` implementation. A future commit will address this problem by replacing `EncodedEd25519Cert::from_bytes` with `Ed25519Cert::decode` to actually parse the cert upon retrieving it from the keystore.
* tor-keymgr: Replace from_encodable_cert with validation function.Gabriela Moldovan2025-01-132-22/+7
| | | | | | | | In practice, we won't be able to obtain an `ToEncodableCert` type from an `EncodableItem` cert without validating it first, so we need to collapse `validate` into `from_encodable_cert`. Part of #1768
* tor-key-forge: Export some additional tor-cert types.Gabriela Moldovan2025-01-131-3/+3
| | | | This will soon be used.
* arti-relay: don't use environment var in `Mistrust`Steven Engler2025-01-132-26/+4
|
* arti-relay: remove `TorRelayConfigBuilder::from_directories`Steven Engler2025-01-131-27/+0
| | | | | I don't think we'll ever need this. Users will set the directories through the config file.
* arti-relay: add basic placeholder loggerSteven Engler2025-01-131-4/+61
| | | | | This is probably not what the final logger would look like, but it's a fine placeholder for now.
* arti-relay: add config loadingSteven Engler2025-01-132-13/+47
|
* arti-relay: make `main` a wrapper around a `main_main`Steven Engler2025-01-132-1/+15
| | | | This makes it more similar to arti.
* arti-relay: add `LoggingConfig`Steven Engler2025-01-132-0/+41
|
* arti-relay: rework default config file path handlingSteven Engler2025-01-131-15/+91
|
* arti-relay: add constant `ARTI_FS_DISABLE_PERMISSION_CHECKS`Steven Engler2025-01-131-0/+24
| | | | We don't actually use it yet, but we do show it in the '--help' text.
* arti-relay: `TorRelay` takes a `CfgPathResolver`Steven Engler2025-01-132-8/+20
|
* arti-relay: remove relay builderSteven Engler2025-01-133-71/+8
| | | | | | | This is a bunch of boilerplate code that we don't currently need, and may not need in the future since we don't need to provide a lot of library-API-level customization for `TorRelay` like we do with `TorClient`.
* arti-relay: default config paths now use path resolverSteven Engler2025-01-133-12/+21
|
* arti-relay: added a base `CfgPathResolver`Steven Engler2025-01-132-5/+124
|
* arti-relay: impl `TopLevel` for `TorRelayConfig`Steven Engler2025-01-131-0/+4
|
* arti-relay: added `From<LogLevel> for tracing::metadata::Level`Steven Engler2025-01-131-1/+13
|
* arti-relay: make cli `log_level` an `Option`Steven Engler2025-01-131-4/+3
| | | | This is an override option, which we want to default to "unset".
* arti-relay: test that global cli options have "global" setSteven Engler2025-01-131-1/+16
|
* arti-relay: moved global cli options to common structSteven Engler2025-01-131-16/+24
|
* Merge branch 'rpc-banner' into 'main'Nick Mathewson2025-01-095-8/+53
|\ | | | | | | | | | | | | RPC spec: specify banner format. Closes #1753 See merge request tpo/core/arti!2700
| * Implement banner for RPC protocol.Nick Mathewson2025-01-095-8/+53
| | | | | | | | Closes #1753
* | tor-config: Test that uninteresting events get ignored.Gabriela Moldovan2025-01-091-3/+21
| |
* | tor-config: Rewrite match for readability.Gabriela Moldovan2025-01-091-3/+5
| | | | | | | | Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2696#note_3145971
* | tor-config: Avoid using EventKind::Any in the tests.Gabriela Moldovan2025-01-091-3/+4
| | | | | | | | Events of type `Any` now get discarded by the event handler.
* | tor-config: Handle rescan events before filtering.Gabriela Moldovan2025-01-091-3/+2
| | | | | | | | | | This enables us to catch "rescan" events, regardless of their underlying `EventKind`.
* | tor-config: Make the `FileWatcher` ignore non-mutating file events.Gabriela Moldovan2025-01-091-1/+13
| | | | | | | | | | | | | | | | Without this, setting `watch_configuration = true` results in endless config reloading due to arti accessing the config (which triggers an access event, which in turn, triggers a config reload, and so on). Closes #1794
* | tor-proto: fix bad indentationSteven Engler2025-01-091-3/+3
| |
* | tor-proto: test `Channel::wait_for_close`Steven Engler2025-01-091-5/+35
| |
* | tor-proto: make `Channel::wait_for_close` non-experimentalSteven Engler2025-01-091-1/+0
| |
* | tor-proto: `Channel::wait_for_close` return success statusSteven Engler2025-01-092-14/+42
|/ | | | | | This had a TODO about returning a "status indication instead of just ()" so this commit adds some status indication that we can expand later if needed.
* tor-circmgr: Add trace log on circuit build timeout.Wesley Aptekar-Cassels2025-01-081-0/+2
| | | | This may help debugging #1792.
* tor-rtcompat: Note that SpawnBlocking isn't for CPU-bound tasks.Wesley Aptekar-Cassels2025-01-071-1/+1
|
* tor-rtcompat: Use GAT instead of RPIT in SpawnBlocking trait.Wesley Aptekar-Cassels2025-01-077-9/+25
| | | | Due to the limitations on RPIT, it's better to use a GAT for now.
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-27 16:41:54 +0000