> > hello!
> >
> > Why don't you just use cryptofs and smartcard together?
> > I'm sure that providing an initrd image would be sufficient.
> > That image would consist of the required apllications and libs with the
> > sufficient kernel. Simple, eh? rootfs and required partitions could be
>
> It would be a solution. But it is not exactly what we want. We would prefer
> both: bootaprotection and crypto filesystems.
For using linux it's certainly possible using a simple initrd-filesystem with
smarcard support in it.
If you want to boot windows on this machine, it should be possible too: look
at the kexec-site
http://www.xmission.com/~ebiederm/files/kexec/
and some links at
http://kt.zork.net/kernel-traffic/topics/Kexec.html
In short: kexec allows linux to return to real-mode, reset the hardware, and
boot other OS.
So there would be a linux-partition of, say, at most 8MB, with an initrd
image, a minimal kernel with kexec, and the rest of the harddisk could be
used at will.
Of course - that doesn't help with encrypting the filesystems of the other OS.
Regards
Phil
_______________________________________________
Muscle mailing list
[EMAIL PROTECTED]
http://lists.musclecard.com/mailman/listinfo/muscle
