Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement proposal 328, relay overload in extrainfo descriptors #91

Open
juga0 opened this issue Mar 12, 2021 · 4 comments
Open

Implement proposal 328, relay overload in extrainfo descriptors #91

juga0 opened this issue Mar 12, 2021 · 4 comments

Comments

@juga0
Copy link
Contributor

juga0 commented Mar 12, 2021

tor is currently implementing the proposal and sbws would need to use that information (issue).

Would be possible that stem implements this?. Thanks!

@nmathewson
Copy link
Contributor

FWIW, I expect that the formats may change over the coming year, so it might be best to expose them for now as a (version, string) tuple rather than parsing them too deeply. Up to you though.

@atagar
Copy link
Contributor

atagar commented Mar 12, 2021

Hi Juga. Stem only integrates changes like this when the proposal has been implemented and moved to the spec. That said, if you'd care to provide a patch I'd be happy to review it.

@nmathewson
Copy link
Contributor

This is now merged in Tor 0.4.6.1-alpha.

@nusenu
Copy link

nusenu commented Nov 1, 2021

a maybe slightly misleading version got merged into the dir-spec.txt
https://gitlab.torproject.org/tpo/core/torspec/-/commit/2b0093c2c972853e5c2c6bc9e41dc83a4a2e7793
https://lists.torproject.org/pipermail/tor-dev/2021-November/014667.html

note the spec says

[Introduced in version 0.4.6.1-alpha]

for overload-general but for the server descriptor it is actually 0.4.6.2-alpha (in 0.4.6.1-alpha it was the extra-info)

https://gitlab.torproject.org/tpo/core/tor/-/issues/40364

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants