Free SoftWare from GroarWare

Groar

1. What's new (2003/08/11)

1.1 (2003/08/11) New test versions

groar-0.1.18.pre7 (see NEWS files) and titi-0.1.8.pre8 (see NEWS files)

The most important news are :

• groar and titi now do need OpenSSL 0.9.6 or newer.
• K&R support has been removed.

1.2 (2001/08/16) Temporary solution to configure not finding system libssl library

Use "./configure --with-openssl=/usr" to configure groar

This permits to configure groar under FreeBSD 4.4, RedHat 7.1, Mandrake 8.0 and certainly others...

1.3 updates

• 00/12/06 groar 0.1.18.pre2 has been reported compiling et working under AIX 4.2.1.0 with cc 3.1.4.0 :-)
• 00/11/26 groar has been ported to SunOS 4.1.4 with OpenSSL 0.9.4 and non-ANSI cc: groar-0.1.18.pre2 .
  • changed md4 files from OpenBSD by those from OpenSSL 0.9.6
    todo: support using md4 functions from OpenSSL if available.
• 00/11/20 groar 0.1.18.pre1 has been reported compiling et working under Solaris 2.8 with WorkShop Compilers 5.0 :-)
• 00/11/19 titi has been partially ported to SunOS 4.1.4 with OpenSSL 0.9.4 and non-ANSI cc: titi-0.1.8.pre3 .
  • crypt and sha1 work , lanman doesn't
  • ntlm doesn't compile because this cc doesn't know about long long
    todo: change md4 files by those from OpenSSL 0.9.6
  • titi-0.1.7 compiles and works fine yet with gcc 2.7.2.1
  • to port groar-0.1.18.pre1 to SunOS 4.1.4 with non-ANSI cc I have to change md4 files by those from OpenSSL 0.9.6
• 00/11/19 titi has been ported to HP-UX B.11.00 U 9000/800 with OpenSSL 0.9.6 and non-ANSI cc: titi-0.1.8.pre2
• 00/11/18 groar has been ported to HP-UX B.11.00 U 9000/800 with OpenSSL 0.9.6 and non-ANSI cc: groar-0.1.18.pre1
• 00/11/17 titi has been ported to HP-UX B.11.00 U 9000/800 with OpenSSL 0.9.6 and gcc 2.95.2: titi-0.1.8.pre1 .
  • groar-0.1.17 compiles and works fine yet.
• 00/11/06 The pre versions of groar and titi have been upgraded to stable versions: groar-0.1.17 and titi-0.1.7
  • updates of files from OpenBSD and OpenLDAP.
  • groar and titi compile with OpenSSL 0.9.6 .

1.4 grunt !

Pages and archives have been deleted from http://groar.sourceforge.net/ and http://sourceforge.net/projects/groar/

1.5 Please help...

Please, send me an e-mail to say on which platform you tried to compile groar and/or titi and what are the results of the following commands:

• uname -a
• ldd groar
• groar -t
• groar -b

If ./configure or make fail then send me the trace of faulty command.

1.6 What I'm working on...

I'm working on several authentication protocols so it could help me a lot if you could send me:

• tcpdump of failed and successfull authentification
• the passwords used to authenticate

The protocols are:

• ntlmv2: my priority
• ntlm in imap, http, ldap, nntp and pop3

Yes, I want to show to everybody that Microsoft's obfuscation isn't security and that poor passwords are always a security risk.

I do need to receive a lot of networks dumps (preferably in tcpdump format). Thanks to everyone who is going to spend just five little minutes to help me.

1.7 What's going on...

The real news: I'm always working on the heart of groar to support, in a nice way, salted passwords (I hate pointers... which proves that I'm a bad programmer; well it's not very new...).

2. Home Pages

Hello, welcome at http://www.groar.org/

I'm just moving in... so the look of that page.

A mailing-list is available:

• visit lists.sourceforge.net/mailman/listinfo/groar-dru to subscribe
• visit www.geocrawler.com/lists/3/SourceForge/1058/0/ to browse the archive.

3. Project's goals

That project began with an administrator that told me that his passwords from his web server were safe because they were hashed with sha1: a few hours latter, I wrote my first password cracker in a quater of hour and cracked more than 50% .

Another lesson here is that a network application isn't secure just because every session are crypted...</personnal message>

Because passwords are often the first and the last security in a lot of systems and applications, the goal of the groar project is to strengthen security by educating people.

Because an image can be better than an hundred words, the first step is to implement a password cracker to show people how easy it can be to crack passwords and to write crackers. That password cracker will never be as fast as John the Ripper and you will need the latter to really use the former. It will be designed to easily add algorithmes.

The second step will be to document as much pasword crypting algorithms as possible and to denounce thoses that are undocumented and/or weak.

4. Packages

Two packages are available for download:

• groar is a password cracker

  Actually groar supports:

  • SHA1 (Netscape LDAP databases and some apache servers),
  • LM & NTLM (without challenge/response),
  • CLEARtext passwords.

  Available files here are:

  • groar.1: a text version of the manual page,
  • ChangeLog: the changes between releases,
  • NEWS: the news between releases,
  • groar-0.1.18.pre7.tar.gz: the latest version.

  Official versions (please use the newer test versions):

  • (old) groar-0.1.17.tar.gz 2000-11-04
  • (older) groar-0.1.16.tar.gz 2000-02-25
  • (older) groar-0.1.15.tar.gz 2000-01-29
  • (older) groar-0.1.14.tar.gz 2000-01-09
  • (older) groar-0.1.13.tar.gz 2000-01-07

  Test versions:

  • groar-0.1.18.pre7.tar.gz 2003-05-30
  • groar-0.1.18.pre6.tar.gz 2003-05-30
  • groar-0.1.18.pre5.tar.gz 2003-05-19
  • groar-0.1.18.pre4.tar.gz 2003-05-15
  • groar-0.1.18.pre3.tar.gz 2003-05-09

  • (old) groar-0.1.18.pre2.tar.gz 2000-11-26
  • (old) groar-0.1.18.pre1.tar.gz 2000-11-18

  • (older) groar-0.1.17.pre3.tar.gz 2000-03-23
  • (older) groar-0.1.17.pre2.tar.gz 2000-03-11

