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

[CS1.6\BUG] "timerefresh" only with sv_cheats 1 #2339

Closed
ghost opened this issue Apr 28, 2019 · 5 comments
Closed

[CS1.6\BUG] "timerefresh" only with sv_cheats 1 #2339

ghost opened this issue Apr 28, 2019 · 5 comments

Comments

@ghost
Copy link

ghost commented Apr 28, 2019

#273

It does not work properly. It is enough to enable sv_cheats 1 on the client side, being on the server at this time and timerefresh is working again!

@ghost ghost changed the title [CS1.6\BUG] "timerefresh" only с sv_cheats 1 [CS1.6\BUG] "timerefresh" only with sv_cheats 1 Apr 28, 2019
@ghost
Copy link
Author

ghost commented May 28, 2019

CS 1.6 [Build 8245] "timerefresh" still exploited by intruders!
The scenario is the same: the intruder visits any server, writes "sv_cheats 1" in the client console and timerefresh works again, allowing his to get an advantage.

This is a high priority issue.

@BUXPb
Copy link

BUXPb commented Jun 6, 2019

I confirm. There is still an error in CS 8254.

@mikela-valve
Copy link
Member

mikela-valve commented Jun 6, 2019

@BUXPb CS 8254 should actually have this fixed. sv_cheats is now restricted to only being set on the server and the current value is sent down to all clients whenever it changes. Ensure you test this by connecting to another server also running CS 8254 and trying to enable sv_cheats. It should fail and inform you that it can only be set by the server (i.e. only by the client running the listen server or someone with access to the dedicated server).

Make sure you're opted into the beta for both CS and HL1 as this was an engine fix so the change is pulled in from HL1 not CS.

@Maxi605
Copy link

Maxi605 commented Aug 24, 2020

I believe this should be closed as it was here: #273

@kisak-valve
Copy link
Member

Closing per the last couple comments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants