[SOLVED] Transmission doesn't encrypt my password

[miceagol]

I have entered the password of the rpc in the settings.json file, but when Transmission is restarted the password is still in plain text. Everyone says the password is supposed to be hashed automatically in other threads I've looked at.

The new user and password works fine in the WebUI, and Transmission was properly stopped before the user/password was entered.

Distro: Ubuntu 12.04.3 LTS
settings.json location: /etc/transmission-daemon
settings.json owner: user
settings.json rights: 600

The settings.json file:

Code: Select all

{
    "alt-speed-down": 50, 
    "alt-speed-enabled": false, 
    "alt-speed-time-begin": 540, 
    "alt-speed-time-day": 127, 
    "alt-speed-time-enabled": false, 
    "alt-speed-time-end": 1020, 
    "alt-speed-up": 50, 
    "bind-address-ipv4": "0.0.0.0", 
    "bind-address-ipv6": "::", 
    "blocklist-enabled": false, 
    "blocklist-url": "http://www.example.com/blocklist", 
    "cache-size-mb": 4, 
    "dht-enabled": true, 
    "download-dir": "/home/user/Downloads", 
    "download-limit": 100, 
    "download-limit-enabled": 0, 
    "download-queue-enabled": true, 
    "download-queue-size": 5, 
    "encryption": 1, 
    "idle-seeding-limit": 30, 
    "idle-seeding-limit-enabled": false, 
    "incomplete-dir": "/home/user/Downloads", 
    "incomplete-dir-enabled": false,
    "lpd-enabled": false, 
    "max-peers-global": 200, 
    "message-level": 2, 
    "peer-congestion-algorithm": "", 
    "peer-limit-global": 240, 
    "peer-limit-per-torrent": 60, 
    "peer-port": 51413, 
    "peer-port-random-high": 65535, 
    "peer-port-random-low": 49152, 
    "peer-port-random-on-start": false, 
    "peer-socket-tos": "default", 
    "pex-enabled": true, 
    "port-forwarding-enabled": false, 
    "preallocation": 1, 
    "prefetch-enabled": 1, 
    "queue-stalled-enabled": true, 
    "queue-stalled-minutes": 30, 
    "ratio-limit": 2, 
    "ratio-limit-enabled": false, 
    "rename-partial-files": true, 
    "rpc-authentication-required": true, 
    "rpc-bind-address": "0.0.0.0", 
    "rpc-enabled": true, 
    "rpc-password": "password", 
    "rpc-port": 9091, 
    "rpc-url": "/transmission/", 
    "rpc-username": "user", 
    "rpc-whitelist": "*.*.*.*", 
    "rpc-whitelist-enabled": false, 
    "scrape-paused-torrents-enabled": true, 
    "script-torrent-done-enabled": false, 
    "script-torrent-done-filename": "", 
    "seed-queue-enabled": false, 
    "seed-queue-size": 10, 
    "speed-limit-down": 100, 
    "speed-limit-down-enabled": false, 
    "speed-limit-up": 200, 
    "speed-limit-up-enabled": true, 
    "start-added-torrents": true, 
    "trash-original-torrent-files": false, 
    "umask": 18, 
    "upload-limit": 100, 
    "upload-limit-enabled": 0, 
    "upload-slots-per-torrent": 14, 
    "utp-enabled": true
}

[JJTagy]

Are you entering the password directly in the settings file?

[miceagol]

Yes, entered directly in settings.json file in quotes. That was the procedure as far as I read everywhere?

[JJTagy]

I'm not sure where you read that. The best thing to do is stop transmission, delete your current password in your settings file, and then restart using the command line to enter your rpc username and password combo. That is where it will automatically convert your plain text password from the command line into the encrypted password in the settings file. After that, you can stop transmission again and make any further changes you want to the file.

[miceagol]

For example here.

What exactly do I do to "restart using the command line to enter your rpc username and password combo"? Could you give me an example command?

[JJTagy]

Interesting. Never tried that method. I'll have to try that sometime. Here is a cmd line method:

.transmission-daemon -u <username> -v <password> -a 127.0.0.1,192.168.*.*"

Then you can ctrl-c out or kill process to find new settings file update.

[miceagol]

Well, the problem here is that I start the transmission-daemon as a service. If I use your command, a settings.json file is created in .config/transmission-daemon in my home folder. But this is not the correct settings file.

The settings.json file I'd like to edit is located in /etc/transmission-daemon. I have to add the parameters when I start the service somehow

Code: Select all

sudo service transmission-daemon start

I tried to hard code the parameters into the /etc/init.d/transmission-daemon script which is executed when starting the service, but no luck there.

Any suggestions?

[miceagol]

Ah! Solved it.

I had for some reason changed the script to run using my user instead of the debian-transmission user. I had also changed the owner/group of the settings.json file. I changed the user and permissions back to the debian-transmission user, and voila, password hashed.

I must have prevented write access to the process that wanted to edit the settings.json file somehow.