In the same way, metaphorically, you wouldn't create a RED dollar bill on the surface. Of course on the surface the output file is going to match the open source counter-part. The TrueCrypt team expressed concerns over what could be done within an encrypted API if the designer wanted to create a sinister internal environment. Your response is only accurate if in fact you fully trust the closed source M$ API, which VeraCrypt and TrueCrypt use for their hardware acceleration option. I turn off and use the established method, but again, its your call. Only rarely will I pick a small speed differential over security. I personally elect to use the open source and "known" AES afforded by TrueCrypt and now Vera Crypt by default. I guess to be consistent you either trust Microsoft or you don't. The acceleration API came from the same company that made Windows. You will have to make up your own mind on this. We examined this over many threads at the TC forum throughout the years. because you want TrueCrypt to use only a fully open-source implementation of AES), you can do so by selecting Settings > Performance and disabling the option ‘Accelerate AES encryption/decryption by using the AES instructions of the processor’ If you want to disable hardware acceleration of AES (e.g. # This AES-API that came from Microsoft is encrypted and is not open source requiring you to trust Microsoft!! The latest TrueCrypt takes advantage of pressure directed from TrueCrypt towards Microsoft in the wake of version 6 that requested an API for hibernation files, which had not existed previously. Two articles with a couple of snips to point you in the direction to learning. TrueCrypt had NO control of the provided AES-API. Click to expand.You missed my point so let me elaborate.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |