Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
-+-
 Reporter:  nickm|  Owner:  (none)
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  034-triage-20180328, |  Actual Points:  .5
  034-removed-20180328, prop275, dir-bandwidth,  |
  needs-analysis, 035-removed-20180711   |
Parent ID:  #25503   | Points:  2
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-

Comment (by nickm):

 Actually, it looks like the required router change is made in 0.4.0.1-as
 well: routers use prop293 to know when to publish, and _do_ recognize
 StaleSesc and so they will tolerate the change to publication time in
 consensus directories.

 The remaining change is for authorities to set the published date in
 consensuses to the far future.  They shouldn't do that, however, until a
 majority of the network is on 0.4.0.1-alpha or later, or until we backport
 the relay part of #26770.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
-+-
 Reporter:  nickm|  Owner:  (none)
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  034-triage-20180328, |  Actual Points:  .5
  034-removed-20180328, prop275, dir-bandwidth,  |
  needs-analysis, 035-removed-20180711   |
Parent ID:  #25503   | Points:  2
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-

Comment (by teor):

 Replying to [comment:42 nickm]:
 > The necessary client change went into 0.2.9.11.  The authority change
 went into 0.4.0.1-alpha.  The last change necessary will be to make
 routers recognize StaleDesc.  For any router that does, we can safely set
 its publication date in the future.

 Just to be clear, the remaining changes are both router changes?

 That is, the router can change its own publication date in its descriptor
 to be in the (far) future.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
-+-
 Reporter:  nickm|  Owner:  (none)
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  034-triage-20180328, |  Actual Points:  .5
  034-removed-20180328, prop275, dir-bandwidth,  |
  needs-analysis, 035-removed-20180711   |
Parent ID:  #25503   | Points:  2
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-
Changes (by nickm):

 * owner:  nickm => (none)


Comment:

 The necessary client change went into 0.2.9.11.  The authority change went
 into 0.4.0.1-alpha.  The last change necessary will be to make routers
 recognize StaleDesc.  For any router that does, we can safely set its
 publication date in the future.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  034-triage-20180328, |  Actual Points:  .5
  034-removed-20180328, prop275, dir-bandwidth,  |
  needs-analysis, 035-removed-20180711   |
Parent ID:  #25503   | Points:  2
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-

Comment (by nickm):

 (The child ticket of this is now what I'm hoping I can do in 0.3.5)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  034-triage-20180328, |  Actual Points:  .5
  034-removed-20180328, prop275, dir-bandwidth,  |
  needs-analysis, 035-removed-20180711   |
Parent ID:  #25503   | Points:  2
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-
Changes (by nickm):

 * keywords:
 034-triage-20180328, 034-removed-20180328, prop275, dir-bandwidth,
 needs-analysis, 035-roadmap-proposed, 035-removed-20180711
 =>
 034-triage-20180328, 034-removed-20180328, prop275, dir-bandwidth,
 needs-analysis, 035-removed-20180711


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  034-triage-20180328, |  Actual Points:  .5
  034-removed-20180328, prop275, dir-bandwidth,  |
  needs-analysis, 035-roadmap-proposed   |
Parent ID:  #25503   | Points:  2
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-
Changes (by nickm):

 * keywords:
 034-triage-20180328, 034-removed-20180328, prop275, dir-bandwidth,
 needs-analysis
 =>
 034-triage-20180328, 034-removed-20180328, prop275, dir-bandwidth,
 needs-analysis, 035-roadmap-proposed


Comment:

 I'm proposing the part of this from prop#293 as in for 0.3.5.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  034-triage-20180328, |  Actual Points:  .5
  034-removed-20180328, prop275, dir-bandwidth,  |
  needs-analysis |
Parent ID:  #25503   | Points:  2
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-
Changes (by nickm):

 * parent:   => #25503
 * milestone:  Tor: 0.3.4.x-final => Tor: 0.3.5.x-final


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  034-triage-20180328, |  Actual Points:  .5
  034-removed-20180328, prop275, dir-bandwidth,  |
  needs-analysis |
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-

Comment (by arma):

 Replying to [comment:27 arma]:
 > I'm going to try to track down the "woah that's a lot of descriptor
 publish attempts" bug more in the meantime.

 I have opened #25686 for this bug.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  034-triage-20180328, |  Actual Points:  .5
  034-removed-20180328, prop275, dir-bandwidth,  |
  needs-analysis |
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-
Changes (by arma):

 * cc: prop275, dir-bandwidth, needs-analysis (removed)
 * keywords:  034-triage-20180328, 034-removed-20180328 =>
 034-triage-20180328, 034-removed-20180328, prop275, dir-bandwidth,
 needs-analysis


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  enhancement   | Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  .5
Parent ID:| Points:  2
 Reviewer:|Sponsor:  Sponsor4
--+
Changes (by nickm):

 * cc: prop275, dir-bandwidth, needs-analysis (added)
 * milestone:  Tor: 0.3.2.x-final => Tor: 0.3.4.x-final


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:  assigned
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.2.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--
Changes (by nickm):

 * status:  merge_ready => assigned
 * milestone:  Tor: 0.3.1.x-final => Tor: 0.3.2.x-final


Comment:

 Deferring the rest.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  merge_ready
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--

Comment (by nickm):

 Merged `prop275_minimal_029` into maint-0.2.9

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  merge_ready
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--

Comment (by arma):

 In fact, I was pondering either a world where we merge something like my
 hack1 branch, and then relays wouldn't need to look at the microdesc
 consensus published_on values anymore.

 Or a world where we design some new hack where we put all the timestamps
 to the same future value, *except* for the ones that are sufficiently old
 to trigger the "is quite old" hack.

 I'm going to try to track down the "woah that's a lot of descriptor
 publish attempts" bug more in the meantime.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  merge_ready
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--

Comment (by arma):

 Replying to [comment:25 nickm]:
 > But I still think we can safely merge the prop275_minimal_029 part.
 Y/N?

 Yes!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  merge_ready
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--

Comment (by nickm):

 Okay, I'm convinced that we shouldn't merge prop275_more_031 now, until we
 have a fix for the "version listed in consensus is quite old" bug.  I
 think that means we can return to this in 0.3.2.  But I still think we can
 safely merge the prop275_minimal_029 part.  Y/N?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  merge_ready
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--

Comment (by arma):

 Replying to [comment:23 nickm]:
 > That's 15/>9000 uploads, though?  It seems like it might not matter a
 great deal then.  I think we can also merge these patches now, and
 investigate how to fix the "version listed in consensus is quite old" bug
 before we actually change the published logic.  Agreed?

 Alas, disagree. I think those "not specified" uploads represent a bug
 where some relays upload when they don't need to (i.e. they didn't mark
 their descriptor dirty in any way before uploading), and where nearly all
 of those uploads are discarded because they have only cosmetic changes.

 Here's the stat after 12.5 hours:
 {{{
 $ grep "New descriptor post, because:" moria1-info|cut -d: -f5-|sort|uniq
 -c
1324  bandwidth has changed
 279  config change
   3  configured managed proxies
 436  DirPort found reachable
   2  dns resolvers back
   2  IP address changed
3434  not listed in consensus
  421560  not specified
1120  ORPort found reachable
 674  rotated onion key
4003  time for new descriptor
 868  version listed in consensus is quite old
 }}}

 And out of the "is quite old", we have
 {{{
 $ grep -A1 "is quite old" moria1-info|grep "Added descriptor"|cut -d\'
 -f2-|sort|uniq -c|wc -l
 426
 }}}

 So 426 of our ~7300 relays stayed in the consensus in the last 12.5 hours
 because of this hack.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  merge_ready
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--

Comment (by nickm):

 That's 15/>9000 uploads, though?  It seems like it might not matter a
 great deal then.  I think we can also merge these patches now, and
 investigate how to fix the "version listed in consensus is quite old" bug
 before we actually change the published logic.  Agreed?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  merge_ready
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--

Comment (by arma):

 Replying to [comment:16 arma]:
 > So if we do the next step, which would be setting the timestamp to 2037
 or whatever, we will disable this hack. Are we still using the hack much?

 It turns out we have a way to check -- when relays publish a new
 descriptor, they can include a header:
 {{{
 case DIR_PURPOSE_UPLOAD_DIR: {
   const char *why = router_get_descriptor_gen_reason();
 [...]
   if (why) {
 smartlist_add_asprintf(headers, "X-Desc-Gen-Reason: %s\r\n", why);
   }
 }}}

 So I instrumented moria1 like so:
 {{{
 diff --git a/src/or/directory.c b/src/or/directory.c
 index 67c28e1..4eb461f 100644
 --- a/src/or/directory.c
 +++ b/src/or/directory.c
 @@ -4462,6 +4462,12 @@ directory_handle_command_post,(dir_connection_t
 *conn, co
  const char *msg = "[None]";
  uint8_t purpose = authdir_mode_bridge(options) ?
ROUTER_PURPOSE_BRIDGE : ROUTER_PURPOSE_GENERAL;
 +{
 +  char *genreason = http_get_header(headers, "X-Desc-Gen-Reason: ");
 +  log_info(LD_DIRSERV,
 +   "New descriptor post, because: %s",
 +   genreason ? genreason : "not specified");
 +}
  was_router_added_t r = dirserv_add_multiple_descriptors(body,
 purpose,
   conn->base_.address, );
  tor_assert(msg);
 }}}

 Over the course of about 15 minutes, I see:
 {{{
 $ grep "New descriptor post, because:" moria1-info|cut -d: -f5-|sort|uniq
 -c
  24  bandwidth has changed
   5  config change
  10  DirPort found reachable
  88  not listed in consensus
9017  not specified
  20  ORPort found reachable
   9  rotated onion key
  79  time for new descriptor
  15  version listed in consensus is quite old
 }}}

 So, initial conclusion is "yes, it's still used".

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  merge_ready
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--

Comment (by arma):

 nickm's {{{prop275_more_031}}} looks fine to me, other than the
 mark_my_descriptor_dirty_if_too_old() issue.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  merge_ready
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--

Comment (by arma):

 I added a separate {{{bug21642-hack2}}} branch which plays around with
 allowing the r lines to omit timestamp in the future. It wasn't so bad
 actually. Not intended for actual use, but rather as a proof of concept
 for one way we could do it.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  merge_ready
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--

Comment (by arma):

 Another option for hack1 is to just change the hack to "if you are missing
 from the consensus, decide that the authorities forgot about you so now's
 a good time to republish". The problem with that option though is that
 each time we hit whatever bugs there are, there's a several-hour gap where
 the relay isn't used by clients. That's not ideal, but maybe it's good
 enough? Yuck.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  merge_ready
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--
Changes (by arma):

 * cc: arma (added)


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  merge_ready
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--

Comment (by arma):

 Replying to [comment:16 arma]:
 > So I have resumed thinking that if we set published_on to always 2037,
 we will be disabling this hack. :(

 If we want to re-enable the hack (assuming that when we do the
 published_on change, we do it only in the microdescriptor consensus, and
 not in the vanilla consensus), here is code that would do that:

 {{{
 diff --git a/src/or/networkstatus.c b/src/or/networkstatus.c
 index 2d39c90..3fde2a2 100644
 --- a/src/or/networkstatus.c
 +++ b/src/or/networkstatus.c
 @@ -811,6 +811,35 @@ we_want_to_fetch_flavor(const or_options_t *options,
 int f
 lavor)
return flavor == usable_consensus_flavor();
  }

 +/** Helper function: return 1 if consensus c is non-null and from
 + * within the time bounds of [valid_after, valid_until]. Else return 0.
 */
 +static int
 +consensus_is_valid(networkstatus_t *c, time_t now)
 +{
 +  if (c && c->valid_after <= now && now <= c->valid_until)
 +return 1;
 +  return 0;
 +}
 +
 +/** Return a valid consensus with the preferred flavor flavor if
 + * possible, else return any valid consensus if possible. */
 +networkstatus_t *
 +networkstatus_find_consensus_with_preferred_flavor(int flavor, time_t
 now)
 +{
 +  networkstatus_t *c;
 +
 +  /* One: If we fetch the preferred flavor type, great, use it. Else,
 switch
 +   * to one that we do fetch. */
 +  if (!we_want_to_fetch_flavor(get_options(), flavor))
 +flavor = usable_consensus_flavor();
 +
 +  /* Two: See if we've got it, and if it's valid. */
 +  c = networkstatus_get_latest_consensus_by_flavor(flavor);
 +  if (!consensus_is_valid(c, now))
 +return NULL;
 +  return c;
 +}
 +
  /** How long will we hang onto a possibly live consensus for which we're
   * fetching certs before we check whether there is a better one? */
  #define DELAY_WHILE_FETCHING_CERTS (20*60)
 diff --git a/src/or/networkstatus.h b/src/or/networkstatus.h
 index 71f36b6..c980da3 100644
 --- a/src/or/networkstatus.h
 +++ b/src/or/networkstatus.h
 @@ -66,6 +66,8 @@ const routerstatus_t
 *router_get_consensus_status_by_nickname(
 int warn_if_unnamed);
  const char *networkstatus_get_router_digest_by_nickname(const char
 *nickname);
  int networkstatus_nickname_is_unnamed(const char *nickname);
 +networkstatus_t *networkstatus_find_consensus_with_preferred_flavor(
 +   int flavor, time_t now);
  void networkstatus_consensus_download_failed(int status_code,
   const char *flavname);
  void update_consensus_networkstatus_fetch_time(time_t now);
 diff --git a/src/or/router.c b/src/or/router.c
 index 6d3a32a..e9378d8 100644
 --- a/src/or/router.c
 +++ b/src/or/router.c
 @@ -2391,11 +2391,17 @@ mark_my_descriptor_dirty_if_too_old(time_t now)
  mark_my_descriptor_dirty("time for new descriptor");
  return;
}
 +
 +  /* Find a live consensus, so we can use it below to check if our entry
 +   * is up-to-date. We prefer the vanilla consensus flavor, because at
 some
 +   * point in the future we might stop listing useful published_on
 entries
 +   * in the microdescriptor consensus. */
 +  ns = networkstatus_find_consensus_with_preferred_flavor(FLAV_NS, now);
 +
/* Now we see whether we want to be retrying frequently or no.  The
 * rule here is that we'll retry frequently if we aren't listed in the
 * live consensus we have, or if the publication time of the
 * descriptor listed for us in the consensus is very old. */
 -  ns = networkstatus_get_live_consensus(now);
if (ns) {
  rs = networkstatus_vote_find_entry(ns, server_identitykey_digest);
  if (rs == NULL)
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  merge_ready
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--

Comment (by arma):

 Thoughts:

 A) I think the patch in prop275_minimal_029 is safe and fine.

 B) Check out in mark_my_descriptor_dirty_if_too_old() how we decide to
 republish our descriptor if our consensus entry says our descriptor is
 more than 18 hours old (#3327):
 {{{
 else if (rs->published_on < slow_cutoff)
   retry_fast_reason = "version listed in consensus is quite old";
 }}}
 So if we do the next step, which would be setting the timestamp to 2037 or
 whatever, we will disable this hack. Are we still using the hack much? I
 think we added it because we have a bunch of subtle bugs where relays
 forget to republish, or where relays *do* republish but the dir auths drop
 their newly published descriptor because it's too similar to the last one.
 I don't think we found or fixed those bugs.

 At first I thought "hey, no problem, relays cache both flavors of
 consensus, because directory_caches_dir_info is so lenient." But then I
 realized that in the above code snippet, the rs is gotten from
 networkstatus_get_latest_consensus(), which will be the microdesc
 consensus. So I have resumed thinking that if we set published_on to
 always 2037, we will be disabling this hack. :(

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  merge_ready
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--
Changes (by dgoulet):

 * status:  needs_review => merge_ready


Comment:

 lgtm!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  needs_review
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--
Changes (by nickm):

 * status:  needs_revision => needs_review


Comment:

 We can't use an assertion there -- we also set it for the
 routerstatus_format_entry() call in   networkstatus_compute_consensus().
 I've added one comment and clarified another.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  needs_revision
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--
Changes (by dgoulet):

 * status:  needs_review => needs_revision


Comment:

 lgtm; One quick comment:

 In `routerstatus_format_entry()`, this is used if not vote status is
 present:

 {{{
 format_iso_time(published, rs->published_on_to_format);
 }}}

 This matches the commit description which is that `published_on_to_format`
 is only used has an output for the control port. However, I think we
 should add a strong validation of that and possibly a `tor_assert(format
 == NS_CONTROL_PORT)` in that if? If not, at least add a comment on how
 that is used for that function and what the caller should expect?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  needs_review
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--
Changes (by dgoulet):

 * status:  needs_information => needs_review


Comment:

 Aaah! ok that makes more sense. Thanks. Back in need review

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  needs_information
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--

Comment (by nickm):

 The plan would be to change all the 'published' dates to something like
 2030-01-01.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  enhancement | Status:
|  needs_information
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, review-group-17  |  Actual Points:  .5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor4
+--
Changes (by dgoulet):

 * status:  needs_review => needs_information


Comment:

 In `prop275_minimal_029`, the changes file is confusing to me:

 {{{
 +  [...] This change will
 +  eventually allow us to stop listing meaningful "published" dates
 }}}

 Kind of weird that we want to stop doing something "meaningful" :)...
 maybe it was suppose to be "meaningless" or "useless" or "wrong" or ... ?
 If not, what does that mean exactly?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorCoreTeam201703  |  Actual Points:  .5
Parent ID: | Points:  2
 Reviewer: |Sponsor:  Sponsor4
---+

Comment (by nickm):

 > I think it's important, ok, and low risk, as long as the major
 distributions will take it.
 > (Are any of them only taking security fixes for 0.2.9?)

 I think we've been judicious enough about backporting stuff that this
 shouldn't have too hard a time of getting in.  And if it does, then
 they'll backport it later on, when their not-quite-Tor-029 series break in
 2018/2019.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorCoreTeam201703  |  Actual Points:  .5
Parent ID: | Points:  2
 Reviewer: |Sponsor:  Sponsor4
---+

Comment (by teor):

 Replying to [comment:6 nickm]:
 > Replying to [comment:5 teor]:
 > > Replying to [comment:3 nickm]:
 > > > To review:
 > > >   * In my public tor repository, `prop275_minimal_029`, which
 permits published times to be in the future without breaking Tor.
 > >
 > > I thought we were only doing security backports to 0.2.9?
 > > Or does LTS buy us more latitude for change?

 I think it's important, ok, and low risk, as long as the major
 distributions will take it.
 (Are any of them only taking security fixes for 0.2.9?)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorCoreTeam201703  |  Actual Points:  .5
Parent ID: | Points:  2
 Reviewer: |Sponsor:  Sponsor4
---+

Comment (by nickm):

 Replying to [comment:5 teor]:
 > Replying to [comment:3 nickm]:
 > > To review:
 > >   * In my public tor repository, `prop275_minimal_029`, which permits
 published times to be in the future without breaking Tor.
 >
 > I thought we were only doing security backports to 0.2.9?
 > Or does LTS buy us more latitude for change?

 I think that the LTS gives us a tiny bit more latitude, early in its LTS
 status, to do very-safe futureproofing.  Of course, I'm making up the
 rules as I go along here---what do you think?

 >
 > > For later:
 > >   * #21669 tracks the change where we eventually make the 'published'
 times uniform.
 >
 > The ticket #21669 doesn't exist yet.

 Whoops, typo.  Should have said "#21659".  Will edit.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorCoreTeam201703  |  Actual Points:  .5
Parent ID: | Points:  2
 Reviewer: |Sponsor:  Sponsor4
---+

Comment (by teor):

 Replying to [comment:3 nickm]:
 > To review:
 >   * In my public tor repository, `prop275_minimal_029`, which permits
 published times to be in the future without breaking Tor.

 I thought we were only doing security backports to 0.2.9?
 Or does LTS buy us more latitude for change?

 > For later:
 >   * #21669 tracks the change where we eventually make the 'published'
 times uniform.

 The ticket #21669 doesn't exist yet.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorCoreTeam201703  |  Actual Points:  .5
Parent ID: | Points:  2
 Reviewer: |Sponsor:  Sponsor4
---+
Changes (by nickm):

 * status:  assigned => needs_review
 * actualpoints:   => .5


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  enhancement| Status:  assigned
 Priority:  Medium |  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorCoreTeam201703  |  Actual Points:
Parent ID: | Points:  2
 Reviewer: |Sponsor:  Sponsor4
---+

Comment (by nickm):

 To review:
   * In my public tor repository, `prop275_minimal_029`, which permits
 published times to be in the future without breaking Tor.
   * In my public tor repository, `prop275_more_031`, which stops all
 reliance on the published time in non-vote documents.
   * In my public torspec.git repository, `prop275_part1`, where I update
 the specs to warn about the eventual behavior change.

 For later:
   * #21669 tracks the change where we eventually make the 'published'
 times uniform.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  enhancement| Status:  assigned
 Priority:  Medium |  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorCoreTeam201703  |  Actual Points:
Parent ID: | Points:  2
 Reviewer: |Sponsor:  Sponsor4
---+

Comment (by nickm):

 Steps to take now:
   * In 029, allow published times in the future.
   * In 031, never look at published times in consensus documents.
   * Once 029 is the oldest version still supported, put all
 microdescriptor published times at 2038-01-01 00:00:00 or something.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
--+
 Reporter:  nickm |  Owner:
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:  2 |   Reviewer:
  Sponsor:  Sponsor4  |
--+
 Proposal 275 will proposal will save a great deal of consensus and
 consensus-diff bandwidth down the road, with comparatively little effort.
 Let's get it implemented.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  enhancement| Status:  assigned
 Priority:  Medium |  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorCoreTeam201703  |  Actual Points:
Parent ID: | Points:  2
 Reviewer: |Sponsor:  Sponsor4
---+
Changes (by nickm):

 * keywords:   => TorCoreTeam201703
 * status:  new => assigned
 * owner:   => nickm


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs