john-users - Re: roadmap

Openwall Project		/home Owl JtR Pro crypt pam_passwdqc tcb phpass scanlogd popa3d msulogin / Linux BIND / advisories presentations / services donations / wordlists passwords / NEWS community lists Wiki CVSweb mirrors signatures
bringing security into open environments

Password Recovery Resources on the Net

[<prev] [next>] [<thread-prev] [thread-next>] [month] [year] [list]

Date: Mon, 30 Jan 2006 16:04:35 +0000 (UTC)
From:  Phantom <phantom_otw@...oo.com>
To: john-users@...ts.openwall.com
Subject:  Re: roadmap

Ok...atleast "anytime soon" is not equal to "never" ;)

P4 optimizations: Will give my "old" P4 Northwood something to do other than 
beeing a server/mediacenter ;)

SMP support would be cool...just wonder how it would work under windows.
Would be cool if you in the ini/conf file could specify how many CPUS to use and
 which (affninity), AND set the priority they should use.
Scenario: use cpu0 100% with "normal" prioritym and use cpu1 with "low" priority.
So you could still use the PC while JTR is working.

Clean up current code sounds like a good idea, allthough I have no idea what and
 how to clean it, hehe
The other hash type patches that exists will have to do for now.
But flagging them as "optimized"/"unoptimized" would be cool :)

Hmmm, how about:
-single> "username-manipulation"-attack?
incrememental="bruteforce"-attack?
Wordlist="dictionary"-attack ?

My input for now....

Regards
PhanTom