Open KSanjith opened 4 days ago
[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]
Dear tester,
The team has discussed and decided to categorize the bug as not in scope. The following are the justifications:
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your reason]
Details: Given how seriously the user's security and privacy are taken, one might expect that the app would not accept blank passwords to be set. However, that is not the case. Careless first time users might accidentally press the enter button when first launching the app, which the app would take to as the password. This poses a major security risk due to the password being left blank.
Steps to Reproduce:
Expected: App warns user that the password field has been left blank, and asks them to create a new proper password.
Actual: App accepts the empty password and continues on as normal.
Screenshot: