[Release] UltimateWar - WarRock Private Server

[Sleutel]

Originally Posted by ✔Star✔

We indeed use plain passwords for compatibility reasons.

Biggest excuse so far, you don't need a plain password for compatibility reasons, just freaking hash them.. This just proves that you don't know what you're doing and you should stop for the sake of your players. "Security Freak" Well that is just bullshit.

[*Last*]

Originally Posted by Sleutel

Biggest excuse so far, you don't need a plain password for compatibility reasons, just freaking hash them.. This just proves that you don't know what you're doing and you should stop for the sake of your players. "Security Freak" Well that is just bullshit.

I think the same, but in the end they will do as they want...the success or failure of their private server will tell them the truth.

[toxiicdev]

[✔Star✔]

Originally Posted by toxiicdev

That's because your IP is blocked prob ^^

Nah joking, the anti SQL script caused this and is fixed already.

[MRx86™]

Originally Posted by ✔Star✔

That's because your IP is blocked prob ^^

Nah joking, the anti SQL script caused this and is fixed already.

Anti sql script ? lol

[✔Star✔]

Originally Posted by GHTheBoss

Anti sql script ? lol

Yeh .htaccess tweaks
Anyways I will be really suprised if someone manage to hack us now via php.

[Sleutel]

Originally Posted by *Last*

I think the same, but in the end they will do as they want...the success or failure of their private server will tell them the truth.

They already failed, their database content leaked. The damage has already been done.

[✔Star✔]

Originally Posted by Sleutel

Well people can easily sue you in the future if their data is leaked, don't think they can't find you because you're sitting behind a computer screen. Even the biggest hackers in history were found. Anyways here is an example about how much '*****' you should give.

Check our register page: Or the spoiler.

I think it's clear enough.

 Spoiler

DO NOT USE SAME PASSWORD ON ULTIMATEWAR THAT YOU USE ON OTHER WEBSITES! WE ARE NOT RESPONSIBLE IF YOU IGNORE THIS.
BECAUSE ULTIMATEWAR IS UNDER DEVELOPMENT DEVELOPERS MIGHT SEE YOUR PASSWORD!

SAME GOES FOR E-MAIL! YOU DON'T USE YOUR REAL E-MAIL BUT WRITE YOUR FAKE E-MAIL DOWN! IF YOU WANT TO CHANGE YOUR PASSWORD IN THE FUTURE YOU WILL NEED TO TELL US YOUR FAKE E-MAIL TO PROOF YOUR THE ORGINAL OWNER OF THE ACCOUNT.
Note: This is only for the in-game account, in the forum everything is secure so you can use your real e-mail there to receive updates etc.

[toxiicdev]

Originally Posted by ✔Star✔

Check our register page: Or the spoiler.

I think it's clear enough.

 Spoiler

DO NOT USE SAME PASSWORD ON ULTIMATEWAR THAT YOU USE ON OTHER WEBSITES! WE ARE NOT RESPONSIBLE IF YOU IGNORE THIS.
BECAUSE ULTIMATEWAR IS UNDER DEVELOPMENT DEVELOPERS MIGHT SEE YOUR PASSWORD!

SAME GOES FOR E-MAIL! YOU DON'T USE YOUR REAL E-MAIL BUT WRITE YOUR FAKE E-MAIL DOWN! IF YOU WANT TO CHANGE YOUR PASSWORD IN THE FUTURE YOU WILL NEED TO TELL US YOUR FAKE E-MAIL TO PROOF YOUR THE ORGINAL OWNER OF THE ACCOUNT.
Note: This is only for the in-game account, in the forum everything is secure so you can use your real e-mail there to receive updates etc.

Cool page, too much professional for my eyes.

[ToxicData]

best url part: /secure/

[✔Star✔]

Originally Posted by toxiicdev

Cool page, too much professional for my eyes.

Ah so now you complain about the looks.

Well you guys are giving me a hard time with the security part that I don't have much time to spend on the gfx.

But don't worry, we are already working on a new php site and it will be released soon.

[toxiicdev]

Originally Posted by ToxicData

best url part: /secure/

Of course it is to mark that's secure, but "you mustn't use your usual password because developers might (may) see that"

[✔Star✔]

Originally Posted by toxiicdev

Of course it is to mark that's secure, but "you mustn't use your usual password because developers might (may) see that"

That's right, every website you should use a different password.
If you don't, you are anyway unsecure.

[Sleutel]

Originally Posted by ✔Star✔

Well you guys are giving me a hard time with the security part that I don't have much time to spend on the gfx.

None gives a dam '****' about the GFX at the moment, don't see you why we are complaining / laughing? You should have put more time in the security.. To be honest you should have done this when you wrote the code, oh wait half of the code is public. Never mind.

Well it's nice that you've put a warning at the register page but there still are a lot of clueless people who just sign-up without reading the warning. Don't bother telling me they should read it, they won't. You should have kept that in mind.

None can justify using plain passwords in 2015 especially when it's easy to hash the **** thing.

Go read this:

Originally Posted by Tom Moertel

If you are storing passwords in a database, you are almost certainly making a mistake.

This article was written almost 10 years ago even then they already said you can't justify it.

Now let's make a moment of silence for the affected users..

[✔Star✔]

Originally Posted by Sleutel

None gives a dam '****' about the GFX at the moment, don't see you why we are complaining / laughing? You should have put more time in the security.. To be honest you should have done this when you wrote the code, oh wait half of the code is public. Never mind.

Well it's nice that you've put a warning at the register page but there still are a lot of clueless people who just sign-up without reading the warning. Don't bother telling me they should read it, they won't. You should have kept that in mind.

None can justify using plain passwords in 2015 especially when it's easy to hash the **** thing.

Go read this:

This article was written almost 10 years ago even then they already said you can't justify it.

Now let's make a moment of silence for the affected users..

Thanks for your feedback, it's on our list.
We will reply to the topic when we switched over to password encryption.