summaryrefslogtreecommitdiff
path: root/crates/tor-netdoc/semver.md
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'relay-flags-options-trait' into 'main'Ian Jackson2025-11-251-1/+1
|\ | | | | | | | | tor-netdoc: Parameterise RelayFlagsParser by an options trait instead See merge request tpo/core/arti!3489
| * tor-netdoc: Rename RelayFlagsParser to relay_flags::ParserIan Jackson2025-11-241-1/+1
| | | | | | | | | | | | | | Since we expose the relay_flags module, it makes sense to give this a shorter name. (It had a longer name when it was part of the netstatus module.)
* | semver.md: Document change to parse2::MultiplicitySelectorIan Jackson2025-11-241-0/+1
|/
* Merge branch 'pub-encode' into 'main'Ian Jackson2025-11-191-0/+1
|\ | | | | | | | | tor-netdoc: Make much more of encode module public See merge request tpo/core/arti!3471
| * tor-netdoc: Make much more of the encode module contents publicIan Jackson2025-11-181-0/+1
| | | | | | | | | | My planned new derive for encoding will be pub, but cfg gated, like parse2 is.
* | tor-netdoc: document RelayFlags changesIan Jackson2025-11-181-2/+3
|/
* tor-netdoc: semver.md updates for RelayFlags overhaulIan Jackson2025-11-181-0/+6
|
* maint: remove all semver.md filesSteven Engler2025-10-301-25/+0
|
* tor-netdoc: impl ItemArgumentParseable for IgnoredIan Jackson2025-10-231-0/+1
| | | | Change our mind about the logic for encoding an Ignored.
* tor-netcoc: Introduce NotPresent, for absent multiplicityIan Jackson2025-10-231-0/+2
| | | | | | | | | Currently this is mishandled: the current use sites (in rs/each_variety.rs) use Option<Ignored>, which would reject repeated items with that keyword, which is technically wrong. And encoing will become a problem. Vec<Ignored> would be wrong too. Instead, broaden NotPresent and give it multiplicity impls.
* tor-netdoc: Document new feature in semver.mdIan Jackson2025-10-221-0/+1
|
* tor-netdoc: Preamble: rename relay_version field to server_versionIan Jackson2025-10-221-0/+1
| | | | This makes it match the protocol and the spec.
* tor-netdoc: Document breaking changes in semver.mdIan Jackson2025-10-221-0/+2
|
* tor-netdoc: Change type of timestamp in SharedRandStatusIan Jackson2025-10-211-0/+1
|
* tor-netdoc: B64 helper type: ExposeIan Jackson2025-10-151-0/+1
|
* tor-netdoc: Provide convenience method for handling invalid argumentsIan Jackson2025-10-151-0/+1
|
* tor-netdoc: Expose Iso8601TimeNoSp and Iso8601TimeSp utility wrappersIan Jackson2025-10-091-0/+1
| | | | We're going to want to change some now-public fields to use these types.
* tor-netdoc: parse2: Add column field to PaarsError and print itIan Jackson2025-10-091-0/+1
|
* tor-netdoc: parse2: Add .column() accessor to ErrorProblemIan Jackson2025-10-091-0/+1
| | | | We'll want to general way to find the error problem column.
* tor-netdoc: parse2: Add column field as far as ErrorProblemIan Jackson2025-10-091-0/+1
| | | | | | | Provide facilities in ArgumnetStream for determining the column, and add the field to all the error types up to and including ErrorProblem. The value still needs to be propagated to ParseError, and printed there.
* tor-netdoc: Abolish now-obsolete field argument to from_argsIan Jackson2025-10-091-0/+1
|
* tor-netdoc: Introduce ArgumentErrorIan Jackson2025-10-091-0/+2
| | | | | This will allow us to (1) move field name handling out of the argument parser method, and also (2) add columns more easily.
* tor-netdoc: Have .reject_extra_args return a bespoke errorIan Jackson2025-10-091-0/+1
| | | | | | | We're about to have some functions return ArgumentError and some ErrorProblem. We don't want to provide a conversion directly between these types, so instead introduce a new type that will be convertible to either.
* tor-netdoc: UnparsedItem: Provide .args() accessorIan Jackson2025-10-091-0/+1
|
* tor-netdoc: parse2: Rename methods on ArgumentStreamIan Jackson2025-10-091-1/+1
|
* tor-netdoc: Add semver.md for parsing/printing changesIan Jackson2025-10-081-0/+4
|
* tor-netdoc: RouterStatus: unify `orport_addrs` and `addrs` methodsIan Jackson2025-10-061-0/+2
| | | | | | | We had two functions with different return types but identical semantics. Replace them with one function returning `impl Iterator`. Make it return owned addresses. These are small.
* release: Remove old semver.md files.Wesley Aptekar-Cassels2025-10-021-2/+0
|
* tor-netdoc: Abolish `dangerous-expose-struct-fields`; always expose, insteadIan Jackson2025-10-011-0/+2
| | | | Fixes #2192
* Remove semver.md filesNick Mathewson2025-08-281-6/+0
|
* tor-netdoc: Add semver notes for these changesIan Jackson2025-08-261-0/+3
| | | | | I don't really see any way to make this less painful for downstreams, so I haven't added compatibility aliases of any kind.
* tor-netdoc: Replace "ns" with "plain" for unflavoured consensusesIan Jackson2025-08-181-1/+3
|
* tor-netdoc: Rename ns-consensus to plain-consensusIan Jackson2025-08-181-1/+1
| | | | | | ns-consensus doesn't seem to have ever been released. This is part of abolishing the use of "ns" to mean "plain".
* tor-netdoc: Change feature name to `ns-consensus` with a hyphenIan Jackson2025-08-181-0/+1
| | | | | | | Our features are generally kebab-case, and this is the way it's documented. Retain the old name for compatibility.
* Remove semver.md files post-release.Gabriela Moldovan2025-04-011-1/+0
|
* netdoc: Make some parsing init functions fallible.Nick Mathewson2025-03-171-0/+1
| | | | | | | I'm about to make our parsers reject some strings at construction time, so it makes sense to have these functions become fallible. This is a breaking change.
* Remove all semver.md files to start a fresh release roundIan Jackson2024-02-051-1/+0
|
* semver note.Nick Mathewson2024-01-161-0/+1
|
* Remove pending semver entriesarti-v1.1.12Nick Mathewson2024-01-091-1/+0
|
* tor-netdoc: Make HsDescBuilder::auth_clients take an Option.Gabriela Moldovan2023-12-141-0/+1
| | | | Closes #1019
* Remove semver.md files from arti 1.1.10Nick Mathewson2023-10-311-5/+0
|
* tor-netdoc: Use the new HandshakeType enum to represent CREATE2 HTYPEs.Gabriela Moldovan2023-10-301-0/+1
| | | | | | | | | | | Representing the supported HTYPEs as `HandshakeType`s instead of `u32`s makes it more difficult to pass in wrong/invalid values to `HsDescBuilder::create2_formats`. This also fixes a descriptor publisher bug spotted by @jnewsome, where the advertised CREATE2 HTYPEs included HTYPE `1`, which is actually supposed to be a reserved value. The publisher now only advertises the `NTOR` HTYPE (just like C Tor).
* tor-netdoc: Building a descriptor now only requires the public part of ↵Gabriela Moldovan2023-10-251-0/+1
| | | | blinded_id.
* tor-netdoc: Update HsDesc, HsDescOuter to accept the hs_desc_sign cert as an ↵Gabriela Moldovan2023-10-251-0/+2
| | | | | | | | | | argument. This will enable us to (eventually) the load the descriptor signing key cert from the keystore (as opposed to always recomputing it when building the `HsDesc`). Part of #1048
* tor-netdoc: Add helper function for computing the descriptor signing key cert.Gabriela Moldovan2023-10-251-0/+1
|
* Remove semver.md files now that 1.1.9 is out.Nick Mathewson2023-10-021-2/+0
|
* tor-hsclient, arti-client, tor-keymgr, tor-netdoc: Use a keypair instead of ↵Gabriela Moldovan2023-09-251-0/+2
| | | | | | | | | | | | | StaticSecret. Previously, when retrieving `KS_hsc_desc_enc` keys (or any other x25519 keys) from the keystore, the keymgr would discard the public part of the key (SSH private keys contain the public part of the key too). Instead of discarding the public key and returning just the `StaticSecret`, the keymgr now returns a `StaticKeypair`. This makes the x25519 `EncodableKey`/`ToEncodableKey` implementation consistent with the ed25519 one (which retrieves key pairs rather than "unescorted" secrets).
* Remove semver.md files for 1.1.6Nick Mathewson2023-06-301-2/+0
|
* netdir: Move voting_period() to netdoc::LifetimeNick Mathewson2023-06-291-1/+1
| | | | | I was going to add a comment about "doing this if we need the voting period anywhere else" but it turns out that we also use it in dirmgr.
* netdir, netdoc: Add accessors for protocol version status.Nick Mathewson2023-06-061-0/+2
| | | | | | | | | | | The consensus includes a listing for clients and for relays, saying which protocol versions are _required_ for participation on the network, and which versions are _recommended_. We have been parsing this, but not yet exposing it. This commit adds accessors to expose it, since we'll need that in order to create CircTargets for introduction points and rendezvous points.