Read this NOW. All of you.

[Nemesis]

Originally posted by Neonight


Nemesis, when the account information leaked, that wasn't someone who knows little about hacking. What you're saying is comparing a box to a mansion. One is little and one is big.

Just for the record, that was in Graalonline's account database, not requesting a new password.

it wasn't a "leak" because I remember people logging on the account the thing was you had to decode something to get the passwords.....it was weird...anyhow...I know a lot of people were "hacked" because their accounts were basically used and abused on graal....

anyhow we can forget this and I'll delete my previous posts

[Milkdude99]

Originally posted by SaitoHajime


His RC didn't get logged-onto. And not allowing those with dynamic IPs to have RC is a mistake; dynamic IPs make it more difficult for someone to be hacked, because if a "Hacker" got his/her IP address at one time, it will have changed by the time they would have "given up and gone to their hacker friends with that IP for extra help."

And, most dynamic IPs (exception being large providers such as AOL) will only give a certain IP range in a local area; so to have an IP in the IP range would mean they would have to meet a lot of circumstances.



To you, all I can say is that you did not read this whole thread, and therefore have no idea what you're talking about.

Problem with the dynamic IP changes is that every time he/she logs on someone will have to change his IP to the Correct one , and who is to say the person asking this is a hacker himself and not the Staff Member?Problem is you don't know for sure until it may be too late , no we won't use anyone with a dynamic IP for these reasons , the only way to get around it is *.*.*.* and we will not do this , as for adding multible IPs well we have never been able to get that to work (12.58.12.356,58.65.458.47.52) example. So for Npulse we will stick to the safest and most secure way of doing it , by static IPs only on RC.