Re: [tor-bugs] #25223 [Core Tor/Tor]: dos: dos_new_client_conn: Non-fatal assertion !(entry == NULL) failed

[Tor Bug Tracker & Wiki]

#25223: dos: dos_new_client_conn: Non-fatal assertion !(entry == NULL) failed
--+
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:  Tor:
  |  0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  tor-dos, tor-relay, 033-must  |  Actual Points:
Parent ID:  #24902| Points:
 Reviewer:  nickm |Sponsor:
--+
Changes (by dgoulet):

 * status:  merge_ready => closed
 * reviewer:   => nickm
 * resolution:   => fixed


Comment:

 Merged into #24902.

--
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] #25223 [Core Tor/Tor]: dos: dos_new_client_conn: Non-fatal assertion !(entry == NULL) failed

[Tor Bug Tracker & Wiki]

#25223: dos: dos_new_client_conn: Non-fatal assertion !(entry == NULL) failed
--+
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:  defect| Status:  merge_ready
 Priority:  High  |  Milestone:  Tor:
  |  0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-dos, tor-relay, 033-must  |  Actual Points:
Parent ID:  #24902| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * 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] #25223 [Core Tor/Tor]: dos: dos_new_client_conn: Non-fatal assertion !(entry == NULL) failed

[Tor Bug Tracker & Wiki]

#25223: dos: dos_new_client_conn: Non-fatal assertion !(entry == NULL) failed
--+
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:  defect| Status:  needs_review
 Priority:  High  |  Milestone:  Tor:
  |  0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-dos, tor-relay, 033-must  |  Actual Points:
Parent ID:  #24902| Points:
 Reviewer:|Sponsor:
--+
Changes (by dgoulet):

 * status:  assigned => needs_review
 * parent:   => #24902


Comment:

 Branch: `bug25223_029_01`

 Based on ticket24902_029_05 branch. Once ACK, I'll merge this into that
 parent branch for the 029 backport.

--
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] #25223 [Core Tor/Tor]: dos: dos_new_client_conn: Non-fatal assertion !(entry == NULL) failed

[Tor Bug Tracker & Wiki]

#25223: dos: dos_new_client_conn: Non-fatal assertion !(entry == NULL) failed
+
 Reporter:  dgoulet |  Owner:  dgoulet
 Type:  defect  | Status:  assigned
 Priority:  High|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tor-dos, tor-relay  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+

Comment (by dgoulet):

 Ok I figure it out I think.

 Bridge aren't suppose to have DoS mitigation on because of this in
 `config.c`:

 {{{
   if (public_server_mode(options)) {
 /* If we are configured as a relay, initialize the subsystem. Even on
 HUP,
  * this is safe to call as it will load data from the current options
  * or/and the consensus. */
 dos_init();
 }}}

 So we don't init the DoS mitigation when reading the options. However,
 when we get a new consensus, we do `set_dos_parameters()` which can
 enable/disable it. See `dos_consensus_has_changed()`.

 Basically, we need to gate the `set_dos_parameters()` for public relays.
 We call that in `dos_init()` and when the consensus changes.

--
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