can you please explain the strength of veracrypt and keepass compared?
Whats theoretically easier to break if both use the exact same password for their respective containers, the vcrypt or keepass file?
Are they both still considered in the dev community as "unbroken" and safe encryption tools for storing data? Or are there successful attacks publicly known? Do they currently have any known weaknesses in their code bases?
Lets say you have a Text.txt file. In one case this txt file is stored in the vcrypt container. And a second time in the keepass kdb as an attachement. Now, when you open both on your windows system (mounting vcrypt and opening keepass kdb), which one is in this "opened state" more vulnerable to what kind of attacks? Which one isolates .txt file in a better way? Here you can consider that you are connected to the Internet while those files are open and you can consider any other attacks.
In case of veracrypt: Is the file safety somehow decreased, when we start opening the text .txt file from within the vcrypt container? How does that impact potential unwanted file access?
what difference does it make in vcrypt selecting algorithms in different order? eg serpent-aes or aes-serpent. What impact does the order have on bruteforcing attacks?