| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | | | | | Merge branch 'tor-keyforge-rsa-types' into 'main' | wesleyac | 2025-09-30 | 8 | -13/+299 | |
| |\ \ \ \ \ | |_|/ / / |/| | | | | | | | | | | | | | | tor-key-forge: Add RSA key types. See merge request tpo/core/arti!3236 | |||||
| | * | | | | tor-llcrypto: Add more comments about implementation of RSA sign function. | Wesley Aptekar-Cassels | 2025-09-10 | 1 | -2/+3 | |
| | | | | | | ||||||
| | * | | | | tor-llcrypto: Add note about key size to RSA KeyPair::generate. | Wesley Aptekar-Cassels | 2025-09-10 | 1 | -0/+4 | |
| | | | | | | ||||||
| | * | | | | tor-llcrypto: Rename rsa::PrivateKey to rsa::KeyPair. | Wesley Aptekar-Cassels | 2025-09-08 | 5 | -17/+18 | |
| | | | | | | | | | | | | | | | | | | | | | As discussed with gabi on IRC today. | |||||
| | * | | | | tor-key-forge: Add RSA key types. | Wesley Aptekar-Cassels | 2025-09-08 | 6 | -9/+289 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some things I'm still considering here: * We may want to define a tor_llcrypto::pk::rsa::Signature newtype. * We likely want to rename tor_llcrypto::pk::rsa::PrivateKey to RsaKeypair. | |||||
| * | | | | | Merge branch 'doc_features_no_longer_there' into 'main' | Nick Mathewson | 2025-09-30 | 57 | -57/+57 | |
| |\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove check_doc_features and doc_auto_cfg. Closes #1514 See merge request tpo/core/arti!3294 | |||||
| | * | | | | | Remove "doc_auto_cfg" incantation from all crates. | Nick Mathewson | 2025-09-29 | 57 | -57/+57 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | This feature has been removed from nightly, in favor of doc_cfg. | |||||
| * | | | | | | Merge branch 'suppress-warnings' into 'main' | Nick Mathewson | 2025-09-30 | 2 | -3/+13 | |
| |\ \ \ \ \ \ | |_|_|/ / / |/| | | | | | | | | | | | | | | | | | Fix two clippy warnings See merge request tpo/core/arti!3295 | |||||
| | * | | | | | rpc: Suppress a clippy warning by making PossumCage used | Ian Jackson | 2025-09-30 | 1 | -2/+11 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes warning: struct `PossumCage` is never constructed warning: associated function `make_cast_table` is never used with cargo +stable clippy --locked --offline -p tor-rpcbase --all-targets Most of our builds happen with --all-features so we don't notice. In that case I think something to do with method printing:(`describe-methods`) is using things enough for the compiler not to complain. | |||||
| | * | | | | | rpc: Suppress a clippy false positive that appears with current beta | Ian Jackson | 2025-09-30 | 1 | -1/+2 | |
| | | |_|_|/ | |/| | | | ||||||
| * | | | | | Merge branch 'sort_circ_actions' into 'main' | Nick Mathewson | 2025-09-29 | 1 | -1/+48 | |
| |\ \ \ \ \ | |_|/ / / |/| | | | | | | | | | | | | | | Sort output events for next_circ_action. See merge request tpo/core/arti!3292 | |||||
| | * | | | | Sort output events for next_circ_action. | Nick Mathewson | 2025-09-29 | 1 | -1/+48 | |
| | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This sort makes it so that that blocking and unblocking are always ordered in a sensible way with respect to sending data. This might help simplify padding machines a bit. Prerequisite for #2190 | |||||
| * | | | | Merge branch 'opentelemetry' into 'main' | wesleyac | 2025-09-29 | 21 | -10/+368 | |
| |\ \ \ \ | |/ / / |/| | | | | | | | | | | | Add experimental OpenTelemetry support See merge request tpo/core/arti!3239 | |||||
| | * | | | arti: Add skip_all to instrument call. | Wesley Aptekar-Cassels | 2025-09-24 | 1 | -1/+1 | |
| | | | | | ||||||
| | * | | | arti: Make panic into error on invalid OTEL endpoint. | Wesley Aptekar-Cassels | 2025-09-24 | 1 | -3/+5 | |
| | | | | | ||||||
| | * | | | arti: Add note about OpenTelemetry data model. | Wesley Aptekar-Cassels | 2025-09-24 | 1 | -0/+3 | |
| | | | | | ||||||
| | * | | | arti: Add note about lack of filtering in OpenTelemetry layer. | Wesley Aptekar-Cassels | 2025-09-24 | 1 | -0/+3 | |
| | | | | | ||||||
| | * | | | arti: Add skip_all to instrument macro. | Wesley Aptekar-Cassels | 2025-09-24 | 1 | -1/+1 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | It's unlikely these arguments will be particularly useful, and omitting skip_all can have security implications, so it's better to avoid it to reflect good practice. | |||||
| | * | | | arti: Add more detail about OpenTelemetry in example config. | Wesley Aptekar-Cassels | 2025-09-24 | 1 | -2/+9 | |
| | | | | | ||||||
| | * | | | opentelemetry: Use humantime_serde for parsing Durations. | Wesley Aptekar-Cassels | 2025-09-24 | 1 | -0/+3 | |
| | | | | | ||||||
| | * | | | opentelemetry: Panic if configured for non-localhost HTTP endpoint. | Wesley Aptekar-Cassels | 2025-09-24 | 1 | -0/+8 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We may want to add a way to opt out of this check, if someone asks for it. Checking for "localhost" and "127.0.0.1" is not a very robust check for a loopback interface, and it's possible that there could be other situations we can't detect where HTTP is safe (private network, WireGuard tunnel, etc). But I don't expect those to be likely to come up in practice, so this should be fine for now. | |||||
| | * | | | arti: Add more info about OpenTelemetry to example config. | Wesley Aptekar-Cassels | 2025-09-24 | 1 | -2/+6 | |
| | | | | | ||||||
| | * | | | opentelemetry: Add note about lack of upstream OTLP exporter. | Wesley Aptekar-Cassels | 2025-09-24 | 1 | -0/+3 | |
| | | | | | ||||||
| | * | | | opentelemetry: Panic on mutex poison. | Wesley Aptekar-Cassels | 2025-09-24 | 1 | -8/+1 | |
| | | | | | ||||||
| | * | | | opentelemetry: Add some instrument macros. | Wesley Aptekar-Cassels | 2025-09-24 | 16 | -10/+61 | |
| | | | | | | | | | | | | | | | | | | | | | I've added these in places that are useful for the debugging that I've been doing. | |||||
| | * | | | arti: Add experimental support for OpenTelemetry. | Wesley Aptekar-Cassels | 2025-09-24 | 5 | -0/+281 | |
| | | | | | ||||||
| * | | | | netdoc parse2 tests: Avoid <String as TryFrom<Vec<u8>>> (3) | Ian Jackson | 2025-09-29 | 1 | -1/+1 | |
| | | | | | ||||||
| * | | | | netdoc parse2 tests: Avoid <String as TryFrom<Vec<u8>>> (2) (fmt) | Ian Jackson | 2025-09-29 | 1 | -2/+1 | |
| | | | | | ||||||
| * | | | | netdoc parse2 tests: Avoid <String as TryFrom<Vec<u8>>> (2) | Ian Jackson | 2025-09-29 | 1 | -2/+1 | |
| | | | | | | | | | | | | | | | | | Should fix the minimal versions test? | |||||
| * | | | | netdoc parse2 tests: Avoid <String as TryFrom<Vec<u8>>> | Ian Jackson | 2025-09-29 | 1 | -1/+1 | |
| | | | | | | | | | | | | | | | | | Should fix the minimal versions test? | |||||
| * | | | | netdoc parse2: Remove some unneeded allows | Ian Jackson | 2025-09-29 | 1 | -2/+0 | |
| | | | | | ||||||
| * | | | | netdoc parse2: Fix two clippy lints | Ian Jackson | 2025-09-29 | 2 | -1/+1 | |
| | | | | | ||||||
| * | | | | neteoc parse2: Provide Ignored value | Ian Jackson | 2025-09-29 | 3 | -1/+41 | |
| | | | | | | | | | | | | | | | | | | | | | This will be used for some bits of netdocs where dummy values now appear. | |||||
| * | | | | netdoc parse2: NetdocParseableFields: suppress errors for empty types | Ian Jackson | 2025-09-29 | 1 | -2/+10 | |
| | | | | | ||||||
| * | | | | neteoc parse2: Import earlier | Ian Jackson | 2025-09-29 | 1 | -2/+3 | |
| | | | | | | | | | | | | | | | | | | | | | This is needed if we want to use these macros in `doc`, which we're going to. | |||||
| * | | | | netdoc parse2: support `with` for rest arguemnts, and test | Ian Jackson | 2025-09-29 | 2 | -2/+18 | |
| | | | | | ||||||
| * | | | | netdoc parse2: support `with` for normal arguemnts, and test | Ian Jackson | 2025-09-29 | 2 | -7/+11 | |
| | | | | | ||||||
| * | | | | netdoc parse2: ArgumentSetMethods: take a parser function | Ian Jackson | 2025-09-29 | 2 | -13/+65 | |
| | | | | | | | | | | | | | | | | | We need this to support `with`. | |||||
| * | | | | netdoc parse2: Support with for Item parsing, comprehensive tests | Ian Jackson | 2025-09-29 | 1 | -0/+64 | |
| | | | | | ||||||
| * | | | | netdoc parse2: tests: NeedsWith type | Ian Jackson | 2025-09-29 | 1 | -3/+55 | |
| | | | | | | | | | | | | | | | | | This type will be used to test `with` attributes. | |||||
| * | | | | netdoc parse2: Support with for Item parsing | Ian Jackson | 2025-09-29 | 1 | -2/+23 | |
| | | | | | | | | | | | | | | | | | Tests will come in a moment. | |||||
| * | | | | netdoc parse2: New single_item attribute, tests | Ian Jackson | 2025-09-29 | 1 | -6/+55 | |
| | | | | | ||||||
| * | | | | netdoc parse2: New single_item attribute | Ian Jackson | 2025-09-29 | 2 | -2/+30 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | Many of the existing netdoc structs have items that are just the single argument. We don't want to turn them all into singleton tuples. Provide a macro feature for this instead. | |||||
| * | | | | netdoc parse2: Break out ITEM_VALUE_FROM_UNPARSED | Ian Jackson | 2025-09-29 | 1 | -2/+6 | |
| | | | | | | | | | | | | | | | | | This is going to get more complicated. | |||||
| * | | | | netdoc parse2: NetdocParseableFields: Fix default, and test | Ian Jackson | 2025-09-29 | 2 | -2/+9 | |
| | | | | | ||||||
| * | | | | netdoc parse2: NetdocParseableFields: introduce use of $fpatname | Ian Jackson | 2025-09-29 | 1 | -5/+4 | |
| | | | | | | | | | | | | | | | | | We're going to want to do more complex things here. | |||||
| * | | | | netdoc parse2: Run selector-based trait check for intro item too | Ian Jackson | 2025-09-29 | 1 | -2/+6 | |
| | | | | | ||||||
| * | | | | netdoc parse2: Tests for new Object handling | Ian Jackson | 2025-09-29 | 1 | -1/+85 | |
| | | | | | ||||||
| * | | | | netdoc parse2: Fix Object handling (fmt) | Ian Jackson | 2025-09-29 | 1 | -2/+4 | |
| | | | | | ||||||
| * | | | | netdoc parse2: Fix Object handling | Ian Jackson | 2025-09-29 | 7 | -42/+133 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use the standard multiplicity technique rather than the ad-hoc impl on Option. This allows us to support an ad-hoc parsing function for a field that's `Option`. Disentangle the `label` field attribute, which did both setting the label, and expecting a different parsing approach: replace it with `with`. | |||||
