Re: problems with 2.4.0 kernal and int patch

[Dale Amon <amon@vnl.com>]

On Mon, Mar 19, 2001 at 03:20:23PM +0000, Marc Mutz wrote:
> 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

However I also still have the problem and have not seen an answer
back to my debug query (help begging missive) on the issue.

In my own case it simply is not possible to "make it smaller". I need a
very large secure file system and it is not for a personal computer. There 
are reasons, but if I told you I'd have to shred you :-)

I can't help think that there are other secure system projects blocked on 
this same requirement.

I really want to get this issue sorted, and I've gone into gdb and
I've written the test file that shows the issue must be in either
the kernel or libraries associated with the open() call, not 
specifically in the loop back or crypto.

Also, is Gisle coming back or is there any sign of someone doing
a 2.4.2 int patch? The 2.4.0 still applies, but...

-- 
------------------------------------------------------
Use Linux: A computer        Dale Amon, CEO/MD
is a terrible thing          Village Networking Ltd
to waste.                    Belfast, Northern Ireland
------------------------------------------------------

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