Update DB to include information for securely storing passwords #21

Activity

1. jslopezgithub

   added

   taskSomething needs to be doneSomething needs to be done

   databaseTasks related to the databaseTasks related to the database

   loginThis includes all the tasks for creating the loginThis includes all the tasks for creating the login

   on Dec 13, 2019
2. jslopezgithub

   added this to the Login Functionality milestone on Dec 13, 2019
3. aliskhanoff commented on Dec 15, 2019

   

   aliskhanoff

   on Dec 15, 2019

   Collaborator

   More actions

   @jslopezgithub Is not clear.
4. jslopezgithub commented on Dec 15, 2019

   

   jslopezgithub

   on Dec 15, 2019

   OwnerAuthor

   More actions

   Did you read the link in #20?
5. aliskhanoff

   self-assigned this

   on Dec 16, 2019
6. aliskhanoff commented on Dec 16, 2019

   

   aliskhanoff

   on Dec 16, 2019

   Collaborator

   More actions

   Yes, i readed it and i know about encryption. Should i store HMAC key generated for each user into database?
   
7. jslopezgithub commented on Dec 16, 2019

   

   jslopezgithub

   on Dec 16, 2019 via email

   OwnerAuthor

   More actions

   Based on the article, if you are to use password stretching what information would you need to store in the database? Il lun 16 dic 2019, 02:16 Ramazan aka 0xBADC0DED <notifications@github.com> ha scritto:

   …

   Yes, i readed it and i know about encryption. Should i store HMAC key generated for each user into database? [image: HMAC] <https://user-images.githubusercontent.com/41637477/70883644-efcd6f80-1fd3-11ea-9421-04a66ca464ee.png> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#21?email_source=notifications&email_token=ABWJL6OI7JLYDQEDN4UEGFLQY4MM5A5CNFSM4J2MH262YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG5UMFY#issuecomment-565921303>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABWJL6J4XCUQPQ4O2MJOVVDQY4MM5ANCNFSM4J2MH26Q> .