Re: Hackers, crackers what ever you want to call this children :)
Quote:
Originally Posted by
Stifi
----
client can always gt hacked easy .. get the best antihack.dll u can find..
get great launcher which is secure
and secure ur main.exe pack it so even ur IP inside its hidden
secure ur pc firewall good
----
1. client anti cheat is aways crackable (trust me, i'know why i sayd ;)
2. server firewall will not help to protect , if the "owner" of d-machine dnt know what to do with it :)
So you can crack BoR anti cheat mega hacker?
Re: Hackers, crackers what ever you want to call this children :)
Usualy it's easier to bypass the Game Guard than cracking it.
Re: Hackers, crackers what ever you want to call this children :)
for new servers, its easy to hack. because usually admins install their 1st website with holes...
and some admins uses 1 easy password only for everything. 1 password for sql pass, admin acc. facebook, yahoo e-mail, hotmail, paypal and etc. :closedeyes:
so when the hacker hacks the website for the 1st time and found out ur pass...
then they know all about you.,
so i suggest, in the beginning.....you should make 1 strong password and try to use a different password for your e-mail and other stuff^^.
its just human errors:ott1: (mostly)
Re: Hackers, crackers what ever you want to call this children :)
Man... the neewbie-ness...
First and foremost; [STOP USING ZONEALARM, MCAFFEE, ETC].
Use a good firewall that supports [SNORT RULES/IDS/IPS] and then you can filter traffic based on [PACKETS] not [IP ADDRESSES] and that will keep your servers from being "HACKED"...
Also, come on paying them to stop, its just the dumbest thing I have ever heard, EVER!!!!!!
If you are using 'template" based sites... well you deserve to get hacked, even more so if you arent smart enough to change all the default passwords.
On another note, if you have a "staff/team/mods/gms", whatever you want to call them, !!!!!!demand!!!! secure passwords and NEVER, EVER, EVER give them direct sql access.... [thats just stupid] .... make sure that you take it upon yourself to change your sql/web passwords and enforce strong passwords from your "staff/team", if a member wont follow the rules, then remove the bad apple before all the apples rot.
