-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Are there any examples, to your knowledge?
G - ----- Original Message ----- From: "Dave Jevans" <[EMAIL PROTECTED]> To: <fde@www.xml-dev.com> Sent: Tuesday, July 22, 2008 6:53 PM Subject: Re: [FDE] ver 6.0 of TrueCrypt > > It's a lot easier to build in obscurity with hardware support rather > than trying to do it in software like TC. > > At 4:00 PM -0400 7/22/08, Garrett M. Groff wrote: >>-----BEGIN PGP SIGNED MESSAGE----- >>Hash: SHA1 >> >>Interesting. Looks like obscurity is hard, too. >> >>G >> >> >> >> >>- ----- Original Message ----- >>From: "Duane Dyar" <[EMAIL PROTECTED]> >>To: <fde@www.xml-dev.com> >>Sent: Tuesday, July 22, 2008 2:18 PM >>Subject: Re: [FDE] ver 6.0 of TrueCrypt >> >> >>>I noted this in Dark Reading in relation to TrueCrypt. >>> >> > http://www.darkreading.com/document.asp?doc_id=159192&f_src=drdaily >>> >>> Duane >>> >>> >>> -----Original Message----- >>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >>> On Behalf Of Garrett M. Groff >>> Sent: Monday, July 14, 2008 2:20 PM >>> To: fde@www.xml-dev.com >>> Subject: [FDE] ver 6.0 of TrueCrypt >>> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> New features include (my summary): >>> >>> * parallelized encryption/decryption (to take advantage of multi-core >>> computers that are all the rage these days) >>> * plausibly deniable hidden OS support >>> * backup of volume header (reliability update) >>> * ability to create hidden volumes on Mac/Linux >>> * some other stuff... >>> >>> Of all the new features, the "hidden OS support" looks the coolest, >>> since most FDE products (for the OS) don't do this (meaning you're >>> still >>> susceptible to the "gun to the head" scenario). >>> >>> - -- >>> >>> I wonder if/when TC will support TPM chips, allowing for PIN entry >>> ('stead of entering a complex p/w on startup) and pre-boot integrity >>> checking). >>> >>> G >>> >>> -----BEGIN PGP SIGNATURE----- >>> Version: PGP Desktop 9.8.3 (Build 4028) - not licensed for commercial >>> use: www.pgp.com >>> Charset: utf-8 >>> >>> wj8DBQFIe6avSGIRT5oVahwRAvCzAJ9TvPxdIB3ahBIRpEwbaDjGPPkssgCfW4fg >>> 7Bb1XG10gtjPOW4kNdWtzQI= >>> =N1sp >>> -----END PGP SIGNATURE----- >>> >>> _______________________________________________ >>> FDE mailing list >>> FDE@www.xml-dev.com >>> http://www.xml-dev.com/mailman/listinfo/fde >>> >>> >>> _______________________________________________ >>> FDE mailing list >>> FDE@www.xml-dev.com >>> http://www.xml-dev.com/mailman/listinfo/fde >> >>-----BEGIN PGP SIGNATURE----- >>Version: PGP Desktop 9.8.3 (Build 4028) - not licensed for >>commercial use: www.pgp.com >>Charset: utf-8 >> >>wj8DBQFIhjxYSGIRT5oVahwRArqiAKCtNwEHCeTvmXJlzHOwP6/CBlfmIwCgyVRc >>o227bAt8JaptBclvygVhrt0= >>=5cTi >>-----END PGP SIGNATURE----- >> >>_______________________________________________ >>FDE mailing list >>FDE@www.xml-dev.com >>http://www.xml-dev.com/mailman/listinfo/fde > > _______________________________________________ > FDE mailing list > FDE@www.xml-dev.com > http://www.xml-dev.com/mailman/listinfo/fde -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.8.3 (Build 4028) - not licensed for commercial use: www.pgp.com Charset: utf-8 wj8DBQFIhyZqSGIRT5oVahwRAvcAAKCptzsRu9pH7Wjg0hQYFy1pnQhKSACgseuD eBIcQ3lYlXUesI/VTcERYdU= =oaZr -----END PGP SIGNATURE----- _______________________________________________ FDE mailing list FDE@www.xml-dev.com http://www.xml-dev.com/mailman/listinfo/fde
