Re: [tor-bugs] #29699 [Core Tor/Tor]: INTRO2 replay warn logs with v3 onions

2019-09-16 Thread Tor Bug Tracker & Wiki
#29699: INTRO2 replay warn logs with v3 onions
-+-
 Reporter:  mikeperry|  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, security,|  duplicate
  041-deferred-20190530 042-should   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by asn):

 * status:  new => closed
 * resolution:   => duplicate


--
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] #29699 [Core Tor/Tor]: INTRO2 replay warn logs with v3 onions

2019-09-16 Thread Tor Bug Tracker & Wiki
#29699: INTRO2 replay warn logs with v3 onions
-+-
 Reporter:  mikeperry|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, security,|  Actual Points:
  041-deferred-20190530 042-should   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by asn):

 Closing this in favor of #26806. I'm moving #26806 to Sponsor27-must so
 that it gets handled.

--
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] #29699 [Core Tor/Tor]: INTRO2 replay warn logs with v3 onions

2019-09-10 Thread Tor Bug Tracker & Wiki
#29699: INTRO2 replay warn logs with v3 onions
-+-
 Reporter:  mikeperry|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, security,|  Actual Points:
  041-deferred-20190530 042-should   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  tor-hs, security, 041-deferred-20190530 => tor-hs, security,
 041-deferred-20190530 042-should


--
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] #29699 [Core Tor/Tor]: INTRO2 replay warn logs with v3 onions

2019-04-15 Thread Tor Bug Tracker & Wiki
#29699: INTRO2 replay warn logs with v3 onions
--+
 Reporter:  mikeperry |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.1.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-hs|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by s7r):

 Yes, this might be a dup of #26806. I get it from time to time on my v3
 onions (like today for example). I was on `Tor 0.4.0.1-alpha-dev`
 installed from deb.tpo tor-nightly-master-stretch. This is a public v3
 onion, so it gets some usage.

 {{{
 Apr 15 00:05:32.000 [warn] Possible replay detected! An INTRODUCE2 cell
 with thesame ENCRYPTED section was seen 5 seconds ago. Dropping cell.
 }}}

--
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] #29699 [Core Tor/Tor]: INTRO2 replay warn logs with v3 onions

2019-03-08 Thread Tor Bug Tracker & Wiki
#29699: INTRO2 replay warn logs with v3 onions
--+
 Reporter:  mikeperry |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.1.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-hs|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by mikeperry):

 This may be a dup of #26806

--
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] #29699 [Core Tor/Tor]: INTRO2 replay warn logs with v3 onions

2019-03-08 Thread Tor Bug Tracker & Wiki
#29699: INTRO2 replay warn logs with v3 onions
--+
 Reporter:  mikeperry |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.1.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-hs|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by dgoulet):

 * keywords:   => tor-hs
 * milestone:   => Tor: 0.4.1.x-final


Comment:

 I suspect actually that a client might be simply retrying the INTRODUCE1
 using the same RP on the same intro points because it never got the ACK.
 Maybe a bug tor client side.

--
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] #29699 [Core Tor/Tor]: INTRO2 replay warn logs with v3 onions

2019-03-08 Thread Tor Bug Tracker & Wiki
#29699: INTRO2 replay warn logs with v3 onions
--+
 Reporter:  mikeperry |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 While testing vanguards 0.3.0 with tor 0.4.0.2-alpha and a v3 onion
 service that was only for my testing, I got several loglines to the effect
 of

 {{{
 Mar 07 11:10:17.000 [info] hs_circ_handle_introduce2(): We received an
 INTRODUCE2 cell with same REND_COOKIE field 1 seconds ago. Dropping cell.
 Mar 08 12:05:58.000 [warn] Possible replay detected! An INTRODUCE2 cell
 with thesame ENCRYPTED section was seen 0 seconds ago. Dropping cell.
 Mar 08 14:17:21.000 [warn] Possible replay detected! An INTRODUCE2 cell
 with thesame ENCRYPTED section was seen 59 seconds ago. Dropping cell.
 }}}

 The client was Tor version 0.3.5.7 (git-9beb085c10562a25), from Tor
 Browser 8.0.6. The client was accessing the service as follows:

 {{{
 while [ true ]; do
   torsocks wget  http://$MYV3_ONION_NAME.onion/404 -O /dev/null
   killall -HUP tor;
 done
 }}}

 That v3 404 url is in fact non-existant -- it does just send back a HTTP
 404.

 I'll match up some log instances and attach.

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