| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
| | | |
| | | |
| | | |
| | | | |
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).
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Switch to FixedCapacityVec from crates.io
See merge request tpo/core/arti!1563
|
| | | | | | |
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
Rebased attempt to merge gsoc2023 examples
See merge request tpo/core/arti!1574
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
We don't use "log" but some dependency of one of our examples does.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Chrono is unmaintained, I think, and uses a version of `time` that
cargo-audit doesn't like.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Part of a solution for cargo-audit.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We have automatic support for "OR", but we can't do anything
automated with AND, since the intersection of licenses can get
complicated. So we just have to authorize the specific combinations
that exist. This is used by matchit, which is used in the gotlou's
examples.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
With permission from gotlou; see discussion at
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1556
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|