ashleypinner / libmcrypt Goto Github PK

I attempted to crypt [decrypt] a group of files from
the command line:
for i in *.nc
done
mcrypt [-d] --key KEY filename $i
done
This gave me a complaint about not accepting input from
stdin [stdout], even though I was giving mcrypt a file
name and it worked outside a loop.
Eventually I managed to get encryption to work if I
added "-F" to the command line.
I could not get decryption to work using -F, until I
put the -F option as the last option before the file name.
What I'm seeing are two unexpected behaviors:
(1) That using mcrypt in a loop seems to have a
different action than using mcrypt on the command line
by itself. I see this when I use the construct above,
when I use a construct such as "ls | while read; do
mcrypt -d $REPLY; done" as well. If I use -F then I can
force it to work.
(2) That the -F construct must be the final option in
the above situation in order to get mcrypt to work.
Please let me know if I can be of any further assistance.
Mcrypt v.2.6.4 (i686-pc-linux-gnu)
Linked against libmcrypt v.2.5.7

I am using an old SPARCstation 10 (Solaris 2.5.1) as a 
web server and am trying to compile the latest stable 
release of libmcrypt with gcc 3.0.4 and Sun's own linker.
Previous releases (libmcrypt 2.5.3) worked fine, but this 
one (2.5.7) crashes out in the ciphertest linking stage:
gcc -g -O2 -o .libs/ciphertest 
cipher_test.o ../lib/.libs/libmcrypt.so -R/usr/local/lib
makes ld spit several pages of unreferenced symbols 
from the libmcrypt library. Now I returned to the ../lib 
directory, issued "make clean" and rebuilt the library 
using the same algorithm and mode object files. This 
time, I got a much smaller library, but the ciphertest 
compiled. However, it fails everything when executed.
Since I used the same compiler "last time", and can't 
imagine any system changes has occurred since then, 
either it is bit rot or something in the build process has 
been changed. I have tried to rebuild the library from 
scratch, both with fresh sources and already processed.
As I understand only one major security issue has been 
addressed since August 2002, maybe I can stick to the 
older version of the library for now? If there is some 
useful output from configure or make one needs to 
determine if an error occurs, I can be reached on e-mail 
or something.
Anders Carlsson, [email protected] 
(I don't spamblock, as I get enough of spam anyway)

decrypt fails when the size of a decrypted file nears a
1k byte boundary. Extra 
bytes appear to be written, and a SHA1 check failure
ensues.
The following script illustrates the problem.
identify system
uname -a
gcc --version
mcrypt --version
MCRYPT_KEY=X
export MCRYPT_KEY
while [ 0 -eq 0 ]; # use ctrl/c to kill
do
for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17;
do j=1
# build a file with i characters
while [ $j -le $i ];
do echo -n "X" >>x$i
let j++;
done
# encrypt it
if !(mcrypt -q -a arcfour --mode stream x$i)
then read -p "Encrypt failed for x$i" ANSWER
exit;
fi;
# now test decrypt
rm x$i
if !(mdecrypt -q --nodelete x$i.nc);
then ls -l x$i*
exit
fi
rm x$i.nc
done;
done
On my system, produces:
tonyb@linux:~/tc> ./t.sh
Linux linux 2.4.20-4GB #1 Wed Jun 18 07:45:45 UTC 2003
i686 unknown unknown GNU/Linux
gcc (GCC) 3.3 20030226 (prerelease) (SuSE Linux)
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying
conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Mcrypt v.2.6.4 (i686-pc-linux-gnu)
Linked against libmcrypt v.2.5.5
Copyright (C) 1998-2002 Nikos Mavroyanopoulos
([email protected])
SHA1 check failed
File x5.nc was NOT decrypted successfully.
-rw------- 1 tonyb users 1024 2003-10-19
14:08 x5
-rw------- 1 tonyb users 1084 2003-10-19
14:08 x5.nc
SHA1 check failed
File x15.nc was NOT decrypted successfully.
-rw------- 1 tonyb users 3072 2003-10-19
14:08 x15
-rw------- 1 tonyb users 3132 2003-10-19
14:08 x15.nc
SHA1 check failed
File x10.nc was NOT decrypted successfully.
-rw------- 1 tonyb users 2048 2003-10-19
14:08 x10
-rw------- 1 tonyb users 2113 2003-10-19
14:08 x10.nc
SHA1 check failed
File x14.nc was NOT decrypted successfully.
-rw------- 1 tonyb users 3072 2003-10-19
14:08 x14
-rw------- 1 tonyb users 3135 2003-10-19
14:08 x14.nc
SHA1 check failed
File x9.nc was NOT decrypted successfully.
etc, etc.
Cheers,
TonyB