| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This crate doesn't have a meaningful public API, so it just gets a patchlevel bump:
arti
These crates had nonbreaking changes, and get a patchlevel bump:
tor-rtcompat
fs-mistrust
tor-llcrypto
tor-cert
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These crates have breaking changes on their own:
tor-error
tor-netdoc
tor-dirmgr
tor-keymgr
Because of the breaking change in tor-error, and the fact that
basically every crate publicly depends on tor-error (by implementing
ErrorKind), we need to call this a breaking change on all of the
following:
tor-config
tor-geoip
tor-rtmock
tor-log-ratelim
tor-rpcbase
tor-bytes
tor-hscrypto
tor-socksproto
tor-cell
tor-proto
tor-netdoc
tor-netdir
tor-persist
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
arti-client
arti-rpcserver
arti-config
arti-hyper
arti-testing
|
| |\
| |
| |
| |
| | |
Run fixup-features in preparation for release, and clean its output.
See merge request tpo/core/arti!1856
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
KeySpecifier improvements
Closes #1126, #1147, and #1151
See merge request tpo/core/arti!1851
|
| | |
| |
| |
| |
| | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1851#note_2981473
|
| | |
| |
| |
| |
| |
| |
| | |
Swap the docs for new_any and arti_pattern to the right methods!
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1851#note_2981475
|
| | | |
|
| | |
| |
| |
| | |
This *is* the spec name.
|
| | |
| |
| |
| | |
Finishes arti#1151 item 10.
|
| | |
| |
| |
| | |
This also passes the information we'll need to populate extra_info.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
This will make the macro work if call sites rebind Result.
|
| | |
| |
| |
| |
| | |
The KeyInfoExtractor impl is still misindented but we'll change that
when we replace it.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Now the only place that knows how to do all this is the one place in
the macro.
The indentation is -4 compared to previously, because we're going to
remove the wrapping with paste::paste! later. It's convenient to do
this reindent now, while we're rewriting it.
arti#1151 item 5.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This can only happen if we tried to parse an ArtiPath as the wrong
kind of KeySpecifier, which shouldn't happen very often.
If it does, the pattern isn't that interesting. Which is just as
well, since we're about to make it a bit harder to obtain it in the
place where this error is going to be constructed.
|
| | |
| |
| |
| |
| |
| | |
Where we wanted this, use derive_more::Constructor isntead.
arti#1151 item 6.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
So now .arti_pattern() is a trait method.
arti#1151 item 3.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
arti_prefix is no longer used. Abolish prefix too.
arti#1151 item 7.
Closes #1147.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This is a better API. The implementation has less monomorphisation.
arti#1151 item 2 and the patterns part of 4.
Closes #1126.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This reduces monomorphisation.
arti#1151 item 4.
The commentary reflects a decision not to do arti#1151
item 9 (using fmt signature for to_component) at this time.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Part of arti#1151 item 10.
Discussion in
https://gitlab.torproject.org/tpo/core/arti/-/issues/1151#note_2977278
|
| | |
| |
| |
| | |
This is going to expand and gain private helper methods.
|
| | |
| |
| |
| |
| | |
We don't handle enums and we don't want to try.
Put this here as documentation of this intent.
|
| | |
| |
| |
| | |
arti#1151 item 1.
|
| | |
| |
| |
| | |
Now d-a #27 is fixed, we don't need this.
|
| |/
|
|
|
| |
As recommended in the d-a changelog, I'm not calling this a breaking
change to our APIs.
|
| | |
|
| |
|
|
|
| |
I'm not sure about this. Leaving it this way seems the most
conservative choice for now.
|
| | |
|
| | |
|
| |
|
|
| |
Diziet addressed these in #1049
|
| |
|
|
|
|
|
|
|
| |
Note: any existing x25519 or expanded ed25519 keys you might have in the
keystore will become invalid (your keystore will appear corrupt, so you
will need to manually delete them if you want to continue using the
onion service they were originally generated for).
Part of #1108
|
| |
|
|
|
|
|
|
|
| |
The sub_builder pattern changes `StorageConfigBuilder` so that
instead of holding an `Option<ArtiNativeKeystoreConfig>`,
it holds an `ArtiNativeKeystoreConfigBuilder`.
This makes it a little more ergonomic to use from Rust,
and lets us use defaults for the builder fields so that we
can make them optional in our configuration.
|
| | |
|
| | |
|
| |
|
|
| |
This makes this like the list for ArtiPath.
|
| |
|
|
| |
That would allow construction of invalid paths.
|
| |
|
|
|
|
|
|
|
| |
Test that the FromStr and TryFrom impls give the same answers as
new().
These tests dodn't even compile before
Properly validate in FromStr
because the derive-more generated version has a wrong error type.
|
| |
|
|
|
|
|
| |
As pointed out in
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1796#note_2974513
derive-more just parses like the inner type, so an unvalidated String.
That is wrong.
|
| |
|
|
| |
Now ArtiPath too is TryFrom<String> and AsRef<str>.
|
| |
|
|
| |
This makes it more like ArtiPathComponent and will allow more unification
|
| | |
|
| |
|
|
|
|
| |
Rename VALID_ARTI_PATH_COMPONENTS from _PATHS. These are tested for
validity as components. I want to add a test for a multi-component
path, so make a place to put it.
|