cuchilloc @ cuchilloc @lemmy.world

Posts

0

Comments

200

Joined

2 yr. ago

Once you master password gets leaked, attackers would also need to know:

• the master “user” (basically a second password)
• the website/app name pattern you use (basically a third password)
• Which algorithm or password generator you are using, and in what setup/config/

iTerm

Stopped reading at “storing my passwords on a db”. Even if you encrypt the data, is it not just plain better to use a generative algorithm for passwords instead that needs no cloud? Why would you even introduce the vulnerability yourself of storing passwords somewhere in the first place? Keep it simple, you don’t want to over-engineer yourself to death, especially if you are actually downgrading your security by building too far ahead of what you actually need.

I suggest you watch Berserk.

I think as UIs get better you will be able to handle that on front end. Like even have curated lists of specific subscriptions.