DescripTor 1.2.0 is released
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello devs, I just released DescripTor 1.2.0: https://dist.torproject.org/descriptor/1.2.0/ - From the change log: # Changes in version 1.2.0 - 2016-05-31 * Medium changes - Include the hostname in directory source entries of consensuses and votes. - Also accept \r\n as newline in Torperf results files. - Make unrecognized keys of Torperf results available together with the corresponding values, rather than just the whole line. - In Torperf results, recognize all percentiles of expected bytes read for 0 <= x <= 100 rather than just x = { 10, 20, ..., 90 }. - Rename properties for overriding default descriptor source implementation classes. - Actually return the signing key digest in network status votes. - Parse crypto parts in network status votes. - Document all public parts in org.torproject.descriptor and add an Ant target to generate Javadocs. * Minor changes - Include a Torperf results line with more than one unrecognized key only once in the unrecognized lines. - Make "consensus-methods" line optional in network statuses votes, which would mean that only method 1 is supported. - Stop reporting "-----END .*-----" lines in directory key certificates as unrecognized. - Add code used for benchmarking. In particular the full rewrite of Javadocs was painful but hopefully useful to people here, not necessarily just DescripTor users but anyone working with Tor network data. Here's the compiled web version until DescripTor has its own website: https://people.torproject.org/~karsten/volatile/descriptor-docs-2016-05-31/ Many thanks to iwakeh for helping with most of these changes! All the best, Karsten -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJXTeNUAAoJEC3ESO/4X7XB208IAKwyJF2jgjvuREfYKkI9UFva ZoMbXgITXfTNJ4hXSc5x30jMw56xVummaWMMgBKwscPyhJAdngUjxQt//8ZOwFx/ hezHbRGxxRZquiROvIMW1mLIfnvSnkZAVL6tPuQmiKfqcR2ExMs3KCZsdCcfI/KR ZB9tHnGsSqhME+XPxQNAhT/OgBNnaq4Y7WFMhLuOHDm4/sCIjeoeix8aF1ve27ue FdOvaxjY1iBipxNdKkup5SXmL1tBmQ7bwTV59EduLatq+30tMnE7Xyat9MeQMyGI Bs9/5h+f29zREzyPp6kPd/m0eN1udvXF8nqa34QqAk0YHECE1BoIRDRo7qkixx4= =xs8m -----END PGP SIGNATURE-----
Hi Karsten, congrats on the release! I gotta admit, first thing I wondered when I saw this was 'what is DescripTor and why does it have a name that will be so easily confused with the documents it fetches?'. Quick peek at the readme seems to indicate this is the DirPort fetching capabilities of metrics-lib? Is this an effort to slit metrics-lib up into smaller libraries? Cheers! -Damian On Tue, May 31, 2016 at 12:17 PM, Karsten Loesing <karsten@torproject.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello devs,
I just released DescripTor 1.2.0:
https://dist.torproject.org/descriptor/1.2.0/
- From the change log:
# Changes in version 1.2.0 - 2016-05-31
* Medium changes - Include the hostname in directory source entries of consensuses and votes. - Also accept \r\n as newline in Torperf results files. - Make unrecognized keys of Torperf results available together with the corresponding values, rather than just the whole line. - In Torperf results, recognize all percentiles of expected bytes read for 0 <= x <= 100 rather than just x = { 10, 20, ..., 90 }. - Rename properties for overriding default descriptor source implementation classes. - Actually return the signing key digest in network status votes. - Parse crypto parts in network status votes. - Document all public parts in org.torproject.descriptor and add an Ant target to generate Javadocs.
* Minor changes - Include a Torperf results line with more than one unrecognized key only once in the unrecognized lines. - Make "consensus-methods" line optional in network statuses votes, which would mean that only method 1 is supported. - Stop reporting "-----END .*-----" lines in directory key certificates as unrecognized. - Add code used for benchmarking.
In particular the full rewrite of Javadocs was painful but hopefully useful to people here, not necessarily just DescripTor users but anyone working with Tor network data. Here's the compiled web version until DescripTor has its own website:
https://people.torproject.org/~karsten/volatile/descriptor-docs-2016-05-31/
Many thanks to iwakeh for helping with most of these changes!
All the best, Karsten
-----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJXTeNUAAoJEC3ESO/4X7XB208IAKwyJF2jgjvuREfYKkI9UFva ZoMbXgITXfTNJ4hXSc5x30jMw56xVummaWMMgBKwscPyhJAdngUjxQt//8ZOwFx/ hezHbRGxxRZquiROvIMW1mLIfnvSnkZAVL6tPuQmiKfqcR2ExMs3KCZsdCcfI/KR ZB9tHnGsSqhME+XPxQNAhT/OgBNnaq4Y7WFMhLuOHDm4/sCIjeoeix8aF1ve27ue FdOvaxjY1iBipxNdKkup5SXmL1tBmQ7bwTV59EduLatq+30tMnE7Xyat9MeQMyGI Bs9/5h+f29zREzyPp6kPd/m0eN1udvXF8nqa34QqAk0YHECE1BoIRDRo7qkixx4= =xs8m -----END PGP SIGNATURE----- _______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Damian, On 02/06/16 17:58, Damian Johnson wrote:
Hi Karsten, congrats on the release! I gotta admit, first thing I wondered when I saw this was 'what is DescripTor and why does it have a name that will be so easily confused with the documents it fetches?'.
Oh, it always had two names, metrics-lib and DescripTor. We have been referring to it as DescripTor lately, that's why I used that name in the announcement. But it's the same thing.
Quick peek at the readme seems to indicate this is the DirPort fetching capabilities of metrics-lib? Is this an effort to slit metrics-lib up into smaller libraries?
No, same thing. The DirPort fetching in DescripTor/metrics-lib is actually something that doesn't work so well, which is why CollecTor uses its own code for that. There are no plans to split up metrics-lib at this point. All the best, Karsten
Cheers! -Damian
On Tue, May 31, 2016 at 12:17 PM, Karsten Loesing <karsten@torproject.org> wrote: Hello devs,
I just released DescripTor 1.2.0:
https://dist.torproject.org/descriptor/1.2.0/
From the change log:
# Changes in version 1.2.0 - 2016-05-31
* Medium changes - Include the hostname in directory source entries of consensuses and votes. - Also accept \r\n as newline in Torperf results files. - Make unrecognized keys of Torperf results available together with the corresponding values, rather than just the whole line. - In Torperf results, recognize all percentiles of expected bytes read for 0 <= x <= 100 rather than just x = { 10, 20, ..., 90 }. - Rename properties for overriding default descriptor source implementation classes. - Actually return the signing key digest in network status votes. - Parse crypto parts in network status votes. - Document all public parts in org.torproject.descriptor and add an Ant target to generate Javadocs.
* Minor changes - Include a Torperf results line with more than one unrecognized key only once in the unrecognized lines. - Make "consensus-methods" line optional in network statuses votes, which would mean that only method 1 is supported. - Stop reporting "-----END .*-----" lines in directory key certificates as unrecognized. - Add code used for benchmarking.
In particular the full rewrite of Javadocs was painful but hopefully useful to people here, not necessarily just DescripTor users but anyone working with Tor network data. Here's the compiled web version until DescripTor has its own website:
https://people.torproject.org/~karsten/volatile/descriptor-docs-2016-05-31/
Many thanks to iwakeh for helping with most of these changes!
All the best, Karsten
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev _______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
-----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJXUFtpAAoJEC3ESO/4X7XBQgsH/A/5T4QnBylP7pxe4xN0Q7GD ZKcwvnNlhLagPaYOHDhGcgFPrYKn1KfGCb1RTF/VDzU7CweXFxwddCd/4suwG840 OclFW2bLTJ1iajOyQSO+zANN5QaQXShdE69aZh8XrA+WV5RrKhJrht1LJN+f7e1F bZw2uwXE6QGWvPC5fR1ISucOeTJZGRTXauSXkHWabeyEIoH+ju99qs4mPWbjgRp2 EhxFbWL/Qqc96M8UkrU64a7rpuk4DU31+YNCytPkIEsWof6mCCaSMhkAu+ZKSoeT caXnu/ztkFx8+nX5p9tzCs0DUKpdlh16MWbazWW8BzaeWJf9KUccpGqZnKW+Yec= =ebdI -----END PGP SIGNATURE-----
Oh, it always had two names, metrics-lib and DescripTor. We have been referring to it as DescripTor lately, that's why I used that name in the announcement. But it's the same thing.
Ahhhh! Gotcha. For what it's worth metrics-lib strikes me as a much better name... * That's what most things I'm aware of refer to. Its git repo, our descriptor parser comparison table, etc. An alternate name is kinda confusing. * Names are often written in lowercase (import statements, etc) so DescripTor becomes descriptor, the thing it's fetching. That's kinda confusing. Anyway, just food for thought. Besides the tarball name I'm not spotting much use of the DescripTor name so it could be pretty easy to standardize on metrics-lib if you wanted. Cheers! -Damian
Hi,
On 31.05.2016, at 21:17, Karsten Loesing <karsten@torproject.org> wrote:
Signed PGP part Hello devs,
I just released DescripTor 1.2.0:
https://dist.torproject.org/descriptor/1.2.0/
From the change log:
# Changes in version 1.2.0 - 2016-05-31
* Medium changes
[…]
- In Torperf results, recognize all percentiles of expected bytes read for 0 <= x <= 100 rather than just x = { 10, 20, ..., 90 }.
Currently a Torperf descriptor contains values for DATAPERC10, DATAPERC20 etc. Will that change and if yes, how? If e.g. it changes to something like DATAPERC01, DATAPERC02, DATAPERC03 etc., will all archived descriptors be newly generated to reflect the new format? Cheers Thomas
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/06/16 14:28, tl wrote:
Hi,
On 31.05.2016, at 21:17, Karsten Loesing <karsten@torproject.org> wrote:
Signed PGP part Hello devs,
I just released DescripTor 1.2.0:
https://dist.torproject.org/descriptor/1.2.0/
From the change log:
# Changes in version 1.2.0 - 2016-05-31
* Medium changes
[…]
- In Torperf results, recognize all percentiles of expected bytes read for 0 <= x <= 100 rather than just x = { 10, 20, ..., 90 }.
Currently a Torperf descriptor contains values for DATAPERC10, DATAPERC20 etc. Will that change and if yes, how? If e.g. it changes to something like DATAPERC01, DATAPERC02, DATAPERC03 etc., will all archived descriptors be newly generated to reflect the new format?
IIRC, OnionPerf generates DATAPERC0 and DATAPERC100 in addition to DATAPERC10 to DATAPERC90. Current descriptors produced by Torperf will remain unchanged, and I don't expect new fields DATAPERC1 or DATAPERC01 to be added soon.
Cheers Thomas
All the best, Karsten -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJXVXg+AAoJEC3ESO/4X7XBO5wH/0Ek4O7i4Ciii9W8j61607Ev tw2/rTAQXDuZyH/t+bwr1IEzXvvLSL949Fhc9FS00kNRfan/ySMqZbskJxYGnLLM 3n+J+GNut4xeJIys7IvDtzMWlq4B0eeWCnXSlIh3Rn4syg5m4ejK8K5Z1Zc6Pa2t MfMBT3o+sNl5W/kWTstNIZuyjsBtcV2wMrdHIEpuj2GwSkmDNPGfBCo+lpFBBu/3 xtY7LMUXqh8AUWDDpDy1beGVsxDqIGH+lfdd9GaRtypzDJgYIKkdcRSfKlQSliV2 jLuwQdrvtfmLV9XMSZbgJg7m1cuDTDykBaLSaz81VpXWAl8gapx5idqzLP3kIR8= =LxwZ -----END PGP SIGNATURE-----
participants (3)
-
Damian Johnson -
Karsten Loesing -
tl