Question about the 'pass' password manager
-
Sorry, homie. I'm not gonna keep arguing with you if you obviously can't argue without moving the goal posts, if your life depends on it.
My point still stands: Encrypting metadata can be sensible/necessary for your threat model and does not count as security through obscurity. You have failed to explain how it would be.
Encrypting metadata can be sensible/necessary for your threat model and does not count as security through obscurity. You have failed to explain how it would be.
I mean, your scenarios here are predicated on the idea that you're so concerned about privacy and security that you use PGP to protect your passwords, but leave your PC totally unencrypted and not password protected for "the police" to just come in and take and discover metdata about your proclivities.
It's absurd to the n^th degree and how you don't see that is astonishing.
-
Encrypting metadata can be sensible/necessary for your threat model and does not count as security through obscurity. You have failed to explain how it would be.
I mean, your scenarios here are predicated on the idea that you're so concerned about privacy and security that you use PGP to protect your passwords, but leave your PC totally unencrypted and not password protected for "the police" to just come in and take and discover metdata about your proclivities.
It's absurd to the n^th degree and how you don't see that is astonishing.
-
So, I've been using keepassxc for some time now, but I wanted a viable alternative for command line usage (there is keepassxc-cli, that I use, but it is really a pain in the ass). So, I searched and found pass and gopass.
However, I've seen that they store each entry in a gpg encrypted file, inside a plain directory hierarchy. And, don't get me wrong, I believe that there are use cases for this, but if someone got their hands in your password_store, they would know every single login that you have (the only information that is protected is the password, or whatever is in the gpg file).
So, my question is, there is a password manager, cli based, that encrypts the whole database, and not the single entries?
It depends how you use it. There is no requirement as to how you set up your directory structure, so you could have one file "passwords" with all your credentials in, including the website. That would break a lot of plugin's functionality though.
-
So, I've been using keepassxc for some time now, but I wanted a viable alternative for command line usage (there is keepassxc-cli, that I use, but it is really a pain in the ass). So, I searched and found pass and gopass.
However, I've seen that they store each entry in a gpg encrypted file, inside a plain directory hierarchy. And, don't get me wrong, I believe that there are use cases for this, but if someone got their hands in your password_store, they would know every single login that you have (the only information that is protected is the password, or whatever is in the gpg file).
So, my question is, there is a password manager, cli based, that encrypts the whole database, and not the single entries?
I use Unix pass and KeePassXC before that. When I was switching I shared the concern of the names and structure of my passwords . A couple things convinced me it was fine.
First: It’s an arbitrary folder structure. You can name the folders whatever you want. Same is true for individual files. There is a field you can populate with the url the password is for, and when using browser extensions, or a mobile Unix pass manager, they use this field to check which password to offer, so the name of the encrypted file can be anything and so I often name them seemingly random things.
Second: how I chose to sync them made it kind of a non-issue. Some people literally store their password store folder on GitHub. This freaked me out a bit for the reason you are concerned, people even knowing the names of my files. The solution was to self host a git repo on my home LAN and then using Tailscale sync my devices to it from anywhere. Could also be done with syncthing, but the mobile app I use has git functionality built in. This way none of my files even touch the clear net, so I worry a lot less about people knowing the names of my passwords.
-
If the police confiscates my PC because of e.g. piracy, they could nail me down if they also knew that I had an account at a darkweb marketplace
Firstly, if the police confiscate your PC, they already know (and have proven to a judge) that you conduct illegal activity and likely already have enough to convict you of a crime. lol
Secondly, you can have an account at a private torrent tracker (or any website [exluding cp]) and there's nothing anyone can do about it--because that's not illegal... Torrenting isn't illegal, either. Sharing copy written content is and they can't prove that you've done that beyond a reasonable doubt simply because you have an account at a website.
These are exceptionally poor arguments.
Cops confiscate devices all the time without good reason lmao. It's commonplace to seize devices on a person upon arrest. Judges also grant search warrants upon very little evidence too. Cops absolutely don't need to "prove" anything to a judge to get a warrant; there is no standard of proof at all; it's a standard of evidence, which is not the same thing as proof, and a low standard of evidence at that.
-
System shared this topic on
