Skip to content
This repository has been archived by the owner on Jan 22, 2022. It is now read-only.

SECURITY ISSUE: Mishandling Credentials #69

Open
5 tasks
0xtejas opened this issue Mar 10, 2021 · 3 comments
Open
5 tasks

SECURITY ISSUE: Mishandling Credentials #69

0xtejas opened this issue Mar 10, 2021 · 3 comments
Assignees
Labels
Priority This issue is Important Security This is very much important to prevent mishap

Comments

@0xtejas
Copy link
Contributor

0xtejas commented Mar 10, 2021

This is a final checklist before 1st production Release

  • Store Usernames and Passwords in more safer way, Instead of plain text format.
  • Update passwords after the implementation of previous step.
  • Have a strong password with 8 or more characters with symbols and numbers.
  • Store passwords of users in hashes in the DB, instead of plain text.
  • Enable 2FA.
@0xtejas 0xtejas added Priority This issue is Important Security This is very much important to prevent mishap labels Mar 10, 2021
@0xtejas 0xtejas added this to the First Production Release milestone Mar 10, 2021
@0xtejas
Copy link
Contributor Author

0xtejas commented Mar 10, 2021

There are two tables, with credentials. One stores them in hashes other in plain text. Need discussion

@sanjay-thiyagarajan
Copy link
Contributor

Yeah. You can work on this if you are interested 👍🏽

@0xtejas
Copy link
Contributor Author

0xtejas commented Mar 10, 2021

Yeah. You can work on this if you are interested 👍🏽

I don't have idea on how the tables are created and stuff... As you have implemented those, its better if you do it rather than me trying to messing with those 😂

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Priority This issue is Important Security This is very much important to prevent mishap
Projects
None yet
Development

No branches or pull requests

2 participants