note 117431 added to security.database.storage

It's difficult to post scripts here for all to view on the subject of best security practices. But i would wish to point out that using a salt with a randomized and odd numbered long length salt value is do_able with two Php functions while retrieving and separating the salt when it comes out using simple math functions. But with everything we add we also have to think of the constant standardized login systems we stay behind with. For one,,, adding and validating two to four passwords is not a bad idea. Also having no username or email going in. They can be stored after the user logs in after the validation process. It is possible to store the email on the first signup and only at that time. And if the user loses his passwords then validate by email only upon request within a contact form by a validated phone number stored in the database,, and then via their email account. ---- Server IP: 72.52.91.14 Probable Submitter: 2602:304:6eec:e6f9:1dee:e1f4:cf0e:efbe ---- Manual Page -- http://php.net/manual/en/security.database.storage.php Edit -- https://master.php.net/note/edit/117431 Del: integrated -- https://master.php.net/note/delete/117431/integrated Del: useless -- https://master.php.net/note/delete/117431/useless Del: bad code -- https://master.php.net/note/delete/117431/bad+code Del: spam -- https://master.php.net/note/delete/117431/spam Del: non-english -- https://master.php.net/note/delete/117431/non-english Del: in docs -- https://master.php.net/note/delete/117431/in+docs Del: other reasons-- https://master.php.net/note/delete/117431 Reject -- https://master.php.net/note/reject/117431 Search -- https://master.php.net/manage/user-notes.php