[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #30726 [Core Tor/Tor]: Missing relay keys in bandwidth file spec
#30726: Missing relay keys in bandwidth file spec
-------------------------------------+-----------------------------------
Reporter: teor | Owner: (none)
Type: defect | Status: needs_revision
Priority: High | Milestone: sbws: 1.1.x-final
Component: Core Tor/Tor | Version:
Severity: Major | Resolution:
Keywords: sbws-spec, sbws-roadmap | Actual Points:
Parent ID: #33121 | Points: 6
Reviewer: ahf, gk | Sponsor:
-------------------------------------+-----------------------------------
Comment (by gk):
Replying to [comment:9 juga]:
> Replying to [comment:7 gk]:
>
> > So, all of those examples look to me like spec bugs: the right thing
happened in the code, but the spec does not reflect that and thus needs to
get updated.
>
> Yes.
> And i think the source of true for the version and when the KeyValues
appeared should be the bandwidth files published by the bwauths, because
with sbws happens that:
> - we change KeyValues
> - we change the specification version in sbws
> - we make a new sbws release (and usually bwauths have run only
releases, except longclaw a couple of times)
> - the new version spec and the KeyValues start to appear in the
bandwidth files
> - we change some more KeyValues (if there's no bwauth running a non-
released version, they're still publishing the last specification version
> - new specification change, new sbws release, bwauths update sbws
version (and therefore KeyValues and specification version)...
>
> So i should check the collector to be sure about the which keys were in
which versions
Sounds good.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30726#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs