Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

give admins the possibility to do some stealth action. #2225

Closed
jxsl13 opened this issue Sep 9, 2019 · 12 comments
Closed

give admins the possibility to do some stealth action. #2225

jxsl13 opened this issue Sep 9, 2019 · 12 comments

Comments

@jxsl13
Copy link
Contributor

jxsl13 commented Sep 9, 2019

Hiding, who they watch + hiding that they are admin.

@fokkonaut
Copy link
Contributor

How can be seen that they are admins?

@jxsl13
Copy link
Contributor Author

jxsl13 commented Sep 10, 2019

Looking at people who are votable + the gamer client for example clearly shows that with an asterisks/star behind the name.

@Dune-jr
Copy link
Member

Dune-jr commented Sep 10, 2019

You don't need any modification, people that you cannot vote-kick in the menus are logged in rcon.
In 0.6, you couldn't votekick them either though (although you had to actually attempt to votekick).

Like I told you earlier, I would argue that

  • if you want to do "stealth action", you can just not log in
  • people who try this hard to dodge admins probably know the name of the admins anyway
  • server modifications for edge use cases (it's a one-liner)

@H-M-H
Copy link
Contributor

H-M-H commented Sep 10, 2019

If you want to be really stealthy, you could use the external console:

MACRO_CONFIG_STR(EcBindaddr, ec_bindaddr, 128, "localhost", CFGFLAG_SAVE|CFGFLAG_ECON, "Address to bind the external console to. Anything but 'localhost' is dangerous")
MACRO_CONFIG_INT(EcPort, ec_port, 0, 0, 0, CFGFLAG_SAVE|CFGFLAG_ECON, "Port to use for the external console")
MACRO_CONFIG_STR(EcPassword, ec_password, 32, "", CFGFLAG_SAVE|CFGFLAG_ECON, "External console password")
MACRO_CONFIG_INT(EcBantime, ec_bantime, 0, 0, 1440, CFGFLAG_SAVE|CFGFLAG_ECON, "The time a client gets banned if econ authentication fails. 0 just closes the connection")
MACRO_CONFIG_INT(EcAuthTimeout, ec_auth_timeout, 30, 1, 120, CFGFLAG_SAVE|CFGFLAG_ECON, "Time in seconds before the the econ authentification times out")
MACRO_CONFIG_INT(EcOutputLevel, ec_output_level, 1, 0, 2, CFGFLAG_SAVE|CFGFLAG_ECON, "Adjusts the amount of information in the external console")

Like that you do not even need to be playing on the server.

@oy
Copy link
Member

oy commented Sep 10, 2019

If you want to be stealthy you log in just when you have to, do your thing and then log of again.
Don't think there needs to be a special feature for that.

@jxsl13
Copy link
Contributor Author

jxsl13 commented Sep 13, 2019

I wonder, has anyone of you done any admin work during 0.6?

@Sonix-
Copy link
Member

Sonix- commented Sep 13, 2019

I wonder, has anyone of you done any admin work during 0.6?

Yes, I log in, I ban and that's all

Else @H-M-H 's suggestion is also reasonable

@jxsl13
Copy link
Contributor Author

jxsl13 commented Sep 15, 2019

I'd say it's reasonable, but not practicable(switching between multiple application sucks). Like most quality of life features contained in the client, they are not needed, but highly appreciated by the people who use them. Especially because you cannot do that directly from within the client(econ). Then I'd ask to add a way to connect via econ directly within the client.
I would guess that the purpose of the econ was to do stuff, while not being on the server, where you can clearly not detect cheaters, when only using econ.
Edit:
By logging in(rcon), you will directly expose yourself as admin. Because potential client modifications can and will keep track(I highly expect that to happen) of admins and exploit it in a way, that botters(etc.) will know when to use their cheats and when not to.
Basically if specific kinds of cheaters don't know whether an admin is online or not, they will less likely try to cheat and if they do and get banned, they will not know, who banned them and would less likely or less visibly cheat as they are aware that they might be watched by an admin, who knows.

@Dune-jr
Copy link
Member

Dune-jr commented Sep 15, 2019

I believe you that this scenario is a real possibility. However, it seems like the large majority of server admins are open about their identity, and there are already tools at your disposal to cover this edge case (external console, or just don't log in).
It constraints you to use a fake identity anyway so you're not going to be doing this all the time.

Now, this seems to be very important for you, so you could also simply comment out this line on your server:

if(Server()->IsAuthed(m_ClientID))
pPlayerInfo->m_PlayerFlags |= PLAYERFLAG_ADMIN;

@sepulzera
Copy link
Contributor

Please note that it is not allowed to run a server with any modification as vanilla gametype. (And I honestly would like to have that rule changed)

@jxsl13
Copy link
Contributor Author

jxsl13 commented Sep 16, 2019

It's not solely my problem, because I mostly play on zCatch it's easily modifiable. I think this is something that affects the general public and admins that want or need to hide their identities. I opened this issue, because I saw a person(not me) who had exactly that problem on ddrace and thought that it might make sense to address that issue on the teeworlds github. What's rather disappointing is that admins do not necessarily look into the development process and thus don't comment to tell whether they would or want to use such a feature.
I think it would make most sense to have some kinda hidden ctrl+F2 console for econ(connecting to current server ip or connecting to custom ip), in order to utilize h-m-h's approach without modifying the rcon logic too much.

@sepulzera
Copy link
Contributor

Why are admins displayed in first place?

@jxsl13 jxsl13 closed this as completed May 4, 2020
heinrich5991 pushed a commit to heinrich5991/teeworlds that referenced this issue Jun 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants