Opened 4 years ago

Closed 4 years ago

#16683 closed defect (not a bug)

TOR keeps selecting exactly the same single entry node every time

Reported by: gupyx Owned by:
Priority: Medium Milestone:
Component: - Select a component Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Since two weeks ago, my copy of TOR (4.5.3) keeps using exactly the same entry node every single time I use it. I am pretty sure that that's not how it used to be in the past.

I feel a bit uncomfortable about it, so I wanted to ask for advice if it's just another security improvement that came with v4.5.3 or if I should do something about it?

The documentation states that it's normal for TOR to use only a few entry relays, and not just a single one. That's what made me suspicious: TOR has been showing me the same IP address for the entry relay for almost two weeks now.

Here's a bit more information on my situation: I am using TOR in a relatively small country with a population of less than 10 million people. According to TOR, the entry relay I have been using the past few days is also located in my country.

In the past, however, TOR mainly selected entry nodes located in adjacent countries (which are multiple times bigger in size and population and thus offer more nodes in general, I guess). I remember very rarely seeing TOR selecting any relays (be it entry, middle or exit) located in my country at all (as there are probably not many relays in my small country in general).

So all in all, I am not quite sure what to make of this recent change and how to react to it.

Child Tickets

Change History (1)

comment:1 Changed 4 years ago by yawning

Resolution: not a bug
Status: newclosed

Guards have been in tor for a long time, and a single guard with a long rotation interval also has been a tor feature for quite a while.

Note: See TracTickets for help on using tickets.