| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
| | | |
| | | |
| | | |
| | | | |
This delivers a fresh account per channel to the places where channels
are actually made, but doesn't pass them to tor-proto yet.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Plumb through a top-level account. This doesn't have any
channel-specific, circuit-specific or stream-specific accounts yet.
tor-circmgr's and tor-hsclient's *tests* need fake account.
In arti-relay, use a dummy account for now.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Making a channel is going to involve making a memquota Participant,
which can fail.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
During startup we'll call a few not-just-at-startup memquota methods
which produce tor_memquota::Error, rather than StartupError. So we
need a variant for that.
|
| | | | | |
|
| | | | | |
|
| | |/ / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Update CHANGELOG.md with more tor-circmgr 0.23.0 changes.
See merge request tpo/core/arti!2496
|
| | |/ / |
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
rpc-meta-draft: describe compatibility rules and mechanisms
See merge request tpo/core/arti!2475
|
| | | | |
|
| | | |
| | |
| | |
| | | |
AIUI they mean the same thing
|
| | | |
| | |
| | |
| | | |
From a suggestion from @diziet
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This tries to memorialize the mechanism that @diziet and I came up
with and memorialized on #1634. Once this is merged I can implement
it.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
arti-client: Clarify the launch_onion_service_with_hsid() docs.
Closes #1626
See merge request tpo/core/arti!2494
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This updates the docs to mention that the specified key may get
actually persisted to disk.
Closes #1626
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Replace references to prop351 with socks-extensions.md
Closes #1629
See merge request tpo/core/arti!2492
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Now that the proposal is implemented and merged into the specs,
the proposal itself is only historical.
Closes #1629.
|
| |\ \ \ \ \
| |_|_|_|/
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Use the new "restricted discovery" terminology throughout
Closes #1476
See merge request tpo/core/arti!2495
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This renames "client auth" to "restricted discovery" where appropriate.
Closes #1476
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This adds a note mentioning the new "restricted discovery" terminology
to the various docs that talk about client authorization.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Part of #1476
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Part of #1476
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Part of #1476
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Part of #1476
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Part of #1476
|
| | | | | | |
|
| | | |/ /
| |/| |
| | | |
| | | | |
Part of #1476
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Use {u64,usize}::div_ceil
See merge request tpo/core/arti!2473
|
| | | |_|/
| |/| |
| | | |
| | | |
| | | | |
Previously we had to avoid it, but now that our MSRV is above 1.73
we can use it with abandon.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
python: Type-annotate rpc.py
See merge request tpo/core/arti!2476
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
@opara says that we'll want to have our API functions be
`extern "C"` everywhere, and so `ctypes.CDLL` should work fine for
them on Windows. This sounds good to me.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This, incidentally, turned up a repeated mistake in the code.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Since params can be "anything encodeable to json", there isn't a lot
of point in restricting its type.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This has required a few code changes and turned up a few bugs.
The type annotations pass with `mypy`.
Notable code changes:
With type annotations, variable assignment may no longer change
the type of a variable. (I disagree with these semantics, but
here we are.)
Note that some TODOs remain: I have no clear sense how to annotate
the library type from `ctypes`, and better wrappers are needed in
some cases.
|
| | |/ / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
CircMgr: Start writing tests.
See merge request tpo/core/arti!2444
|
| | | | | | |
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
Python tool to build RPC method/type documentation.
See merge request tpo/core/arti!2479
|
| | | | | | |
|
| | | | | | |
|