next »

[advanced-scape]

mmk thanks heapr prime

[baton1]

I would do all of that to have better protected site. But how it should look like in my case - I want to have some zones, where one is everyone accessable, and few are for only one man (one login and password), but every zone for different man? I mean I need few accounts for few pages, not one or few for all.
So where should be any changes? And should I create few files with php script for every password?

[Primefalcon]

I agree 100% with everything you just said bind but....

Code:

ps- i agree about the salted hashes too .... its much harder to brute force

I assumed that was about the passwords, my bad, so I well still agree with what you said

I would do all of that to have better protected site. But how it should look like in my case - I want to have some zones, where one is everyone accessable, and few are for only one man (one login and password), but every zone for different man? I mean I need few accounts for few pages, not one or few for all.
So where should be any changes? And should I create few files with php script for every password?

well you could use that script as a base, but you would have to have a mysql database and have the password and username pulled from the database to be checked against, which is where the password hashing that Bind and I were talking about becomes very important.

Wouldn't you agree bind

[bind]

yes I agree.

he needs a website user administration and authentication system for that level of functionality.

It can be accomplished with any flatfile, SQLite or MySQL, but MySQL is the most efficient that can be used on 110mb.

[Primefalcon]

also the most secure as well