Sebastian G. wrote:

> Cyberiade.it Anonymous Remailer wrote:
>
> > Sebastian G. wrote:
> >
> >> nemo_outis wrote:
> >>
> >>
> >>> You see, the space on a HD, as conventionally set up,
> >>> consists entirely of the following: the boot track and one or
> >>> more partitions. (This excludes the rare cases where there
> >>> is unallocated unpartitioned space on the drive, and arcana
> >>> such as the HPA and manufacturer's reserved space).
> >>>
> >>> So, if you encrypt all partitions on such a drive (as
> >>> Truecrypt v5 now allows you to do, even if it is the
> >>> boot/system drive) you have encrypted the **whole drive** -
> >>> with the exception, of course, of the small unencrypted
> >>> bootstub info on track 0 - just as with ALL other whole-disk
> >>> HD OTFE encryption programs.
> >>
> >> If you're not using the pre-boot stuff, then TrueCrypt can
> >> encrypt the entire volume including the MBR with its partition
> >> table.
> >
> > It "can", but that's a destructive process and there's
> > absolutely no way to bootstrap any operating system that you
> > might install after the fact.
> >
> > You guys aren't thinking this through.
>
>
> Maybe you're just stupid. Why do you narrow your views to one
> drive? You can have two or more. One contains the operating
> system, does the pre-boot stuff and has an identifyable partition
> table. The second drive is meant to store data, and is fully
> encrypted, including the partition table.

Maybe you're just a lying sack, desperately trying to change the
rules to try and win a point.

Can you install an OS to ANY device that's been encrypted by
Truecrypt? No.

Case closed. Have a nice day.

Next!