| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
For the expiry times for descriptors we are intending to publish, copy
out of our data structure. We don't need to actually update it to
account for (possible) imminent publication; the publisher will do
that.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
And plumb the reference through to places that will need it.
We don't actually do anything with the results yet.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
We are going to need to hold the ipt_set lock while we loop around
making changes to our data structures etc.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This should be an Option, to correspond to what's in IptSet.
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-ptmgr: Add new tests
See merge request tpo/core/arti!1579
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This commit adds a unit test that checks if an empty value is parsed
properly.
It fixes the coverage in `crates/tor-ptmgr/src/ipc.rs:120`.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This commit adds a test which checks for a missing value in an SMETHOD
argument.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This commit adds a unit test to the `tor-ptmgr` crate, which checks for
forbidden `=` signs while reading a value.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This commit adds a unit test to the `tor-ptmgr` crate, which checks if
arguments are terminated with a backslash, which is forbidden.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This commit adds a unit test that checks if all octal escape sequences
are treated as an unsupported error.
|
| | |/ /
| | |
| | |
| | |
| | | |
This commit adds a test to the `tor-ptmgr` crate, which increases the
test coverage by checking for escape sequences in values.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
maint/bump_nodep: Two changes to help it work in my environment
See merge request tpo/core/arti!1573
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Sadly the environment I ran this command on today didn't have
"git restore". I should upgrade it but there are yaks, and I may
not have managed to upgrade it by *next* Arti release.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is a more convenient approach to command overriding. It's what
we do elsewhere. I need this because with a script like
"maint/bump_nodep", which edits the tree, I need to write
CARGO='nailing-cargo -E' maint/bump_nodep ....
(The -E option tells my privsep tool that the command is *supposed* to
edit the tree - and that I am intending to review those changes.)
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
Begin working on configuration logic for onion services
See merge request tpo/core/arti!1557
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Don't make people say "Dangerous!" in the configuration, document
the formats, and make the strings case-insensitive.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Also, allow nonempty ranges starting with 0- and implement Eq and
PartialEq.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Note a few issues encountered while doing so.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For rate-limiting, we make it optional. If it isn't set, we don't
tell the intro to rate-limit.
We condense our two max-streams options into one. We had two
options here because we were looking for feature parity with C, but
I think I had misunderstood what C provides.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-hsservice: Use the new IPT change notifier API.
See merge request tpo/core/arti!1576
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The reactor events are no longer received on the same channel, so we
don't need the `Event` enum or the old `Publisher` APIs any more.
Svc config changes are received on a wseparate `postage::watch` channel,
whereas IPT changes are detected through the `IptsPublisherView`.
The publisher will (eventually) be informed of keystore changes through
another `postage::watch` channel.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
If multiple config changes happen in quick succession, we don't want the
publisher to publish a new descriptor for every single one.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This makes the publisher watch for IPT changes using the
`IptsPublisherView` added in arti#1023 (instead of waiting for an
`Event::NewIntroPoints`. The `Event` enum will soon be replaced by
multiple `postage::watch` channels, one for every type of change it
needs to react to).
|
| | | | | |
|