Tranmission 2.93 compatability

[Tangbravo221]

No description provided.

[Tangbravo221]

HI Guys,

This is my first issue, so please forgive any breach of protocol.
Transmission 2.93 was released today (3/19/2018) and doesn't require a username. The current version (5.14) won't authenticate unless there IS a password.

Thanks,

TB

[antekgla]

I don´t understand...
In 2.93 it is possible authenticate with username only (without password)
or without username/password at all?

[AffekeNommu]

I am also having the same issue. I can get to my copy of Transmission 2.93 via the web interface with password and no username just fine but I cannot configure Transmission Remote GUI to get to it as it does not save the login credentials if the username is blank.
Yes Transmission 2.93 allows you to login using just the password and leaving username blank.

[Tangbravo221]

It’s possible to authenticate without USERNAME, PW is still required. T-GUI 5.14 won’t allow any sort of authentication without a Username. It’s either all or nothing on authentication.

[teufelhunden0311]

It seems the remote gui is busted until an update allows authentication without a username. It's sucks too because my seedbox updated our transmission clients yesterday.

[Tangbravo221]

Yup, but I hadn’t see anything on it so I thought I would post it.

[antekgla]

I try to look at it...
...but I dont understand: what is the advantage of not have a Username and only password?
What security problem resolve that?
There any scenario where that is desirable?

edit: for a temporary fix can't you edit your settings.json in transmission daemon and add a username?

[Tangbravo221]

No idea of the advantage. You would have to ask the authors of Transmission 2.93… It’s caused a lot of problems not just to users, but to seedbox support…

[leonsoft-kras]

@antekgla - there is version 2.93 for windows. We need to install and configure the input of only the password. Next, look under the debugger, what happens in the TRGUI.
Perhaps the problem isn't only in the TRGUI. It may be necessary to modify the RPC protocol in the program.

[Tangbravo221]

This is what my provider said was needed: For things which require a username it is possible to add one to the rpc-username field of ~/.config/transmission-daemon/settings.json. Please bear in mind you'll need to stop the Transmission process prior to making changes. Also, adding a username will negatively impact the web UI - it will continue to auto-refresh until you press enter on the URL bar.

[antekgla]

@Tangbravo221 you need to do what your provider said:

• Log in your seedbox (using putty or another terminal program)
• Stop the transmission daemon (ask your provider how do that)
• Edit ~/.config/transmission-daemon/settings.json adding in the rpc-username the username you want (between quotes)
• Save ~/.config/transmission-daemon/settings.json
• Start the transmission daemon again.
• Log in with TransGUI with the new username.

[Tangbravo221]

Actually I’m just going to switch to deluge and be done with it, especially if T-GUI will not be updated.

[PeterDaveHello]

@Tangbravo221 no offense, but I think maybe less emotions here can help solving the problems, we're all trying to imrpove this project by our own spare time.

[AffekeNommu]

I have been having a poke around the code and can see that blank username is being used to set the authentication flag in LoadConnSettings in connoptions.pas.
I have added a username in the rpc-username settings in the json and login is working happily for Transmission Remote GUI now.
Really do not know why Transmission chose to default to password and blank username...

[antekgla]

I have been having a poke around the code and can see that blank username is being used to set the authentication flag in LoadConnSettings in connoptions.pas.

Yes I see it but that is not the problem. That line in LoadConnSettings in connoptions.pas only prevent of read the password from ini file if the username is blank and fill the password edit.

I have being debugging and seems a deeper problem. I guess what is not transGUI fault besides a problem in synapse library.., but I am only guessing and I need to investigate a lot more.

[Tangbravo221]

I’m sorry, I had no idea I was showing emotion. I get this a time contribution thing and that it’s fixing something done by the authors of Transmission. I just meant to say that for me, trying to change a file and going in via SSH is right on the edge of the cliff for my expertise. I’m offered rtorrent and deluge and rather than overtax my limited skills, I’m better off going temporarily to another platform. I take no offense and my apologies if someone took offense at what I wrote. It was not, in any way meant to critize or offend anyone (except maybe ok, whoever made this change at transmission and forcing it (as opposed to allowing the old way to continue.)

[antekgla]

Fixed in fafa368

Was an error in Synapse library what exclude all authentication info when the user is empy.
Now checks user AND pass, if any is not empty the auth info is included.
Also adapted the LoadConnSettings procedure in connoptions.pas to load the password also when the user is empty.

@Tangbravo221 sadly you have to wait to a new release to enjoy this fixes 😢 unless what @PeterDaveHello make a 5.15.1 release 😉

[PeterDaveHello]

@antekgla not really, we have temporarily builds in every commit :)

[PeterDaveHello]

@Tangbravo221 what's your operating system? Except Windows, we provide temporarily builds for other platforms that we support.

[Tangbravo221]

Wouldn’t you know it, I’m on windows 10 x64….

[PeterDaveHello]

@Tangbravo221 hmmm, I'll release v5.15.1 soon for that, as we don't have automatic build for Windows, it takes more time and manual works to release for it.

[Tangbravo221]

No problem I appreciate it. Amazing this thing you guys do….Most folks have no idea….

[PeterDaveHello]

Thanks. Hopefully, v5.15.1 will be released within 12 hours.

[Tangbravo221]

Wow, on behalf of so many that wouldn’t know who to thank…THANK YOU!

[PeterDaveHello]

@Tangbravo221 due to some reasons, I have to push the release a little bit later, about 6 hours later. Just let you know.

[Tangbravo221]

No problem. Appreciate your time and effort. Thank you! (and for the update also!)

[PeterDaveHello]

v5.15.1 here:
https://github.com/transmission-remote-gui/transgui/releases/tag/v5.15.1

[Tangbravo221]

THANK YOU PETER!

[PeterDaveHello]

@Tangbravo221 you're welcome

[cfpp2p]

@antekgla @PeterDaveHello
daemon also accepts empty for both in settings.json and authenticates with web client.
I can't authenticate like that with transgui right now.
I don't know what's a use case or security reason but regardless, whether we like this daemon behavior or not.

    "rpc-authentication-required": true, 
    "rpc-password": "", 
    "rpc-username": "", 

fafa368
looks like we can do entirely without cbAuth.Checked and if (User <> '') or (Pass <> '') then

All other usename password configurations function with v5.15.2

thanks for v5.15.2 :)

[PeterDaveHello]

@cfpp2p I saw that you have a forked version of transgui, maybe you'd like to contribution some codes? :)

[cfpp2p]

@PeterDaveHello thanks for opportunity, we'll see, time is crazy...

[PeterDaveHello]

@cfpp2p 😄

[barbequesauce]

@cfpp2p described my use case nicely. No username/password, instead access is controlled by the rpc whitelist. Hoping this can be addressed...

[antekgla]

@cfpp2p @barbequesauce
What is the point of have Authentication = true and no username and password. Makes no sense...
Make Authentication= false and TransGUI would be connect leaving Authentication checkmark uncheck.

[barbequesauce]

My understanding was that rpc-authentication-required must be true to enable the whitelists...

[antekgla]

My understanding was that rpc-authentication-required must be true to enable the whitelists...

It not true... You can make Authentication=false and have Whitelist active.
Whitelist on/off is controlled by rpc-whitelist-enabled = true

[barbequesauce]

Then I must have some other complication... I'll open a separate issue for that.