[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tor-dev
Subject:    [tor-dev] PrivCount Status
From:       teor <teor () riseup ! net>
Date:       2019-04-24 3:30:31
Message-ID: 656BB96E-4B24-46D3-B53C-3CB5B7A871DA () riseup ! net
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Hi,

Nick asked me to send a status email about PrivCount, before I go on
leave for a few weeks.

Plan

We want to add the following counters to a PrivCount Proof of Concept:
* check counters (zero, relay count, time in seconds)
* consumed bandwidth

Nick also suggested adding connection counts. That seems like a good
counter, but we want to make sure we do bandwidth in the first release,
because it's a high-risk statistic.


Status

In March and April, I deferred PrivCount tasks to work on chutney for
one of our other sponsors.

I also delayed these tasks, because I was waiting for #29017 and #29018
to merge:
* #29017 PaddingStatistics should be disabled when ExtraInfoStatistics is 0
* #29018 Make all statistics depend on ExtraInfoStatistics


Tickets

The top-level ticket is:

PrivCount proof of concept with existing statistics
https://trac.torproject.org/projects/tor/ticket/27908

I was mainly working on code for these tickets:

PrivCount proof of concept: implement check counters
https://trac.torproject.org/projects/tor/ticket/29004

PrivCount proof of concept: implement consumed bandwidth counters
https://trac.torproject.org/projects/tor/ticket/29005

Make relays report bandwidth usage more often in test networks
https://trac.torproject.org/projects/tor/ticket/29019


Code

I have incomplete branches for #29004, #29005, and #29019 here:
https://github.com/teor2345/tor/tree/ticket29004-wip
https://github.com/teor2345/tor/tree/ticket29005
https://github.com/teor2345/tor/tree/ticket29019

I think all the necessary code is present in these branches.
(But maybe it's not???)

But it needs some cleanup:
* rebase on to the current master,
* put the commits on the right branches
* make sure it does what these tickets say it should do

I'm happy to do that after I come back from leave.
I am also happy if Nick wants to clean up this code.

See also my previous email about BridgeDB and PrivCount. Maybe we can
save ourselves some effort by using PrivCount's obfuscation on
BridgeDB's statistics.

T

--
teor
----------------------------------------------------------------------


["signature.asc" (signature.asc)]

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEo9HIo7IdGQ1wBWG3EP6qDnB1ZyoFAly/2FcACgkQEP6qDnB1
Zyrvwg/+KTpZNg5RdzS5EKeVbi/AhKEgdune9ywoZXNxbFzdpjCkBCM2hgDXTiL6
eM4ytzW1mBS/d2yruZ1rOM3IuqWsTFMBxexp4EiNHV6fcL4mInnkJ6SMPjQd/usK
MvBr4hMyktuQ4vHeKmtP9W0DelAOKsj7lHqL4SQNVzwd+DmegGRF5XGcO23w4R7V
S9ItQb6dqj5kUdCpkRImcdsYBnczPAiCAAeQXMKhQDfEcwergU0wDr1/vC3ead2z
Qg9LRACjtyNJpBqL/uGda0jWqopoZGYYeCpKtSevYVoE4g/2Qj0pYZplS9nVM4oY
1PxG5cK+dbQkVNWCxxB2LS9aW6wIJVce9UqAxTgyaW0OTvs3FPeAVIgmTYxzvxFG
9gbq8mpe8hSOBhAE0tY7/dh1NSnTwPBNwz2jCncsvI7FUv6T+ogZ434Z+Am/bj22
KRHiYr6p7Beej7VfDLHblm5cVpaw4OB3f2PyYnzsTZC3cwCHafU1QHBVLgfJKeZE
caZu8vSSCzIz61A+LYwd20HhTlHyecM3Zq0w09r7fY8wCwPWVjTSLOfOYt2uRL5e
WxD/ugWCRh9ESKOlYlk92R79CIPrJuhO/EHo+EgKLoil2jt82mrKOXyEGkuGNRkQ
YGZBQ7CqUrUk1B/t/OQiYUnCRI7Lf/2gaU4Uy5iMLA0VgZHjbus=
=Xo8o
-----END PGP SIGNATURE-----

[Attachment #6 (text/plain)]

_______________________________________________
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev


[prev in list] [next in list] [prev in thread] [next in thread]