[1018] in linux-security and linux-alert archive
Re: [linux-security] Problems running crack on linux.
daemon@ATHENA.MIT.EDU (Jeff Barrow)
Mon Aug 19 19:21:01 1996
Date: Fri, 16 Aug 1996 22:49:07 -0500 (CDT)
From: Jeff Barrow <jeffb@hsnp.com>
To: "Robert R. Collier" <rob@lspace.org>
cc: linux-security@tarsier.cv.nrao.edu
In-Reply-To: <199608161521.QAA28744@tanstafl.demon.co.uk>
On Fri, 16 Aug 1996, Robert R. Collier wrote:
> --8<--8<--
> pwc: Aug 16 16:11:12 Crack v4.1f: The Password Cracker, (c) Alec D.E. Muffett, 1992
> pwc: Aug 16 16:11:12 Version of crypt() being used internally is not compatible with standard.
> pwc: Aug 16 16:11:12 This could be due to byte ordering problems - see the comments in Sources/conf.h
> pwc: Aug 16 16:11:12 If there is another reason for this, edit the source to remove this assertion.
> pwc: Aug 16 16:11:12 Terminating...
> -->8-->8--
This is a byteorder problem. I got it working by configuring crack to use
the libc version of crypt()... I'm not SURE, but you can try #include
<asm/byteorder.h> in the main include file, it may work. The problem is
that crack uses a _very_ old method of deciding endianness, that may be
slightly incompatible with our libc.
> I tried changing various #defines in Sources/conf.h but to no effect.
Try #define LITTLE_ENDIAN as well....
Good luck!
