Find a hidden file with a password to get it out of an invisible folder
Find a hidden file with a password to get it out of an invisible folder
Does it make sense to put an encrypted file inside another encrypted file? For instance: putting "Encrypted Word.doc" into a folder called "Files.rar" with password 567, and then putting that whole package again into another archive named "Files2.rar" with password 1234. I'm doing this because I want to add more protection so hackers can't crack my first layer of security (password 1234) later on. Is it safe? Or could adding or taking out files inside the archive mess things up over time? I've actually done this for years without any trouble, but now I'm worried about something happening in the future.
It's not really unsafe either, but it offers very little security actually. If someone can get past the first layer, then getting through the second or third should be easy too. Unless this is meant to make a working cold fusion reactor happen, nobody cares about your Word document anyway.
Yeah, people who are hackers or other sneaky guys can do that all the time. But this is just for "user area" stuff. Some bad people want to mess with my work. They can't break the locking system without me being there, but they can unlock it if I make a stupid mistake. One time he tried something while I was typing my password, and then got confused because he typed three different @ signs in 20 characters.
If you have an encrypted rar file or another compressed-encrypted thing like zip or 7z, let's pretend we figure out how to get a new file from that archive. The new file might actually be a real rar file, but it could also just be random junk data that looks exactly like one by chance. To check if something is really valid, you need the right password. So here is my question - How can I tell the difference between a bunch of random data that happens to look like a real rar file versus an actual encrypted rar file without the password? Last but not least: I have to assume that the names, attributes, and folder structure are all locked up too (and of course the format actually supports encryption). And yes, there must be a different password for each nested layer.