Never bind rcon password directly!!! It's really stupid idea.
Secure way:
In cod4/main create a file called rcon.cfg and put there:
rcon login RCON_PW_GOES_HERE
save. Then you can safely make a bind like:
/bind F5 exec rcon.cfg
I'm not a PB Staff member but PB is doing this since its first release. The difference between that one and PB is that PB is far more advanced and provide much better functionality. PBBans does not support it.
To find out if its compatible with PB, open a trouble ticket
As far as I know Yawn admins will not remove your warning as long as its linked to banned PB GUID. We will not remove this ban because its valid. ETPro ids are unreliable. Everyone knows it.
Yes. One of them was closed few months ago. All their customers were globally banned. Another is having same problem. As I said, its only matter of the time. Sooner or later someone always leaks.
Wrong answer.You see, its difficult to find something if you don't know what you are looking for either. EvenBalance needs some time to find out what needs to be checked. It's always only a matter of time.
I had one idea.
Run a separate site which would handle etkey registration that would communicate with Hub.
It could provide etkeys in following ways:
1. One key per account
2. Make a third party program which would tie etkey to hw guid.
3. Selling etkeys
4. Bind etkey with registered username(http://evenbalance.com/index.php?page=registry.php)
Hub could query this site and kick players with unknown guids. It would be also possible to check guid age.
The 1st possibility is the easiest but the least effective
The 2nd one is in theory the best one but it would require third party program that would communicate with the registry. Sooner or later it would be cracked and bypassed.
The 3rd one is good but not sure if would be legal.
The 4th one is the best for practical implementation. It would make et non-free game and thus reduce cheating. And all money would be for PB.