Opened 4 years ago

Closed 3 years ago

#19114 closed defect (fixed)

Rejecting INTRODUCE1 on non-OR or non-edge circuit

Reported by: toralf Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor:
Severity: Normal Keywords: tor-hs
Cc: asn Actual Points:
Parent ID: Points:
Reviewer: Sponsor: SponsorR-can


got this today

May 18 06:41:46.000 [warn] Rejecting INTRODUCE1 on non-OR or non-edge circuit 2147483651.

for the very first time since I run an exit relay. I updated my tor exit relay at a stable hardened Gentoo Linux to HEAD of 0.2.8.x with :

it diff tor- -- . ':!doc/contrib' ':!changes' ':!scripts' > /tmp/tor.patch

few days ago.

Child Tickets

Change History (5)

comment:1 Changed 4 years ago by nickm

Milestone: Tor: 0.2.9.x-final
Status: newneeds_information

Do we have any ideas here? This looks like somebody's testing a broken Tor implementation or something?

comment:2 Changed 4 years ago by dgoulet

Keywords: tor-hs added
Milestone: Tor: 0.2.9.x-finalTor: 0.3.0.x-final
Sponsor: SponsorR-can

I'll also assume at first glance that someone is running a broken implementation. We are also recently seeing #20332 (kind of related). I wonder also if this could have anything to do by the fact that it's on an Exit node... ?

Deferring to 030 because I doubt we'll be able to diagnostic this in time for the 029 stable release. If we do find out that it's something broken in 028, let's consider the backport!

comment:3 Changed 4 years ago by asn

Cc: asn added

comment:4 Changed 4 years ago by nickm

Milestone: Tor: 0.3.0.x-finalTor: unspecified

comment:5 Changed 3 years ago by dgoulet

Resolution: fixed
Status: needs_informationclosed

This warning is at protocol warning level since a4eb17ed89d4761146280490e838cf850bc81296 released in tor-

Note: See TracTickets for help on using tickets.