Temporary passwords

[hizuro]

Hello guys

nice new feature. thanks at the developers

but currently not fully supported by server version 3.0.5.

current problems:
1. passwords not stored in database, empty list after next restart or servercrash.
2. field "connect to channel" has no effect

i hope the next server version coming soon.

greetings
hizuro

[dante696]

We don't wan't to store this password entry in a databse. This is a temporary password, like a temporary channel is. We store it in the RAM of the server and nowhere else.

Can you explain point 2? What does not work here?
I create a password and select a channel and my client joins the channel as soon i use the password i have set in there.
- Note1: do not use the same password, as you big server password!
- Note2: This temporary password only works, when a server password is set and when the user does not use the big server password

[hizuro]

hmm...

client v3.0.6 [win7]
server v3.0.5 [linux x86_64]
server password present
temp password different to server password + other channel (not the default channel)

result: temp password accepted, joined to default channel
5 times set new temp password. same result.

no error messages in client and in logfile or database table messages

I hope to have explained the second point is now better.

[dante696]

1. Make sure that the channel password does match.
2. Check all permissions.
The Maybe needed join power is to high, or your client is not allowed to join that type (semi-per, permanent,...) of channel
3. check that the channel is not full
4. The target client needs the latest client

[hizuro]

hmm...

ok. it works after a change of the permissions b_channel_join_(permanent|semi_permanent|temporary ).
problem: i don't like to give guests the right to jump from channel to channel (the good old sticky ^^)

do you have a recommendation?

[Screech]

I think they should be stored in the database. If I create a temp password for 30 days and a server update is released I have to restart. If 30 days bans (also technically temporary) remain, temp passwords should too.

[dante696]

do you have a recommendation?

You still could use the invite dialog, but this stands in conflict with the temporary password.

ts3server://youriphere?port=9987&password=yourpasswordhere&token=JnDLEgcrmpf4m3cfmiPakdn0A5noLh6TrxRqF0HD

Why do you use a server password, if nobody is allowed to join any channel at all.
You better use the normal group and you could assign then b_virtualserver_join_ignore_password. Then set a server password, that nobody of these Normal users ever get toled.
Now you could allow that guests can join any channel type again.

[hizuro]

hmm...

this is a worse idea to set b_virtualserver_join_ignore_password, because then anyone can connect without password.

And to give all channels a separate password is more work than necessary, for servers with very many channels too much work.

why does not exists a value like b_channel_sticky.
* Users with server password and b_channel_sticky can only join on the default channel.
* Users with a temporary password to connect automatically to their channel.

No one can connect without a password and only privileged users can move freely between channels.

I think:
Features that are in conflict with good safety practices are not good features.

please, give me back the good old sticky feature

greetings
hizuro

[R. Ludwig]

a sticky permission will be implemented in one of the next builds...

[dante696]

An internal ticket for this already does exist.

Internal Ticket TSSERVER-22