do anyone of you know if it is possible to have the partition table on a file and insert that to the kernel instead of using actual MBR from harddrive?
what would the point be?
booting from usb keyring and leaving MBR with only a windows partition to boot, as a part of disk encryption
obscurity is never a good security measure
I don't see the connection.
without usb keyring it is impossible to boot and readout partition table
oh ,you mean "hidden partitions" on teh disk? have fun patching the kernel.
if you want encryption, create a large file on a normal partition with a normal filesystem, adn then mount the file using aesloop and format it
i understood malex that was his idea
note that software can in theory examine the "empty" space and notice there's a filesystem on it.
that's the idea, luks device mapper or something
not empty urandom filled or encrypted
no zero parity bits
wheter there is a partition or not doesn't matter. it's how you use it that does. if it's encrypted, it's encrypted. might as well have a sane partition table
if it's empty or filled with random data it's NOT A FILESYSTEM.
even an encrypted filesystem ahs a partition and a signature. taht's how the kernel can know there's a filesystem there. if you're talking about an arbitrary non-partition disk block in empty space, have fun writing the driver.
i am not
the security nuts people I know, simply have a normal system install, and then their home directory is aesloop mounted file on the normal drive. They keep all things that should be secure in the aesloop home.
malex suggested only having the partition table known on the bootable usb keyring, not on the harddrive itself, kid of make it impossible to prove exist
doesn't sound useful to me at all
that's a completely unnecessary step.
If my friend things aesloop is a good solution for it, I have no reason to doubt it.
s/things/thinks/
ok, thanks for giving your point =)