origin server ban system
origin server ban system
There is a keyhash system in the origin servers its just not showing with the bfsm software, you can however still use bfsm to add the key once you found it.
The keyhash can be found in the xml logging or statistics.csv if you have those system activated. The server will display a kicked message at joining.
The keyhash can be found in the xml logging or statistics.csv if you have those system activated. The server will display a kicked message at joining.
Re: origin server ban system
no keyhashes here, not even in xmlsfreddy wrote:There is a keyhash system in the origin servers its just not showing with the bfsm software, you can however still use bfsm to add the key once you found it.
The keyhash can be found in the xml logging or statistics.csv if you have those system activated. The server will display a kicked message at joining.
but what's weird, there's a server that's running my patched linux binary and they have keyhashes even in gamespy replies
and they say they didn't modify anything
it's puzzling
can you check gamespy query on your server where you see keyhashes?
echo -n '\status\'|nc -u ip 23000
Re: origin server ban system
Hmm i need to pay more attention to details (:
Windows xp machine, using tuia´s patched exe (two exploit fix and 128 players) bfsm v2.0
Adminlog.csv, no keyhashes
statistics.csv, no keyhashes
.xml, show keyhash
xxxxx by me
Linux machine, using s[sk]´s modified linux exe (two exploit fix by tuia, dont know how many players) bfsm v2.0
Adminlog.csv, show keyhashes
statistics.csv, show keyhashes
.xml, show keyhash
I dont know how to use the code "echo -n '\status\'|nc -u ip 23000" i tried it in a cmd window but it didn´t recognize the command.
Windows xp machine, using tuia´s patched exe (two exploit fix and 128 players) bfsm v2.0
Adminlog.csv, no keyhashes
statistics.csv, no keyhashes
.xml, show keyhash
xxxxx by me
Code: Select all
<bf:event name="playerKeyHash" timestamp="242.362">
<bf:param type="int" name="player_id">0</bf:param>
<bf:param type="string" name="keyhash">xxxxxc65cbe078612b3f0ac635bcd162</bf:param>
</bf:event>
Adminlog.csv, show keyhashes
statistics.csv, show keyhashes
.xml, show keyhash
Code: Select all
"xxxx and $niper",xxx.xxx.216.30,xxxxx9750d12815bf0772b19e0074d8f,[unknown],"operator",1353269473,coral sea,kick,0,banned words in chat messages
I dont know how to use the code "echo -n '\status\'|nc -u ip 23000" i tried it in a cmd window but it didn´t recognize the command.
Re: origin server ban system
that was a linux commandfreddy wrote:I dont know how to use the code "echo -n '\status\'|nc -u ip 23000" i tried it in a cmd window but it didn´t recognize the command.
anyway, it's strange that you have those keyhashes
can you pm me ip of your server so i can check what's mine?
Re: origin server ban system
hm
there's product code in origin client and that one md5summed gives the keyhash i had on that other server
now to find out why doesn't it show on my server, it has to be some setting
there's product code in origin client and that one md5summed gives the keyhash i had on that other server
now to find out why doesn't it show on my server, it has to be some setting
Re: origin server ban system
probably got it, it's that remote keyhash check
iptables -I OUTPUT 1 -d 69.10.30.248 -p udp --dport 29910 -j REJECT
case solved
it created a slight delay when connecting, maybe some suitable --reject-with would help
this should be server-side patchable too
iptables -I OUTPUT 1 -d 69.10.30.248 -p udp --dport 29910 -j REJECT
case solved
it created a slight delay when connecting, maybe some suitable --reject-with would help
this should be server-side patchable too
Re: origin server ban system
Again i missed some details, i have this line in place in the linuxbox since some months back -A OUTPUT -d 69.10.30.248 -p udp --dport 29910 -j DROPfreddy wrote:Hmm i need to pay more attention to details (:
For the windows machine so far have only used the inbuilt firewall but no special rules, installed WIPFW yesterday but havent defined any ruleset for it
edit: blocked output to 69.10.30.248 on the windows machine now, curious to see if it the keyhashes will show up in statistics and adminlog now, the product key is the same as the "game key" you can put it into windows registry if you want.
Re: origin server ban system
Adding some information, Windows BF1942 server v1.612 doesn't communicate with master.gamespy.com:29910 to check for keyhash validation, but keyhash is sent from the client to the server. They've disabled displaying the keyhash of the clients, in GameSpy queries and "game.listPlayers" command, that's why keyhashes don't show on BFServerManager. I don't understand why they chose to do it, maybe to cripple the free server version. Strangely, as freddy pointed out, keyhashes show in game event logs. Anyway, this can probably be patched.
Re: origin server ban system
You mean f31629750d12815bf0772b19e0074d8ffreddy wrote:xxxxx9750d12815bf0772b19e0074d8f
Bitcoin address: 1NEoGgsFS9vxLT3eW4w6RFdvzPXLpQX66t
Re: origin server ban system
It was just some random exampleSeth wrote:You mean f31629750d12815bf0772b19e0074d8ffreddy wrote:xxxxx9750d12815bf0772b19e0074d8f