Difference from Crack 4.1 to 5.0

Difference from Crack 4.1 to 5.0

Post by wa.. » Wed, 20 Aug 1997 04:00:00



From the Crack 4.1 docs:

In a similar vein, when a Crack run terminates normally, it writes out to
the feedback file all encrypted passwords that it has NOT succeeding in
cracking.  Crack will then ignore all of these passwords next time you run it.

This functionality does not seem to exist in 5.0 and I found no mention
of it being removed or how you might gain this functionality.  Has this
truly been removed?  This was very handy, can it be simulated?

Wayne

--
====================================================================
Wayne E. Beech
University of Kentucky Computing Center
Senior Systems Programmer

 
 
 

Difference from Crack 4.1 to 5.0

Post by Joerg Schumach » Wed, 20 Aug 1997 04:00:00


[...]

Quote:> This was very handy, can it be simulated?

Yes.  Someone posted a workaround proposed by Alec Muffett:

: Yes, unless you "sort" the passwd file and save it:
:
:        sort oldpwfile > old
:
: Then when you next want to check passwords:
:
:        sort newpwfiles > new
:        comm -13 old new > tmp
:        mv new old
:        Crack tmp
:
: - not so hard, eh?

Hope this helps,
Joerg.

 
 
 

Difference from Crack 4.1 to 5.0

Post by wa.. » Thu, 21 Aug 1997 04:00:00



Schumacher) writes:

> [...]
> > This was very handy, can it be simulated?

> Yes.  Someone posted a workaround proposed by Alec Muffett:

> : Yes, unless you "sort" the passwd file and save it:
> :
> :        sort oldpwfile > old
> :
> : Then when you next want to check passwords:
> :
> :        sort newpwfiles > new
> :        comm -13 old new > tmp
> :        mv new old
> :        Crack tmp
> :
> : - not so hard, eh?

> Hope this helps,
> Joerg.

BUT... If you are running a network crack, then you have to deal manually  
with things such as which copies ran to completetion if some where  
interrupted, etc.  Just because they have the same password as before  
doesnt mean the password should not still be examined.

wayne

 
 
 

1. Crack 5.0 runtimes enormous compared to 4.1?

I started a network-distributed crack on approximately 1200 accounts,
distributed across 30 different Alpha systems on Saturday morning. At
2pm Tuesday, it hadn't finished on any of them. 4.1f only took around 10
hours per system to run.

Does 5.0 REALLY take that much longer?

--
======================================================================
Brian O'Neill - Director of Computing, Computer Science (508) 934-3645

"Did I mention that my nose is on fire and that there are 15 badgers
 living in my pants?" Marcus, Babylon 5

2. newbie on freebsd

3. Probleme avec crack 5.0 + RH 5.0

4. Adding SCSI Card to x86 Server

5. Error on Crack 4.1

6. Finding module dependencies.......problem!

7. Crack 4.1 on an Alpha AXP?

8. rapskunk the thread slinker #3

9. RE Crack 4.1 on Next

10. Crack 4.1 - doesnt crypt properly on NeXTs?

11. **Help With Crack 4.1!!!

12. Crack 4.1 on Digital Unix

13. shadow and Crack 4.1