On Thu, Nov 24, 2005 at 01:41:34PM -0500, Vili wrote: >>>>In TBV, we can see that all files are encrypted, but the main >>>>setting file, global.ini remains unencrypted, why ? is it deliberate >>>>and for which reason ? >> Some settings are needed for the program before it initializes the >> OTFE, prompts the user for the password, and so on. That's why the >> global.ini is not encrypted. We will probably split this config file >> to two files, one of them would be encrypted, while another will >> only keep startup parameters. > > What if you implement a BUILT-IN encryption in TBV already, and you > use this built-in enc/decryption to enc/decrypt global.ini?
PMFJI, but what should this be good for? A built-in encryption would have to use a fixed key. It will be only a matter of time until this key is disassembled from the binary and a program (can) exist that reads the encrypted 'global.ini' as well. So nothing will be won then. Just my 0.2 ยข ... ;-) -- Ciao, Pit ________________________________________________________ Current beta is 3.63.05 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
