Transmission 2.90 Upgrade (Because of Malware)

[adelaespriella]

Hello everyone. Anyone have any idea when the plugin Transmission will me updated to 2.93? version 2.90 has been infected with malware and its giving several problems.

https://www.transmissionbt.com/

 

[Yatti420]

I didn't know freenas was based on macosx.. If you run a mac you should update above 2.90.. They may bump all other versions but who knows..

If your worried about speed of releases install the port instead of a pbi package...

 

[Joshua Parker Ruehlig]

2.93 doesn't exist at the moment, it looks like 2.92 is the latest version.
the freenas PBI that I built from source doesn't include malware (unlike the osx version). I looked at the changelog not much has been fixed for freebsd compared to 2.90

 

[stillka]

Hi,

any idea why 2.90 version always overwrite umask to 18? I stop all transmission daemons, modify the settings.json file but after I start it back online umask is back to default!

Rest of settings preserve....

Thank you!


- daemon is stopped, I set umask to 0:
root@transmission_1:/ # ps aux | grep transmission
root 158 0.0 0.2 192456 25716 ?? IJ Sun02PM 0:51.13 /usr/pbi/transmission-amd64/bin/python2.7 /usr/pbi/transmission-amd64/control.py start 192.168.1.20 12346
root@transmission_1:/ # grep umask /var/db/transmission/settings.json
"umask": 0,


- I start daemon UP and umask is re-set to 18..
root@transmission_1:/ # ps aux | grep transmission
transmission 82493 1.6 0.1 74636 8728 ?? SsJ 11:39AM 0:00.02 /usr/pbi/transmission-amd64/bin/transmission-daemon -g /var/db/transmission -x /var/run/transmission/daemon.pid
root 158 0.1 0.2 192456 26096 ?? IJ Sun02PM 0:51.28 /usr/pbi/transmission-amd64/bin/python2.7 /usr/pbi/transmission-amd64/control.py start 192.168.1.20 12346
root@transmission_1:/ # grep umask /var/db/transmission/settings.json
"umask": 18,

 

[Joshua Parker Ruehlig]

Hi,

any idea why 2.90 version always overwrite umask to 18? I stop all transmission daemons, modify the settings.json file but after I start it back online umask is back to default!

Rest of settings preserve....

Thank you!


- daemon is stopped, I set umask to 0:
root@transmission_1:/ # ps aux | grep transmission
root 158 0.0 0.2 192456 25716 ?? IJ Sun02PM 0:51.13 /usr/pbi/transmission-amd64/bin/python2.7 /usr/pbi/transmission-amd64/control.py start 192.168.1.20 12346
root@transmission_1:/ # grep umask /var/db/transmission/settings.json
"umask": 0,


- I start daemon UP and umask is re-set to 18..
root@transmission_1:/ # ps aux | grep transmission
transmission 82493 1.6 0.1 74636 8728 ?? SsJ 11:39AM 0:00.02 /usr/pbi/transmission-amd64/bin/transmission-daemon -g /var/db/transmission -x /var/run/transmission/daemon.pid
root 158 0.1 0.2 192456 26096 ?? IJ Sun02PM 0:51.28 /usr/pbi/transmission-amd64/bin/python2.7 /usr/pbi/transmission-amd64/control.py start 192.168.1.20 12346
root@transmission_1:/ # grep umask /var/db/transmission/settings.json
"umask": 18,

Don't edit this particular settings directly. I tried to make this one easier to change by making it available in the freenas webui and more human readable.
Instead go to FreeNAS WebUI > lef panel > Plugins > Transmission, and change the Permission setting.

 

[trosso]

2.93 doesn't exist at the moment, it looks like 2.92 is the latest version.
the freenas PBI that I built from source doesn't include malware (unlike the osx version). I looked at the changelog not much has been fixed for freebsd compared to 2.90

I know of one tracker that banned all Transmission 2.90 clients due to the OSX malware issue, despite there being no issues on other platforms. It'd be nice to have the plugin updated to 2.92, only so that it works with trackers that have stringent client rules. Not a big deal though, I'm using another client in the meantime.

 

[Goobz]

2.93 doesn't exist at the moment, it looks like 2.92 is the latest version.
the freenas PBI that I built from source doesn't include malware (unlike the osx version). I looked at the changelog not much has been fixed for freebsd compared to 2.90

I know of one tracker that banned all Transmission 2.90 clients due to the OSX malware issue, despite there being no issues on other platforms. It'd be nice to have the plugin updated to 2.92, only so that it works with trackers that have stringent client rules. Not a big deal though, I'm using another client in the meantime.

I have a few trackers implementing a similar policy and therefor the current 2.90 install in my plugin jail is currently being rejected. This is in turn, screwing up all my automated programs (sonarr, cp etc.).

If it's not too much work can we have an update to 2.92? If not is there an easy way to downgrade without having to re-set up all my seeds?

Thanks so much I appreciate your hard work!

 

[Joshua Parker Ruehlig]

@trosso @Goobz
https://forums.freenas.org/index.php?threads/transmission-2-9-released.41785/page-2#post-270573
I plan on working on it in a few nights.

You can downgrade to any version of the plugin using this procedure.
https://forums.freenas.org/index.php?threads/transmission-settings.41545/page-2#post-267827

 

[Goobz]

@trosso @Goobz
https://forums.freenas.org/index.php?threads/transmission-2-9-released.41785/page-2#post-270573
I plan on working on it in a few nights.

You can downgrade to any version of the plugin using this procedure.
https://forums.freenas.org/index.php?threads/transmission-settings.41545/page-2#post-267827

Thanks for that link. I'll save it for later. I'll hold out on downgrading if you are going to look at it in the next few days. Nothing urgent. Thanks again mate!

 

[Joshua Parker Ruehlig]

transmission 2.92 should be available from the freenas repo now

 

[digitaldiatribe]

transmission 2.92 should be available from the freenas repo now

Thanks for the quick turnaround.

 

[Goobz]

transmission 2.92 should be available from the freenas repo now

Thanks so much! You are a legend! All working perfectly now!

 

[Chris Cameron]

transmission 2.92 should be available from the freenas repo now

would you update transmission to 2.93 due to this vulnerability?
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5702

 

[Joshua Parker Ruehlig]

sure, thanks for informing me. I'll try updating it tonight if I have a chance

 

[Mark Holtz]

Thank you, looking forward to it.

 

[Joshua Parker Ruehlig]

I built the update and uploaded it to my local repo, but for some reason it crashed last night before the official repo could pull the update. hopefully it wont happen again, and the update will be available tomorrow.

 

[Chris Cameron]

I built the update and uploaded it to my local repo, but for some reason it crashed last night before the official repo could pull the update. hopefully it won't happen again, and the update will be available tomorrow.

would it be possible to get an update to 2.94? some of my private trackers are doing away with support for TLS 1/1.1 & only supporting TLS 1.2+... though I'm not sure if this update will make TLS 1.2 work...? maybe updating OpenSSL in the plugin jail?