Assword

Heres how the new frontend works: It's all in one html file, an app.js file hides/shows sections based on button clicks and such. The other js files (Vault, signup, login) all run at button clicks and used session storage to get the jwt, salt, and email. The masterpassword is stored in a shared js file. The request code is very similar to V1, just simplified to run on a button click. api.js (file for all calls) now never calls crypto.js(file for all encryption stuff), all encryption is handled by the other js files. The auth and encryption key are now derived using PBKDF2 (SHA256). The frontend is up on my domain (assword.simoncrystal.dev)! Also now the backend will only accept requests from that domain, making it harder for possible attackers

Right now the frontend "works" but has some issues. Its four pages of bare html linked to js pages. Two extra js files handle encryption and api calls respectively. However the frontend has a fundamental flaw: the pages only store data for eachother in session storage, so storing the masterpassword here wouldn't be secure. Now the frontend is capable of: - Signing up a new user - Logging in a user - Making entries - Displaying entries That sounds like everything but it isn't, the UX is really bad. The user needs to re-enter there password every time they: - See their entries: - Make an entry - log in Also every entry is just displayed on the screen so your passwords are exposed every time. I want to make a frontend that is: - One page, elements change with js - looks WAYYY better - Has better UX