Earlier quoted context omitted.
> Another alternative is a GPG-encrypted file, though keeping that synchronised between multiple locations might prove a challenge. What's the difference between what you're suggesting here and a password manager? Enxrypted local file, with an optional sync service. I know that if I was setting up my own password manager for security reasons, the sync part is likely the most vulnerable, hence why I would like to offl…
Your personal convention that would keep you unaffected from bulk attacks targeting the tool used by millions in the same way.
Autofill in password managers can allow login credentials to be stolen
101–110 of 144 posts
Re: Autofill in password managers can allow login credentials to be stolen
#102Earlier quoted context omitted.
> Another alternative is a GPG-encrypted file, though keeping that synchronised between multiple locations might prove a challenge. What's the difference between what you're suggesting here and a password manager? Enxrypted local file, with an optional sync service. I know that if I was setting up my own password manager for security reasons, the sync part is likely the most vulnerable, hence why I would like to offl…
Your personal convention that would keep you unaffected from bulk attacks targeting the tool used by millions in the same way.
Re: Autofill in password managers can allow login credentials to be stolen
#103Earlier quoted context omitted.
That was going to be my suggestion. I'm a fan of Zettlekasten for notetaking and knowledge management. Filing passwords on index cards or business cards (3.5x2 in, ~9x5cm), with a sensible indexing system, scales up reasonably well. There's certainly extant physical infrastructure. The typical person has on the order of about 100 online accounts. Managing even 1,000 accounts in an index card file is at least within r…
> Another alternative is a GPG-encrypted file, though keeping that synchronised between multiple locations might prove a challenge. What's the difference between what you're suggesting here and a password manager? Enxrypted local file, with an optional sync service. I know that if I was setting up my own password manager for security reasons, the sync part is likely the most vulnerable, hence why I would like to offl…
The ability to port to any alternative tools that provide superior capabilities, should the need arise.
Utilising the file using standard shell tools (gpg piped to grep, sed, awk, etc.).
I've been around long enough to see multiple tools come and go. Even PGP itself dates from after the beginning of my professional career with computers (though near the beginning). There are multiple applications, operating systems, and architectures I've used which have been relegated to the dustbin of history. I'm quite leery of becoming dependent on any one specific application or tool, most especially one that that's not been proven across multiple decades and widely adopted.
PGP, GPG, vi/vim, or emacs would all pass my tests. They're available on any system I could conceivably use. Even iOS, though with some difficulty.
Encrypting and syncing a file is simple.
Managing syncs from multiple locations of an encrypted file is ... a bit more complicated. Git might be able to manage that with some hooks.
Re: Autofill in password managers can allow login credentials to be stolen
#104Re: Autofill in password managers can allow login credentials to be stolen
#105Re: Autofill in password managers can allow login credentials to be stolen
#106Re: Autofill in password managers can allow login credentials to be stolen
#107Earlier quoted context omitted.
> A piece of paper can easily be found by someone. Much easier than hacking a password manager. A piece of paper in a locked drawer is potentially accessible to a person breaking into it. It is probably an unsophisticated burglar looking for money. They are probably located in the vicinity of your neighbourhood and have rocked up to your home, and will not evade capture for long. They will likely leave DNA. If they d…
If someone sees a list of site/user/pass, wouldn't they take a photo of it instead of stealing the entire notebook? It just seems like the obvious thing to do. >They are probably located in the vicinity of your neighbourhood and have rocked up to your home, and will not evade capture for long. They will likely leave DNA Did you get that from CSI: Miami? Nobody is gonna collect DNA samples just because some stuff went…
Australian here. When my house was broken into Police forensics came that afternoon and fingerprint dusted all points of entry and lifted prints. Do they not do this in your jurisdiction? I have just realised DNA is probably poor shorthand for that.
Re: Autofill in password managers can allow login credentials to be stolen
#108I don’t see the vulnerability. His demo collects credentials then displays them ... all on the same domain websecurity.dev So what? What am I missing? How will he exfiltrate the data? With JS that posts it to another domain?
If the attacker has XSS and gets the password, exfiltration is the easy part. JS offers many options, starting with fetch.
Re: Autofill in password managers can allow login credentials to be stolen
#109Earlier quoted context omitted.
> If some site has an XSS vulnerability, then they've already got access to my session cookies Not true if the website uses HttpOnly session cookies as they should.
They don't need your session cookie either. An attacker can just use XmlHttpRequest to perform any actions as you on the website, and read the web page results. E.g. go to your profile and steal all your personal data. They can also set up a keylogger or fake login screen and wait for you to type or paste in your password yourself. I've always thought HttpOnly cookie flag is overrated. Stealing the session cookie may…
Re: Autofill in password managers can allow login credentials to be stolen
#110I get that this is a theoretical vulnerability, but there's no way I'm turning off automatic autofill. It's way too convenient. If some site has an XSS vulnerability, then they've already got access to my session cookies, and have the ability to spoof a "you've been logged out, please log back in" screen where people could type in a password anyways . If a site is vulnerable to XSS it's basically game over security-w…
Another reply seems to have focused on having XSS causing an attacker to gain access to session cookies. But no one has mentioned using Content-Security-Policy [0] - which if set properly can make it nearly impossible to exploit an XSS vulnerability in the first place.