Transmission
|
Posts: 403
Threads: 26
Joined: Aug 2015
Reputation:
39
[Solved]
Aug 28, 2015, 11:06 AM
(This post was last modified: Aug 28, 2015, 11:07 AM by manne.)
Maybe change the permission for the file in /var/lib/...?
Wait for Mikes answer
Sent from my SM-G925F using Tapatalk
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Solved]
Aug 28, 2015, 03:24 PM
Manne, that is what I was going to say. Even though Transmission on Jessie uses systemd and I edited the systemd service to explicitly use the /etc/transmission/settings.json file, using the web interface to make changes may be using the /var/lib folder instead.
Try changing the permissions on the settings.json file to 775 and see if they stick, if not I will need to adjust the script to use the /var/lib settings.json.
Posts: 403
Threads: 26
Joined: Aug 2015
Reputation:
39
[Solved]
Aug 28, 2015, 05:59 PM
There is something wrong
This field, stores the password in clear text.. It should encrypt the file upon save and exit
"rpc-password": "password",
I don't have this problem in my product environment.
I have the same problem.
Tried this:
sudo service transmission-daemon stop
sudo chown pi:pi /etc/transmission-daemon/settings.json
sudo chown -R pi:pi /var/lib/transmission-daemon
sudo chmod 775 /etc/transmission-daemon/settings.json
The changes I did here:
sudo nano /etc/transmission-daemon/settings.json
was copied to this location too even if I didn't touch this file,
/var/lib/transmission-daemon/info/settings.json
sudo service transmission-daemon restart
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Solved]
Aug 28, 2015, 06:10 PM
That is exactly what the installer script does Manne, can one of you try
Code:
yes | cp /etc/transmission-daemon/settings.json /var/lib/transmission-daemon/info/settings.json
Posts: 403
Threads: 26
Joined: Aug 2015
Reputation:
39
[Solved]
Aug 28, 2015, 06:15 PM
(This post was last modified: Aug 28, 2015, 06:42 PM by manne.)
(Aug 28, 2015, 06:10 PM)Mike Wrote: That is exactly what the installer script does Manne, can one of you try
Code:
yes | cp /etc/transmission-daemon/settings.json /var/lib/transmission-daemon/info/settings.json
Code:
cp: ‘/etc/transmission-daemon/settings.json’ and ‘/var/lib/transmission-daemon/info/settings.json’ are the same file
Why does it not encrypt my password?
I found this:
https://forum.transmissionbt.com/viewtopic.php?t=15226
But my user is pi, the same as transmission user
in my product environment I found this:
# The name of the user that should run Transmission.
# It's RECOMENDED to run Transmission in it's own user,
# by default, this is set to 'transmission'.
# For the sake of security you shouldn't set a password
# on this user
USERNAME=transmission
The problem is maybe that we have the same user PI in both transmission and RPI user
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Solved]
Aug 28, 2015, 07:43 PM
Looks like it but I personally haven't seen it, what happens if you change the user back to
Code:
debian-transmission
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Solved]
Aug 28, 2015, 07:46 PM
manne, the reason I switch transmission to run as the pi user is to avoid permission issues
I think debian-transmission is the owner of th /var/lib/transmission directory. This could fix the encryption and the permission issues
Code:
sudo usermod -a -G pi debian-transmission
sudo chmod 775 /var/lib/transmission-daemon/info/settings.json
Posts: 403
Threads: 26
Joined: Aug 2015
Reputation:
39
[Solved]
Aug 28, 2015, 07:55 PM
Nothing.
Password still not encrypted.
I did first stop the service, run the commands, start service, changed settings in webui, restarted the service. settings gone and password not encrypted..
My main issue is the encrypted password. I can make my changes in the settings file and live with it for now :p
But I can test anything you want, it's still my test environment
Posts: 1,646
Threads: 2
Joined: Aug 2015
Reputation:
42
[Solved]
Aug 28, 2015, 08:09 PM
(This post was last modified: Aug 28, 2015, 08:29 PM by Mike.)
Sorry manne, I mixed it, this fixes it. Switch username in /lib/systemd/system/transmission-daemon.service to debian-transmission.
sudo usermod -a -G pi debian-transmission
sudo systemctl daemon-reload
sudo service transmission-daemon restart
Now you will have an encrypted password in /etc/transmission-daemon/settings.json and your debian-transmission user will be able to write to folders owned by the pi group
I updated the installer to run it this way. Thank you both for bringing it to my attention, this forum is paying off
Posts: 403
Threads: 26
Joined: Aug 2015
Reputation:
39
[Solved]
Aug 28, 2015, 08:55 PM
There you go!
password encrypted & changes in webui still intact after restart!
Pleasure doing testing with you!
|
|
|