[1013] in linux-security and linux-alert archive
Re: [linux-security] Problems running crack on linux.
daemon@ATHENA.MIT.EDU (Elliot Lee)
Fri Aug 16 15:19:21 1996
Date: Fri, 16 Aug 1996 14:22:19 -0400 (EDT)
From: Elliot Lee <sopwith@redhat.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:
[Mod: Quoting trimmed. --Jeff.]
> --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--
Basically, Crack is using its own internal fcrypt() instead of the one in
libc (which is also faster :) You have to edit the Makefile to tell it
not to link in its own fcrypt() stuff...
--==== Elliot Lee = <sopwith@redhat.com> == Red Hat Software ====--
"Usenet is like a herd of performing elephants with diarrhea; massive,
difficult to redirect, awe-inspiring, entertaining, and a source of
mind-boggling amounts of excrement when you least expect it."
