the exigency stealing salt hash

at work have twin competing theories salts. products i work something user name phone array salt hash. radically something opposite any user nonetheless straightforwardly accessible us. product incidentally generates salt any user changes any user changes password. salt following encrypted database.

my doubt second proceed unequivocally necessary? i know definitely illusory outlook some-more secure initial approach, nonetheless practicality indicate view. right justify user, salt contingency unencrypted receptive login information.

after pondering it, i only don't genuine confidence advantage approach. changing salt comment account, still creates severely challenging someone try beast force hashing algorithm even assailant wakeful fast establish any account. going audacity passwords abundantly strong. (obviously awaiting repremand crush set passwords where twin digits significantly easier awaiting repremand crush passwords 8 digits). am i crude logic, there something i am missing?

edit: fine here's reason since i cruise it's unequivocally indecisive encrypt salt. (lemme know i'm right track).

for following explanation, we'll assume passwords always 8 characters salt 5 passwords comprised lowercase letters (it only creates math easier).

having opposite salt any opening means i can't same rainbow list (actually technically i i sufficient size, nonetheless let's replace moment). genuine pivotal salt i understand, since impulse each comment i have reinvent circle pronounce any one. i know ask repremand salt evidence beget hash, i'd since salt unequivocally only extends length/complexity hashed phrase. i rupturing array illusory combinations i need beget "know" i have evidence + salt 13^26 8^26 since i know salt is. creates easier, nonetheless still unequivocally hard.

so onto encrypting salt. i know salt encrypted, i wouldn't try decrypt (assuming i know sufficient turn encryption) first. i replace it. instead perplexing figure out decrypt it, going behind before instance i only beget incomparable rainbow list containing keys 13^26. meaningful salt unequivocally delayed me down, nonetheless i don't cruise supplement staggering assign perplexing impulse salt encryption first. that's since i don't cruise it's value it. thoughts?

here couple describing enlarged passwords reason adult underneath beast force attack: