Darkphantom
Brandon so far as I've seen overall "harder" securaty is not a solution it only makes it harder to solve when everything dose goto s**t. becasue so much power has been displaced off the user to the system that there is all too often nothing you can do.
Except that I'm not sure why you can't trust a hardware implementation of MD5. The function of TC is to offload common validation techniques into tamper-resistant hardware. In and off itself, this is not all that bad of an idea.
Quote:
Becasue you can bet that it will be hacked and pepole will devise methods of cracking MS and its s**t whtich will allow it to be forced into the trusted part of the system.. and I want a chance to defend myself with applications that those virus creators won't expect. Your just lettling yourself become a sitting duck if all the "trusted" Antivirus applications are written down on a peice of paper for anyone to see.
Cracking systems is getting harder with things like NX. And the concept of TC is that applications will have something like an SSL certificate which includes a hash that indicates the application is, indeed, what it claims it is.
Quote:
I've only ever experinced one case of BIOS hijacking... and even when it screws up you can simply reset the CMOS to restore fully functionallity. I'm a firm believer of
user > system;
System securaty == unintrusitve;
If the user can circumvent the system, then security has failed. And it's well known that security is a trade-off between functionality and safety. The trick is to put security measures in place that are effective and minimally intrusive. Hardware-computed checksums based on an embedded digital certificate that throws an alert when the file doesn't match the signature sounds like a good bet to me.
