![]() With this type of attack the hacker or let's say maybe a gov't looks at an encrypted piece of data and is able to determine that the key for accessing that the data actually only falls within a key space of 100,000 possibilities vs. ![]() And that sort of makes sense because lately the threat to encrypt should that we've been seeing has been an attack on the keys space. So if the known vulnerabilities aren't there there's only 1 other police for it to exist and that's in the encryption algorithm itself. This is actually sort of the interesting because traditionally these are the places where you'd expect to find those things because vulnerabilities here would essentially allow you to trick your way into the encrypted data. ![]() The audit found that there were no major vulnerabilities or backdoors in this part of troop crypt. In the first part of the audit the parts of true cryp that were a analyzed were the boot loader and the kernel drivers or at least they were the primary focus of the audit. So what is it that we know about true cryp to right now? We know that the first part of the independent audit cryp Autoit is complete. The one thing we can be sure of is that they bought somehow the product was vulnerable and whether they actually knew specifically with what was vulnerable war what the vulnerability was that might be debatable. Who knows why they did this was it because they wanted to protect users of the product during the transitional time that they would need to move from true crypt to another product? Did they do it because they thought that true crypts would be found to be vulnerable to warring Indian head being independent audit of the software and dean one a few like they ended up with egg on their face after almost a decade of development? I don't know and I don't think anybody ever will. When the true crit project was shattered the dead simply stated that the software was vulnerable in that you should use something else they were very nonspecific and it didn't bother to provide any detail as to what the vulnerability actually was. Well I had a big long explanation typed up as to why true crypt is possibly vulnerable but my cat jumped on the keyboard and its that's all gone now I probably should have typed the response in a word processor first and then pasted into the response box but I didnt so now you get the voice recognition dictated version it's going to be messy and lacking a lot of punctuation and I apologize for that but it's a nice day out and I want to get out on the bike.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |