I have some files that are critical to be secure. I keep these files inside an encrypted VeraCrypt container, on an encrypted SSD. So, it is critical to have a password to my SSD that is hard enough to find, even for the government.
The problem is that the password for SSD is very complex, so I keep it inside to another VC container with a password that I can remember in 100% of the cases, but isn’t strong enough. The SSD password is stored in this format: (lots of random characters)+(actual password with some decoy characters)+(other lots of random characters).
So, instead of keeping the SSD password as text, I want to use an algorithm that will generate the actual SSD password, using as a starting point another text.
Let's say I have these random characters as beginning. “B|(=h&jMRSl(Hz2IO2“. I will convert them text ASCII “66 124 40 61 104 38 106 77 82 83 108 40 72 122 50 (+ additional three numbers before last three ASCII, ex. 44) 73 79 50“. After, I will convert ASCII version to SHA256 “c2338bdaca948b6d30c135817bce23488713e35e635da7f898dd5d6af0c80b5f“ , and this will be the new SSD password.
I think that this is a valid solution to my problem. But, since I don't have a background in cryptography, my question is if this is a secure way to keep a hard-enough-to-crack-password and what are the odds for a cryptography specialist from the government to find the final password (assuming I don't make any stupid mistakes).
The problem is that the password for SSD is very complex, so I keep it inside to another VC container with a password that I can remember in 100% of the cases, but isn’t strong enough. The SSD password is stored in this format: (lots of random characters)+(actual password with some decoy characters)+(other lots of random characters).
So, instead of keeping the SSD password as text, I want to use an algorithm that will generate the actual SSD password, using as a starting point another text.
Let's say I have these random characters as beginning. “B|(=h&jMRSl(Hz2IO2“. I will convert them text ASCII “66 124 40 61 104 38 106 77 82 83 108 40 72 122 50 (+ additional three numbers before last three ASCII, ex. 44) 73 79 50“. After, I will convert ASCII version to SHA256 “c2338bdaca948b6d30c135817bce23488713e35e635da7f898dd5d6af0c80b5f“ , and this will be the new SSD password.
I think that this is a valid solution to my problem. But, since I don't have a background in cryptography, my question is if this is a secure way to keep a hard-enough-to-crack-password and what are the odds for a cryptography specialist from the government to find the final password (assuming I don't make any stupid mistakes).