[Preview] 4Story Website Core

[caiverzi1]

Hello guys , i was long time away from this community
What i present you right now is old v4story website , due some personal problems i left from v4story project...

I had some free time and i reopen my old work..
The design of website is a fusion of p4story,zemi4s,opora4s
The website is not yet ready, when I finish I would put a link to a livepreview

Website Features:
Every single functions is written in PDO.
#Donation
#Login
#Userpanel
#Lottery
#News
#Vote
#Multilanguages
#Activation by email
#Forgot Password
#Resend activation link
etc...

Some screens


If u want to help me with translation of website , you are free to text me









i will update theard soon maybe with link for livepreview or with a video ... who cares anyway xD
#MCCALL

[depaki]

thats pretty dope

[.Konst]

Looks pretty good, I must admit

[Logtetsch]

Md5 Password checksum? Did you already know that md5 is deprecated? You should really move to a more new & dope solution like sha2 or sha3 ... just in case you care about your users

[.Konst]

Originally Posted by Logtetsch

Md5 Password checksum? Did you already know that md5 is deprecated? You should really move to a more new & dope solution like sha2 or sha3 ... just in case you care about your users

4Story only supports upto Sha1

Originally Posted by Logtetsch

Md5 Password checksum? Did you already know that md5 is deprecated? You should really move to a more new & dope solution like sha2 or sha3 ... just in case you care about your users

Also you still cannot decrypt MD5. The only way to obtain MD5 Passwords is by "Dictionary Attacks" or brute forcing, which also work on other Encryption methods.

[Logtetsch]

Well, you are working directly with the source code .. soo .. where's the problem to implement or import a sha2 / sha3 library to your project? Since md5 is not an encryption solution, it can't be decrypted. The real risk that comes with md5 is

Using salted md5 for passwords is a bad idea. Not because of MD5's cryptographic weaknesses, but because it's fast. This means that an attacker can try billions of candidate passwords per second on a single GPU.

Source:

KR Logtetsch

[.Konst]

Originally Posted by Logtetsch

Well, you are working directly with the source code .. soo .. where's the problem to implement or import a sha2 / sha3 library to your project? Since md5 is not an encryption solution, it can't be decrypted. The real risk that comes with md5 is



Source:

KR Logtetsch

As much as I remember it's the SQL Server that refuses to work with it.

[Logtetsch]

Why? The field type is as far as I can remember defined as a VCHAR(x) or TEXT, isn't it? The SQL Server itself is just as smart as a garbage can. There is no build-in md5 or sha2/3 data type so it doesn't know about it's real world object data type. Therefore it just can't say "oh, wow, you are working with SHA2/SHA3 objects, hehe, I will block them u fool :evil: ".

KR Logtetsch

hint →

[michamo]

Originally Posted by .Konst

4Story only supports upto Sha1

Who said to you this deception?
Varchar could be large to 2^31-1. So where is problem?
BTW.
SHA-256 have 64Bytes
SHA-512 have 128Bytes

[.Konst]

Well maybe we did something wrong, but when we tried to convert text to sha256/512, it came out as (NULL).

Also according to a few articles I've found on the Web, SQL Server 2008 indeed only supports upto SHA1

[Logtetsch]

That sounds kinda stupid. I'm pretty sure you did something wrong

string passwordChecksumSha3 = createChecksumSha3(password).toString();
database.insert(passwordChecksumSha3, tblPasswords);

^You have to work with plain text.

KR Logtetsch