Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#1652 closed Bug (fixed)

Whitelist is always enabled in transmission-daemon

Reported by: DonkeyPunch Owned by: charles
Priority: Normal Milestone: 1.50
Component: Daemon Version: 1.42
Severity: Major Keywords:
Cc:

Description

Just tried using transmission-daemon 1.42 on a machine without any previous version installed. The default settings.json file contains a whitelist of '127.0.0.1'. I edited the settings.json file with the line: "rpc-whitelist-enabled": 0,

When starting up transmission-daemon using -f, I get the following output:

Transmission 1.42 (7495) started
RPC Server: Adding address to whitelist: 127.0.0.1
RPC Server: Serving RPC and Web requests on port 12001
RPC Server: Whitelist enabled
RPC Server: Password required
transmission-daemon: requiring authentication
Port Forwarding: Opened port 51413 to listen for incoming peer connections

I don't understand why the Whitelist is being enabled when I have told it not to. I have got around this by changing the default whitelist from 127.0.0.1 to *.*.*.*

Change History (4)

comment:1 Changed 12 years ago by charles

  • Milestone changed from None Set to 1.43
  • Status changed from new to assigned

comment:2 Changed 12 years ago by charles

  • Milestone changed from 1.43 to 1.50

comment:3 Changed 12 years ago by charles

  • Resolution set to fixed
  • Status changed from assigned to closed

Looks like this was fixed as a side-effect of the tr_sessionInit() changes in r7367

diffs between r7367 and the previous version

comment:4 Changed 12 years ago by charles

  • Severity changed from Normal to Major
Note: See TracTickets for help on using tickets.