Opened 11 years ago

Last modified 7 years ago

#689 closed enhancement (None)

Add Bogon network to the default reject policy

Reported by: amis Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.1.2.19
Severity: Keywords:
Cc: amis, arma, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

IP from the bogon list could be found in the current directory:
1.1.1.1 1.1.1.2 39.x.x.X

Add the bogon network list in the default reject policy could be good.

If i don't think there is, an accept policy most of these IP could be added.

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (4)

comment:1 Changed 11 years ago by arma

I see that 'dir1' is advertising an IP address of 1.1.1.1. But that doesn't
matter, because in the networkstatus consensus it is not listed as Running.
So nobody will use it.

As for rejecting all the unassigned network ranges by default in the exit
policy, we even have a FAQ entry for that:
https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#UnallocatedNetBlocks

comment:2 Changed 11 years ago by amis

we could see also
36.232.55.149
27.237.10.86
5.12.130.211
5.255.238.134

dir1 1.1.1.1 and dir2 1.1.1.2 all seen in Torstatus.

I think, tel me if you agree, that if they are test routers they not have to be published using ip from Unassigned block.
Perhaps Test class block should be better.

For my request of blocking, i was wrong, sorry. So i agree and request to close this bug.

comment:3 Changed 11 years ago by phobos

flyspray2trac: bug closed.

comment:4 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.