Cyberiade.it Anonymous Remailer <anonymous@remailer.cyberiade.it> writes:
> 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.

Au contraire. Sebastian's thought this through in its
entirety, it's just that you're all taking a long time
to catch up.

Your "that's a destructive process" is either meaningless
or wrong. Your "there's absolutely no way to bootstrap any
operating system" is completely false. Boot of another
medium. Trivial.

_Any_ container for an encrypted file system will break
the contained file system if tampered with. That applies
exactly equally to an entire disk as it does to a single
file sitting within an arbitrary other file system.

Please try to keep up.

Phil
--
Dear aunt, let's set so double the killer delete select all.
-- Microsoft voice recognition live demonstration