From owner-freebsd-security Tue Jul 2 6:41:41 2002 Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3285837B400 for ; Tue, 2 Jul 2002 06:41:39 -0700 (PDT) Received: from wrath.cs.utah.edu (wrath.cs.utah.edu [155.99.198.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88B0F43E0A for ; Tue, 2 Jul 2002 06:41:38 -0700 (PDT) (envelope-from danderse@cs.utah.edu) Received: from famine.cs.utah.edu (famine.cs.utah.edu [155.99.198.114]) by wrath.cs.utah.edu (8.11.6/8.11.6) with ESMTP id g62DfT908553; Tue, 2 Jul 2002 07:41:30 -0600 (MDT) Received: by famine.cs.utah.edu (Postfix, from userid 2146) id 5B94623A7A; Tue, 2 Jul 2002 07:41:27 -0600 (MDT) Date: Tue, 2 Jul 2002 07:41:27 -0600 From: "David G . Andersen" To: Eric Anderson Cc: freebsd-security@FreeBSD.ORG Subject: Re: password crackers? Message-ID: <20020702074127.B21304@cs.utah.edu> References: <3D21AC48.3E2C1BC1@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3D21AC48.3E2C1BC1@centtech.com>; from anderson@centtech.com on Tue, Jul 02, 2002 at 08:36:08AM -0500 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Eric Anderson just mooed: > What does everyone recommend for a general password file cracker? I have been > using an old version of crack, but there must be better ones around. I need to > crack solaris, freebsd, and linux password hashes. Any recommendations? Single-host: John the Ripper http://www.openwall.com/john/ Multi-host: Probably still Crack. John will be faster on a single host than Crack on two hosts, most likely, but if you've got a host of hosts to throw at it, crack is easier to manage. -Dave -- work: dga@lcs.mit.edu me: dga@pobox.com MIT Laboratory for Computer Science http://www.angio.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message