[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-crypto
Subject:    Re: problems with 2.4.0 kernal and int patch
From:       Marc Mutz <Marc.Mutz () uni-bielefeld ! de>
Date:       2001-03-19 15:20:23
[Download RAW message or body]

Morbid Angel wrote:
> 
> Hi !
> 
> i have problems with Kernel 2.4.0 and INT patch
> 
> i have done all like it is written in the howto
> and it all was succesfull
> 
> but if i want mount my crypted file i get ever "File to large"
> my crypto file is 12GB big, but i know the 2.4.0 kernel can "work" with
> files >2GB
> 
> why do i get this error message ?
> what can i do ?
> 
<snip>

Shrink the crypted file to a reasonable size. I honestly cannot imagine
needing that much encrypted space at all. When you go through what you
want to put into it one by one, you'll most probably see that there's no
point in putting so much stuff into it. Personally, I used up to 2G,
mostly because I was putting my complete email traffic there (with all
the mailing lists I am subscribed to). But that's nonsense. Everybody
can see your email when you send it or when you use PGP, you don't need
to encrypt it a second time.

It suffices to put one's .netscape, .pgp, .gnupg etc there. My encrypted
space is now much smaller.

Also, if you really care about your data and want it protected, you
won't put so much stuff in it, not even mentioning stuff that everybody
knows, because of known-plaintext attacks. If you use blowfish, I would
not dare to encrypt that much data under a single key, because of the
birthday attack, whose 'magic number', ie. the size of data where equal
ciphertext blocks will occur with probability 1/2, is about 2^32 blocks,
ie. 32GByte.

Marc

-- 
Marc Mutz <Marc@Mutz.com>     http://EncryptionHOWTO.sourceforge.net/
University of Bielefeld, Dep. of Mathematics / Dep. of Physics

PGP-keyID's:   0xd46ce9ab (RSA), 0x7ae55b9e (DSS/DH)



Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/

[prev in list] [next in list] [prev in thread] [next in thread]