[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #23391 [Metrics/Metrics website]: Add changes section to Tor bridge descriptors specification
#23391: Add changes section to Tor bridge descriptors specification
-------------------------------------+------------------------------
Reporter: karsten | Owner: metrics-team
Type: enhancement | Status: needs_review
Priority: Medium | Milestone:
Component: Metrics/Metrics website | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------+------------------------------
Comment (by iwakeh):
Yes, it is important to have such a change description/listing.
To have a more complete changelog more items should be included. From the
simple [https://gitweb.torproject.org/collector.git/log/?qt=grep&q=sani
git search]:
* Retain padding-counts lines when sanitizing descriptors.
Karsten Loesing 2017-05-11
* Retain hidserv-* lines when sanitizing descriptors. Karsten
Loesing 2016-11-23
* Sanitize TCP ports in bridge descriptors. Karsten Loesing
2016-09-18
* Sanitize bridge descriptors with ed25519 lines. Karsten Loesing
2015-06-13
* Parse "published" lines from bridge statuses. Karsten Loesing
2014-10-13
* Clarify ntor-onion-key lines and @type versions. Karsten
Loesing 2014-06-10
* ...
CollecTor's [https://gitweb.torproject.org/collector.git/tree/CHANGELOG.md
changelog] is also a source for change info.
Maybe, there's a way to automate the list? All bridge desc sanitation
related changes in a release tag without test related commits ...
Well, at least a source for adding historical changes manually.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23391#comment:3>
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