Any explanation of Why to not store passwords in plaintext and encrypt folder in zip archive (I guess U cant break pass?) Pls don’t be agressive!!
You must log in or register to comment.
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn’t great, if contents of the website are behind a paywall maybe copy them into the post
- Don’t promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
- 0 users online
- 57 users / day
- 383 users / week
- 1.5K users / month
- 5.7K users / 6 months
- 1 subscriber
- 2.44K Posts
- 57.5K Comments
- Modlog
I use KeePassXC
It stores your passwords in an encrypted file, then i use the random password generator, the browser extension and free phone apps to autofill everything.
(It is up to you to sync the file between devices)
There’s two avenues for opening an encrypted file, attacking the password/access method or attacking the encryption itself.
Generally using a basic zip-lock is not going to have a second factor, a rate limiting mechanism, anything really other than the password to stop a random brute force effort if they got a hold of the file for local processing.
Using something with some front end protection like bit warden with 2FA or keepass with the key file option added in makes it more a task of going after the crypto itself which is a much much harder approach.
Because it’s bad, prone to errors, user interface is poor and relies on you following your process perfectly every time.
Bitwarden.
Or KeePass.
KeepassXC if you’re on Linux and KeepassDX on android, preferably on Fdroid.
Bad UX and lack of any integration like autofill or autotype, thats it.
Depends against whom you are protecting yourself. If it’s against
Note I’m NOT a security expert so… don’t believe me.
I don’t know that I’d really add more. It all depends on who and what you’re protecting against. The only thing that’s secure is something that doesn’t exist.
National level hackers have access to resources you might not be able to think of. And if they really want in, rubber hose cryptography is super effective. But most “hackers” on the Internet? And encrypted zip is often enough to deter them. Not impossible, but you might not be worth the time and effort.
In summary, there is better. Much better than an encrypted zip file. But only you can judge if you’re a juicy enough target to pursue more esoteric protection.
You can. You can also light your house with just candles. Its just not a very efficient or effective way of doing it and you lose out on modern features.
I’m curious: what modern features are you looking for when setting your house on fire?
deleted by creator
If you do this, you’ll start writing small scripts to help you with repeating tasks, to simplify somethings, then you’ll start looking for help trying to improve those scripts, then you’ll find better written and tested ones and start replacing yours with those, one by one. Then you’ll probably find pass or other terminal password manager. It can be a fun learning experience but sooner or later you’ll end up using a password manager.
Ah, the programmers pilgrimage. The first hill that they must climb is the one where they spend 12 days automating something that would have taken 10 seconds every time + half hour setup time.
Pass is pretty cool, used it for many years
Now switched to vaultwarden so it’s more user friendly for my girlfriend
To add to the rest: A manager also stores the history. And it has a pass generator. And lots of quality of life things.
deleted by creator
In many unzip utilities, they use temp files that you wouldn’t be paying attention to. These temp files will contain your credentials and you won’t know where they are or if they got deleted.
And even if they’re deleted by the archive program, it’s likely a normal deletion, and not a secure delete where the original data is overwritten with random data before deleting the entry in the file system, which could be potentially recovered.
Also an excellent point
Zip uses very bad encryption that is vulnerable to a known plaintext attack. Do not ever use PKZIP encryption for any purpose https://github.com/kimci86/bkcrack
They added AES encryption to the spec 20 years ago. It’s pretty-well supported AFAIK.
Yeah zips have no mechanism to prevent brute forcing as far as I’m aware. You can attempt as many passwords as you want as frequently as you want without any sort of rate limit.
That’s not the issue. You can attempt as many passwords as you want in actually secure password managers as well. KeepassXC for instance IS secure, you can still brute force the password, but because of the hashing algorithm they use it’s extremely hard. With PKZIP if you know some of the words in the file, you can easily guess the password in just a few hours because the encryption algorithm it uses isn’t secure
Both are true. Brute forcing zips is also faster than brute forcing almost anything else. Other formats use key derivation functions like PBKDF2-SHA1 (hundreds of thousands of iterations of sha1) to slow down the calculation of the key from the password, but PKZIP does not do this. Brute forcing zips can be done at 10 billion passwords per second on a typical GPU, whereas rar/7z/keepass are only a few thousand per second.
Here’s an interesting research paper describing both the known plaintext attack and the standard brute force attack https://www.scitepress.org/Papers/2019/73605/73605.pdf
I used to get some documents sent in a password encrypted zip file, they regularly messed up the password, so i ended up just brute forcing them when i received them since it was easier and faster (usually like 15 seconds)
Not very relevant here since i knew roughly the length of the password and it was quite short, but i thought it was pretty funny
Oh interesting, thanks for the clarification
I dont see the “manager” part in your zip archive…
More like a bunch of text files… and you are doing the job of the manager
pass has a similar spirit, where passwords are just GPG encrypted files with some CLI glue on top.
You could achieve the same with an encrypted .zip file and a bit of bash, even if it would probably be less ergonomic.
removed by mod
This depends on how the decompressor is implemented. It’s certainly possible to do it all in memory.
removed by mod
One thing to think about is the encryption quality of a zip file, which I ignore.
One danger that I see is that you have the risk of having the passwords on the clear all over the place many times. Not an expert so don’t quote me on this, but password managers are careful avoiding passwords on the clear as much as possible.
I don’t trust any online service for that, I am using keepass/syncthing for myself, with android as the only client decrypting (as I always have my phone with me). one example of advanced security measures is that while using the app I can’t take screenshots, and I hope/expect that it uses images backed by secure memory to show them to me and is careful with things like RAM and temporary files (didn’t check personally though, although being open source I could)
Having to be sure that your zip app handles that seems like a hustle honestly. On top of having random passwords without the biases I would add for each separate site.
I suppose there’s nothing wrong with it when the file is at rest, it looks like zip uses AES 128 or 256 which are adequate if you have a very strong password for the encryption. Ideally the encryption would feature a computationally intensive algorithm to slow guessing attempts when attempting to decrypt so you probably don’t want to use a weak password.
Usability won’t be great, you’ll be copy pasting constantly and that presents an opportunity for malware to spy on the paste buffer and steal your passwords but it’s a low to medium severity issue.
If you want to keep everything local I’d recommend KeePass, it’s free, open source, and very strong. It’s kinda the same thing but with the ability to insert passwords directly in some cases and can do more to keep everything organized.
If you want to use this in environments where you can’t install anything on the systems but don’t want anything online, this is probably acceptable though.
I’d like to mention Bitwarden as well. It’s open source, free(mium) with the option to self-host.