Opened 13 years ago
Closed 13 years ago
#1583 closed Bug (fixed)
daemon ignores IP whitelist
| Reported by: | yee379 | Owned by: | charles |
|---|---|---|---|
| Priority: | Normal | Milestone: | 1.41 |
| Component: | Daemon | Version: | 1.40 |
| Severity: | Normal | Keywords: | |
| Cc: |
Description
so i'm running:
/usr/local/bin/transmission-daemon -a 127.0.0.1,192.168.0.104,192.168.0.204
and the rpc *IS* blocked on other addresses.
i'm not sure of the heuristics, but it makes sense to me that the webui should also utilise the same ACL. however, it does not - and actually allows access from everywhere.
Change History (6)
comment:1 Changed 13 years ago by charles
- Component changed from Transmission to Daemon
- Milestone None Set deleted
- Owner set to charles
- Status changed from new to assigned
comment:2 Changed 13 years ago by charles
- Milestone set to 1.41
- Version changed from 1.40+ to 1.40
comment:3 Changed 13 years ago by charles
- Resolution set to fixed
- Status changed from assigned to closed
- Summary changed from transmission webui ignores transmission-daemon acl to daemon ignores IP whitelist
comment:4 Changed 13 years ago by Ger Teunis
- Resolution fixed deleted
- Status changed from closed to reopened
It seems that this breaks whitelisting a network range? When I enable the following option (default setting network media tank).
transmission-daemon -a +192.168.2.11 -g /share/.transmission -T -w /share/Download
9/24
Then I get an connection refused when I try to connect using my computer with ip address 192.168.2.135.
comment:5 Changed 13 years ago by Ger Teunis
the line is ofcourse
transmission-daemon -a +192.168.2.119/24 -g /share/.transmission -T -w /share/Download
The "9/24" was pasted by accident after the code block.
comment:6 Changed 13 years ago by charles
- Resolution set to fixed
- Status changed from reopened to closed
I think what's happening here is you're still feeding Transmission an ACL instead of a whitelist. As of 1.41 beta 5, Transmission will warn about this if you feed + or - into the whitelist string...
fixed in trunk in r7346
fixed in 1.4x branch in r7345