Как повысить security level в тимспик
TeamSpeak 3
версия: 3.3.8
Последнее обновление программы в шапке: 07.04.2021
Краткое описание:
Голосовое общение во время игры, прямо как на ПК.
Приложение официальное. Что тут есть:
1. закладки
2. мульти-серверное подключение
3. активация микрофона клавишей (клавиши поверх всех окон пока нет), голосом или постоянно включенный микрофон (в играх будет работать только так)
4. управление идентификацией
5. информация об игроках и каналах
6. уведомления о статусе игрока
Прога несовместима с каналами TeamSpeak версии v2 (только с v3 и старше)
Требования для текущих версий:
- ARMv7
- Андроид ОС не ниже 2.3.3
- На вашем устройстве хотя бы один раз должен быть выполнен вход в Google Play
Для версий 3.0.0-beta и ниже - все их можно найти в спойлере "Прошлые версии" :
- Андроид ОС не ниже 2.2
Аналогичная программа: Zello рация
Русский интерфейс: Нет
Причина редактирования: Обновление: новая версия 3.3.8 GP от 25.11.20 непохо, но запоздал на пару лет, да и в скайпе проще, помню как с друзьями и сокланами в тс болтали, всех нагибали, гангали :)тут вроде задумка что бы не постоянно было слышно,а при нажанитий на какую нибудь клавишу,типа как в кс)))
активация микрофона клавишей (клавиши поверх всех окон пока нет) Да простит меня автор, но это просто бред делать программу, да ещё такую на ARMv7, это феил, господа *facepalm* Почему TeamSpeak 3 требуется такой процессор можно прочитать ниже.
The TeamSpeak 3 for Android app is not available for my device. Why?
More "value-classed" devices such as the HTC Wildfire, HTC Legend, Samsung Galaxy Ace, LG Optimus V, and others, instead contain an "ARMv6" chip type, which does not support hardware math co-processing, or the level of performance required by the TeamSpeak 3 application. Therefore, at this time these types of devices are not supported.
During development the decision was made to try and provide the very best voice chat solution, with the best voice quality, to as many people as possible. Supporting lower-performance devices would have resulted in a lower-voice-quality solution for everyone. Please keep this in mind when posting Android Market reviews regarding compatibility issues, as the device choice was made in the interest of supporting as many users as possible.
А так же, у кого какие проблемы с клиентом или есть хорошие идеи - советую писать на официальном форуме на английском языке.
TeamSpeak 3 VoIP communication system uses a concept of so called identities to identify the client to the server. These identities are basically public/private key pairs.
In order to prevent people from just generating a new identity after being, e.g., banned, they added a feature called security levels. Increasing security levels take exponentially more CPU time to reach.
This way a banned user needs to spend at least a minimum amount of time to generate a new identity with the required security level before he is able to join the server again.
Now to my question:
How are security levels implemented, so that the time to improve one can increase exponentially but the time to verify one at the server-side stays the same (or at least increases just linear)?
71.2k 22 22 gold badges 135 135 silver badges 218 218 bronze badges4 Answers 4
A TeamSpeak identity is simply an ECC key pair for the NIST curve ECC-256 as generated by the libtomcrypt library, together with a counter value that is a 64-bit unsigned integer.
The security level makes use of a classical Proof-of-work system.
Let PUBLICKEY be the base64-encoded string of the identity's ASN.1 DER encoded public key. Further, let COUNTER be the decimal ASCII-encoding of a 64-bit unsigned integer. Then the security level is defined as follows.
securitylevel := leadingzerobits(sha1(PUBLICKEY || COUNTER))
Consequently, the expected number of counter values that need to be tried to reach security level n is 2^n (under the assumption that SHA-1 is a uniform random function).
Note that in theory, the maximum security level could be 160 (as SHA-1 produces a 160-bit hash). However, the TeamSpeak client seems to set the limit artificially to 128. In practice, this makes no difference, as no one will ever reach a security level over 128 (except another breakthrough in attacking SHA-1 happens).
Source: TSIdentityTool, which is an open source implementation of the identity and security level mechanisms.
Hashcash is a proof-of-work system designed to limit email spam and denial-of-service attacks.
I can't tell for sure. But if you are looking for a similar feature I would implement it as following: An ID contains a private and a public part (That's what Teamspeak does). So I guess it's some asnyc encryption key you can generate yourself.
Now just generate a sequence of numbers e.g. s = [1..n] and hash them.
As soon as the first M bits of the generated hash match the first M bits of the public key you take it as a valid prof of work for the Security level of M .
You needed n rounds of hashing to find the hash, but to prof it, the server must only hash the result s once and check how many bits match to your public key. The dificulty for you will rise exponentially.
This is in fact similar to what Bitcoin does. But Bitcoin tries to get a certain numbers of Zeros in front of the hash and you don't hash a random number but the b-tree of the block you want to mine plus a nonce (random number).
From Teamspeak: Generate an ID e.g. IHoxfrQNl152vs80N4wYvsEmNd8= Export it to see the secret: e.g. 205VFy/YWQLyDeTxIIQvyy4hGQYxWloFH0R9VW4VRCxQHkcOdFdyX2YHMztQDQQeDA1gNG9Ce0N6CipVHkMie2lzX3ReRX4HFQhqFiB5FBQEEi0DVhhCUltiOE4GcmV2W3FkDX1OdXcrUUxwUUloQVBHRjYvM3EzWCtGeUpkRHlWTTFXZGh1VHJRZVA0Q3hMWE1ITXVxNlU1TTQ=
If you now increase the security, just the first part of the export changes. From 8 → 9 → 24 it gets from 205 to 247 to 520935 .
My highest key has some number around 29147155819 at level 34.
I think this number will somehow hash to something that is related to my public key. So anyone can proof it with a single round of hashing, but my PC needed 29147155819 rounds of hashing to find it, which took quite a while ;)
Btw: The max security is 128, so I guess that's the length in bits of the public key.
Список наших гайдов по администрированию ТС3.
Раздел на стадии заполнения.
Включение расширенных настроек привилегий в Вашем клиенте ТС3:
Переходим по разделу Settings - Options(горячая комбинация клавиш Alt+ P) и ставим галочку "Advanced Permissions system"
Жмем "OK"
Запрет перемещения гостей по Вашему серверу:
Заходим в раздел привилегий групп сервера Permissions - Server Group, выбираем группу гостей(Guest) и снимаем 3 галочки входа в комнаты, название привилегий:
Гости будут попадать на канал который установлен по умолчанию на сервере.
Создание групп с раздельными правами для комнат(подходит если Вы используете один сервер для двух проектов)
1. Все комнаты которые Вы создаете с авторизацией должны иметь значение 20(в редактировании или создания канала - permissions - join - 20)
2. Создаем группу канала(Permissions - Channel Group - выбираем группу гостей, слева внизу есть кнопки, по центру найдете кнопку Copy - пишите любое название группы канала - привилегию i_channel_join_power ставите равную цифре, что установили в настройках канала, у нас это число 20)
3. Добавляем пользователей в группу канала:
3.1. Permissions - Channel Group - выбираем созданную группу канала, слева внизу есть кнопки, самая правая отвечает за пользователей для каждого канала на сервере. Наши каналы будут обозначены буквами A, B, C, D.
3.2 Выбираем в новом окне нужный нам канал A, жмем кнопку add вводим уникальный айди пользователя. Теперь этот пользователь сможет входить в канал А, другого пользователя добавляем по такой же схеме но в каналы: B и С.
В итоге один пользователь сможет входить только в канал А, другой в канал B и С.
ЗАПРЕТ ВХОДА НА ОПРЕДЕЛЕННЫЙ КАНАЛ
В редактировании канала(ПКМ по каналу - Edit Channel) во вкладке "permissions" находится поле "Join", эта вкладка отвечает за доступ пользователя в канал, чтобы пользователь мог зайти в канал, привилегия "Join"должна быть ниже, чем привилегия в группе: i_channel_join_power, а чтобы пользователь не смог зайти в канал, то привилегия "Join"должна быть наоборот выше.
прим. по умолчанию значение Join стоит 0, означает что данное ограничение отключено.
I've used teamspeak for nearly 10 years and have never seen this. What is it and why does it want to take an eternity to do whatever it is doing?
It seems I need to do it to joing the VVG server. Has something been changed?
I should have announced or posted before doing this, sorry to have not done so.
I increased the security level on our TS server to provide a cooling down or waiting period people need to endure before being able to log on to the TS3 server. It's a one time thing that is still less secure than a password, but easier to navigate for people not au fait with putting passwords or identities in bookmarks.
The reason is to provide a (very limited) amount of protection against people that want to come in our channel and troll us. A recent incident where a VVG member did similiar to another outfit made me conscious of this need.
I had increased security a couple of months ago, but it was to a pretty low level, and went unnoticed, so I tried to incrementally increase it again. It seems I increased it to much, as everyone is noticing. I had anticipated members would have to wait 3-4 minutes (additional, on top of their previous security level), but I seem to have increased it higher than intended, and I've heard of waits up to 10 minutes.
A new member, that joins today, would need to wait longer, as their security level would be 0, and they need to reach level 28. Perhaps 10-15 minutes.
Once your client has reached the required security level, you will not need to go through the process again. If you game on multiple PCs, each instance of your client will need to go through the security period.
It is very straight forward, there is nothing you need to do, hit start, and wait for a few minutes. watch this this and this this and you should be done. :)
I trust everyone is in agreement with the spirit of the intent, if not the method (sorry to have neither announced, nor sought consent).
Читайте также: