If you are having first-hand experience running an encrypted file system
on FreeBSD, could you please get in touch with me?
Thanks,
--Lucky
On Thursday, February 14, 2002, at 10:03 PM, Lucky Green wrote:
> If you are having first-hand experience running an encrypted file system
> on FreeBSD, could you please get in touch with me?
>
> Thanks,
> --Lucky
I read this about Mac OS X, which is based heavily on FreeBSD:
(in today's topic
On 2/16/2002 7:27 PM, "Tim May" <[EMAIL PROTECTED]> wrote:
> On Thursday, February 14, 2002, at 10:03 PM, Lucky Green wrote:
> I read this about Mac OS X, which is based heavily on FreeBSD:
>
> (in today's topics at http://www.macintouch.com/index.shtml)
>
>
> "A number of readers offered a s
> Is there any way to encrypt the swap partition? Passwords and other
> sensitive data can sometimes linger there.
OpenBSD can encrypt the swap. It can't encrypt any other part of the
disk, though. D'ohh! "OpenBSD: Crypto everywhere... except for your
files."
On 17 Feb 2002, Dr. Evil wrote:
> > Is there any way to encrypt the swap partition? Passwords and other
> > sensitive data can sometimes linger there.
>
> OpenBSD can encrypt the swap. It can't encrypt any other part of the
> disk, though. D'ohh! "OpenBSD: Crypto everywhere... except for you
"Lucky Green" <[EMAIL PROTECTED]> writes:
> If you are having first-hand experience running an encrypted file system
> on FreeBSD, could you please get in touch with me?
# cd /usr/ports
# make search key=crypto
yadda yadda
# cd /usr/ports/security/cfs
# make all install clean
(same commands w
On 19 Feb 2002, Dr. Evil wrote:
> > (same commands work on OpenBSD which has better crypto support)
>
> Yes, everywhere except on the disk. The kernel ships with a great
> rock-solid encrypted swap. It ships with a broken tcfs and a broken
> encrypted vnd (loopback) fs. So you get crypto every
On Tue, 19 Feb 2002, cyphrpnk wrote:
> unfortunately an examination of the source reveals no hmac being maintained on
> the file used as a vnode mounted filesystem, gives this same vunerability.
> (its easily resolved by taking an external hmac(via samhain,demairc,tripwire,
> sha1 etc,) during un
zem wrote:
>>In addition...a sudden power down on this type of
filesystem(encrypted, VND
>>mountea)d will damage the resulting structure so that fsck WILL NOT work
>>on it.
>>
>
> I've had power failures while using mounted encrypted loopbacks which
have
> recovered fine with fsck. Hav
