kinda weird, I was so sure that I have already reported similar bug. Now I'm not sure whenever I should comment here or open a new report.
The --auth option in transmission-daemon.default file is redundant and users encounter below problem: When you have argument --auth passed to transmission-daemon it takes precedence over "rpc-authentication-required" setting from settings.json, enforcing authentication. Additionally after client is closed "rpc-authentication-required" is set to true. It basically mean that the user cannot configure transmission-daemon to not require login and password when accessed. By default "rpc-authentication-required" is set to 1, it's also set to "true" after transmission-daemon was run with --auth argument so there shouldn't be a problem when users suddenly run insecure daemon. Best Regards, Krzysztof Klimonda -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
