[1043] in linux-security and linux-alert archive
Re: [linux-security] Problems running crack on linux.
daemon@ATHENA.MIT.EDU (root)
Wed Aug 21 12:34:31 1996
Date: Tue, 20 Aug 1996 11:04:12 -0700 (PDT)
From: root <root@dial-sc1-8.iway.aimnet.com>
To: Alan Cox <alan@cymru.net>
cc: "Robert R. Collier" <rob@lspace.org>, linux-security@tarsier.cv.nrao.edu
In-Reply-To: <199608161857.TAA10030@snowcrash.cymru.net>
On Fri, 16 Aug 1996, Alan Cox wrote:
> > 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 correct. Our long passwords are different. We also have a very
> fast crypt() in libc, so use that an for optimal performance static link
> it so crypt isnt running -fPIC
>
> Crack 5.0 is about to appear
>
>
I had the same prob with crack 4.1f, and i had to get a procompiled
version from sunsite... i want to know how to link libc's crypt() into
crack... can someone make a patch for crack 4.1f?
-Rob
