maprox / keyholder-angular Goto Github PK

There're multiple places like this:

It should not be used for storing real passwords, since it's a demo server and might be restarted (data might be lost)!

It should be simple key-value database,
Key is generated on front-end, based on login (email?) and password.
If entry exists - it's being passed to the front-end end decrypted there.
Proposed table structure:
Key / json {login, encrypted json data {root, settings}}

endpoints suggested:

1. POST /api/signup/
   Body: login, key
   200 - OK + encrypted json data {root, settings}

2. GET /api/storage/{key}
   404 - Not Found
   200 - OK + encrypted json data {root, settings}

3. PUT /api/storage/{key}
   Body: encrypted json data {root, settings}
   400 - Key Not Found
   200 - OK

• Add/display validation for the fields
• Do not allow to send invalid data

Password minimal requirements:

• = 8 symbols

• At least one of A-Z, a-z, 0-9, and "special" char (e.g. !?#$ etc.)

tbd

Add settings page with default:

• password length
• password characters

Add "retry" link to the offline bar which will recheck connection.
Add countdown to reconnect (gradually increase interval between attempts, e.g. 15s, 30s, 1m, 2m and so on).

Send impersonal hash instead of the email as a login, so there'll be no information about the user on the server.

• name
• secret (hidden, autogenerated, show on click, hide on blur)
• notes (hidden, empty, show on click, hide on blur)
• save button
• delete button (in edit mode)
• regenerate button (near secret field)

Add sign in and sign up page.

Copy password to clipboard when user clicks on secret.

Add service to generate a password based on settings length and chars.

Make app available offline

npm

Add ability to change the password.
It will be new account actually.
We should remove old one on success.

Add ability to tag secrets and folders

Implement searching by title

Do not allow slashes in folder name.
Display validation error in case it's been entered.

Integrate tests with Travis CI

Appropriate folder should be opened based on the url path, e.g. /storage/level1/level2

• No root in the path

Cover code with unit tests

Examples:

storage//
storage//folder1/
storage//folder1/folder2

If user reloads the page root is being opened instead of the folder where user was before.

Investigate possibility (pros and cons) of using IPFS as a backend storage.
OrbitDB in particular.

Focus on first input when adding folder or secret