Hmm, seems to me using both is optimal horrible psuedocode follows... cryptchoice = len(username) % 3 switch cryptchoice: case 0: pepper = pepper[1] salt = email case 1: pepper = pepper[0] salt = creation_time case 2:…
What can someone use as a salt that is unique to a user that would not be in that record as plain-text and guess-able? Creation timestamp? email? username?
Being colorblind, This map is completely useless. At least the table is there
while(read(article)) { if(galaxy === universe) { clickbait++; break; }
Hmm, seems to me using both is optimal horrible psuedocode follows... cryptchoice = len(username) % 3 switch cryptchoice: case 0: pepper = pepper[1] salt = email case 1: pepper = pepper[0] salt = creation_time case 2:…
What can someone use as a salt that is unique to a user that would not be in that record as plain-text and guess-able? Creation timestamp? email? username?
Being colorblind, This map is completely useless. At least the table is there
while(read(article)) { if(galaxy === universe) { clickbait++; break; }