• Hey Guest, we're evolving the future of TeaSpeak.
    You're invited to join the discussion here!

Pending Channel password doesn't seem to be working.

GiliceJani

Member
Hey!

When I create a channel with the following command as a serverquery a channel gets created with the name "asd" and a password that is not what I set it to be (asd), I can't figure out if I use the command wrong, or there is a problem with TeaSpeak itself.
Code:
channelcreate channel_name=asd channel_password=asd

When I use a client to create a channel with a password it works fine.

Edit:
Forgot the server version. It's "1.5.0-beta".
Passwords don't work, no matter which client I use, tea or tea*.
There is a password set, as the client shows it in yellow color but it's not the same as I given it.
 
Last edited:

WolverinDEV

TeaSpeak Team
Staff member
Administrator
Well you're right.
By default the client sets the password hashed via SHA1.
The query should not be required to do so.
That's a bug (will be fixed in the next build)
 

GiliceJani

Member
I'm looking at a temporary solution as I use a script to create channels with passwords.
Are you sure it's SHA1? Is it salted or something? Because SHA1 doesn't work for me. (Using the php sha1 function)
 
Last edited:

GiliceJani

Member
base64_encode(sha1($pw)) doesn't work either.
According to a community post it's this algorithm.
Code:
Base64(SHA1(Base64(SHA1(UTF8Encode(password))) + virtualserver_keypair))
 

WolverinDEV

TeaSpeak Team
Staff member
Administrator
You may want to set the channel_flag_password=1 explicitly. But I don't think that this will change the basic behaviour...
 

GiliceJani

Member
Code:
base64_encode(sha1(utf8_encode($password)))
This doesn't want to work for me.

channel_flag_password is set to true by my php code.

I will look into this a bit later.

---- Automatically Merged Double Post ----

Aaah, so it looks like this works in php
Code:
base64_encode(hex2bin(sha1($password)));
You win.
UTF8 Encode is not needed in php.
For me it only made utf8 passwords not work lol.
 
Last edited:

WolverinDEV

TeaSpeak Team
Staff member
Administrator
Ahh well php seems to return the SHA1 hash as hex which is pretty interesting tbh^^
 

WolverinDEV

TeaSpeak Team
Staff member
Administrator
//Opened
Query passwords should have been hashed automatically by the server for query connections