• titi is a set of password "crypters"

  Actually titi supports:

  • DES,
  • MD5,
  • BlowFish (BF),
  • SHA1,
  • LanMan (LM) & NTLM (with and without challenge/response).

  Available files here are:

  • titi.1: a text version of the manual page,
  • ChangeLog: the changes between releases,
  • NEWS: the news between releases,
  • titi-0.1.8.pre8.tar.gz: the latest version.

  Official versions (please use the newer test versions):

  • (old) titi-0.1.7.tar.gz 2000-11-04
  • (old) titi-0.1.6.tar.gz 2000-01-28
  • (old) titi-0.1.5.tar.gz 1999-12-15

  Test versions:

  • titi-0.1.8.pre8.tar.gz 2003-05-30
  • titi-0.1.8.pre7.tar.gz 2003-05-30
  • titi-0.1.8.pre6.tar.gz 2003-05-19
  • titi-0.1.8.pre5.tar.gz 2003-05-15
  • titi-0.1.8.pre4.tar.gz 2003-05-09

  • (old) titi-0.1.8.pre3.tar.gz 2000-11-19
  • (old) titi-0.1.8.pre2.tar.gz 2000-11-19
  • (old) titi-0.1.8.pre1.tar.gz 2000-11-17

  • (older) titi-0.1.7.pre7.tar.gz 2000-03-23
  • (older) titi-0.1.7.pre6.tar.gz 2000-03-13

Any comment is welcome at the following e-mail address.

5. Development

Developed principally on:

• Linux: Slackware 4 (libc5) and 7 (glibc2.1.2).
  "slack" is certainly the best Linux distribution because the more stable.
• OpenBSD 2.5 and 2.6

Regularly tested on:

• Linux: redhat 6.0 and debian (slink)
• FreeBSD 3.2
• Solaris 2.6 (sparc - gcc 2.7.2.3) and 2.7 (intel - gcc 2.8.1)

You must have installed OpenSSL before to compile groar and titi. Development and tests are principally done with OpenSSL-0.9.6. Previous tests done with 0.9.1c , 0.9.2b , 0.9.4 , 0.9.5beta1 and SSLeay 0.8 were great.

Under OpenBSD, you can use the system ssl library: ./configure --with-openbsd.

Under Solaris, my tests are done with openssl-SNAP-20000113 .

Tests have been done under SunOS, AIX, DG/UX and HP/UX. Please confirm me what is working and what isn't.

groar and titi run only under Unix and I don't think that I'll develop a ZindoZ version.

Successfull compilations and executions (updated 2000/11/26):

• At home:

• At work (thanks to Hervé Schauer and all others):

• Elsewhere, sometimes by someone else (thanks to each of you):

6. TODOs

6.1 TODO

1. Change the license from the default GPL installed by automake by a BSD license
   Sorry but I'm doing an epidermic reaction about the "GNU/Linux" term. Linux is under GPL but it isn't a project officially supported by gnu: there isn't any link from the gnu site to the Linux one. I thank Richard Stallman for all his work about Free Softwares but I think that he is wrong about that.</personnal message>
2. Change internal structures to:
   • Support algorithms with salt (DES, MD5, BlowFish and LanMan & NTLM with challenge / response)
   • Support double hashes: that will speed up LanMan cracking
   • Minimize memory used during cracking
3. Implement "make test" to speed up development: I need help to know how to say to automake that I use shell scripts in "make test" (or it tries to generate it from cc or it's impossible to use "make dist").
4. Improve portability: I'm looking for volunteers who have access to systems I don't have access to, or people who can give me access to such systems.
5. Improve my personnal skills in programming: C, autoconf & automake, man pages, etc.
6. Implement a system to distribute passwords generation.

6.2 DONE (last done first)

1. Implement "groar -t" to autotest crypt functions and "groar -b" to do benchmarks (only because people generally love to compare CPU performances).
2. Use an avl tree to:
   • Minimize memory used during startup by the qsort function
   • Optimize the search of entries with a crypted password (my dicotomic search is certainly FUBAR)
3. Use installed openssl libraries instead of stolling files: the asm version of sha1 is 3 times faster than the C one.
   I know that openssl is very big and I use only a very small part of it: its compilation lasted 26 hours on my 386sx25 with 4 MB of RAM and gcc 2.7.2 under Slackware 3.1

7. Thanks

I want to thank every one who:

• downloaded groar and/or titi and sent me an email about that
  • Solar Designer: a very great guy who makes very good jobs such as John the Ripper and Linux kernel patch
  • and others... (what about having your name here ?)
• give me access to systems to test groar and titi:
  • Hervé Schauer: my actual employer.
  • and others... (what about having your name here ?)

Once again: any comment is welcome at the following e-mail adress.

Have phun,

Groar

This document in written in sgml (LinuxDoc DTD) and translated in html with SGMLtools (version 1.0.9) .