12 Dec 10, 03:20PM
I think Ronald_Reagan is on to something, but can't confirm it.
So I tried a different approach. After running some tests on a local server, I believe the exploit is based on changes made to local DNS -- changing the local IP address without changing the external IP address. Something as simple as switching to another computer may allow this, though I believe some additional tweaking is required.
My experiment, truncated for clarity:
Although... I can't imagine why an external IP address would be discriminated by the server in this way. "88.163.251.84" looks like any other "88.163.251.84" to the server. I can't imagine how this would be done in a public server.
So I tried a different approach. After running some tests on a local server, I believe the exploit is based on changes made to local DNS -- changing the local IP address without changing the external IP address. Something as simple as switching to another computer may allow this, though I believe some additional tweaking is required.
My experiment, truncated for clarity:
[SELECT ALL] Code:
logging local AssaultCube server (version 1104, protocol 1132/104) now..
[127.1.1.0] client connected
[127.1.1.0] unarmed logged in (default), AC: 1104|840
[127.1.1.0] client connected
[127.1.1.0] DES|V-Man logged in (default), AC: 1104|840
[127.1.1.0] player DES|V-Man used admin password in line 9
[127.1.1.0] set role of player DES|V-Man to admin
[127.1.1.0] client DES|V-Man called a vote: ban player unarmed, reason: noob
[127.1.1.0] disconnecting client unarmed (vote-banned from the server) cn 0, 49 seconds played, score saved
[127.1.1.0] client connected
[127.1.1.0] disconnecting client unarmed (connection refused - you have been banned from this server) cn 0, 0 seconds played
[127.0.0.1] client connected
[127.0.0.1] unarmed logged in (default), AC: 1104|840
[127.0.0.1] unarmed says: ':D'