Opened 12 years ago
Last modified 10 years ago
#2209 assigned bug
[BlockList] blocklist ignored on startup
| Reported by: | beadon | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | Future |
| Component: | Core | Version: | 1.3.5 |
| Keywords: | blocklist | Cc: |
Description
It appears that the Blocklist is ignored on startup of the daemon for a short period of time -- the test here is to add a tracker to the blocklist and restart the daemon, you will see a connection established to the (supposedly blocked) tracker and torrent downloads will function for the torrent.
Change History (2)
comment:1 by , 12 years ago
| Component: | other → plugin |
|---|---|
| Owner: | set to |
| Status: | new → assigned |
| Summary: | BlockList not always enforced → [BlockList] blocklist ignored on startup |
| Version: | other (please specify) → 1.3.5 |
comment:2 by , 10 years ago
| Component: | Plugin → Core |
|---|---|
| Owner: | removed |
Note:
See TracTickets
for help on using tickets.
The reason is that the plugin is loaded a while after the libtorrent session has started.
I think the solution would be to have something along the lines of an option in core to block all ips on startup, as this can't be solved in the plugin code.