Fix a typo in the HTTP proxy error message.

See merge request !829

Signed-off-by: David Goulet <[email protected]>

This proposal adds new syntax to the SOCKS5 username/password extension scheme,
so that requests with usernames starting with <torS0X> are now reserved.

For C tor, all we need to do is reject every username starting with <torS0X>
unless it is exactly "<torS0X>0".

Fixes #40966



Signed-off-by: David Goulet <[email protected]>

two small presentation issues in man page

See merge request !824

Implement phase 1 of Proposal 350 (remove TAP onion keys)

See merge request !822

Relay=1 is no longer supported; it corresponds to TAP.

Microdesc=3 and Desc=3 are now supported; they correspond to the ability to
handle (micro)descriptors without TAP onion keys.

All of these elements are now mandatory, so we can now simplify
our logic for making sure that they are all present or all not-present.

(Renaming them has forced me to look at every place where they are used, so I
can make sure that they are really optional now.)

Also, stop storing onion keys in microdesc_t.

(In prop350, for microdescs, we are making the body optional; the "onion-key"
entry is still mandatory, so that we can tell where microdescs begin.)

Signed-off-by: David Goulet <[email protected]>

Alexander Hansen Færøy authored Jul 21, 2023 and David Goulet committed Jun 18, 2024

This patch makes sure we clean up our version and implementation fields
in our Managed Proxy struct after each test run.

This was detected by LeakSanitizer.

See: #11101.

Alexander Hansen Færøy authored Jul 21, 2023 and David Goulet committed Jun 18, 2024

This patch adds two new keys to bridges' extra-info document:
"transport-version" and "transport-implementation".

These two new values always appear together (if one is missing, the
other one will be missing too) and is parsed from PT's STATUS
TYPE=version messages.

See: #11101.

Alexander Hansen Færøy authored Mar 24, 2022 and David Goulet committed Jun 18, 2024

This patch adds support for handling the version status message. Once we
receive such message, we add the given version string to the
managed_proxy_t instance. Note this value can be NULL and the value can
change throughout the lifetime of the PT as multiple status version
messages are handled.

See: #11101

fix sandbox for bandwidth authority

Closes #40933

See merge request !821