[Deque]

ArchiveCracker



I have worked on the CLI version of my archive cracker lately. Since it supports more features now, I decided to publish it separately. GUI version will be updated later.
This program cracks password protected archive files like ZIP, RAR, ...

Features:

• customizeable multi-threading
  
• word generation for bruteforcing
  
• custom alphabets for wordgeneration, definition by file or interactive
  
• wordlist attack
  
• time measurement
  

Limitations:

• large archives take too long to check for passwords
  
• large wordlists not supported yet
  

Usage:



Example usage:

Simple wordlist attack:
java -jar archivecracker.jar -w wordlist.txt myarchive.zip

Simple bruteforce attack with interactive alphabet definition:
java -jar archivecracker.jar myarchive.zip

Bruteforce attack with alphabet from a file and custom thread options:
java -jar archivecracker.jar -t 6 -a characters.txt myarchive.zip

Bruteforce attack with default alphabet:
java -jar archivecracker.jar -d myarchive.zip

LOC: 1027
Requirements: Java 7 Runtime

Download program: http://uppit.com/c89nm21rxqa3/archivecracker.jar
Download source: http://uppit.com/ib3gg6ha2g01/src.zip
GUI version: http://www.hackcommunity.com/Thread-HC-O...acker-V0-4

All my programs are under Free BSD License

----------------------------------------------------------------------------------

Changelogs:

Spoiler:

Changelog V0.4

• interactive alphabet definition
  
• faster initialization
  
• characters for word generation used in same order as given by user
  

Changelog V0.3.1

• bugfix, thanks to @noize for pointing out the problem
  

Changelog V0.3

• multi-threading
  
• custom alphabets for wordgeneration
  
• time measurement
  
• progress bar
  

TODO-list for upcoming versions:

• support for large wordlists
  
• support for large archives
  
• wordlist scrambling
  

[noize]

"No support for huge wordlists."

But I just tried with the wordlist that came with the GUI which is 22 kibibytes large.

Also, the GUI, when trying with the same wordlist and 4 threads printed a Init... and then didn't do anything else. I've waited for many hours but it was taking too much memory and I had to kill it.

Wouldn't it be nice to allow the user to directly enter the alphabet? Like a check if-exists_file ) else ( use the alphabet.
Intance: alphabet: file.txt
when file.txt exists use file.txt's content.
when it doesn't exist use f, i, l, e, ., t, x as alphabet.

It would be probably better to let the user define whether it's a file or not, in case there is a file matching user's direct alphabet (like a "abc"), but it'd be fine however.

Just my point of view.

[Deque]

Thanks for your feedback, @noize.

I am a bit confused. Are you making suggestions for the GUI or the CLI version?
The support for large files will be added when I have time. That's what I wrote here in the todo-list.
The wordlist that comes with the GUI version is not large, I don't want you to download gigabytes of a wordlist if you only want a program. (Or did I upload something wrong?)

I am not sure what you want to say with "But I just tried with the wordlist that came with the GUI"
Did it work or didn't it work?
If it didn't work, what exactly happened?

Like a check if-exists_file ) else ( use the alphabet.[/size]
Intance: alphabet: file.txt
when file.txt exists use file.txt's content.
when it doesn't exist use f, i, l, e, ., t, x as alphabet.

I already do that. If you don't give a file, it uses a default alphabet.

It would be probably better to let the user define whether it's a file or not, in case there is a file matching user's direct alphabet (like a "abc"), but it'd be fine however.

So you want the user to enter the alphabet within the program or do you want it to use the default alphabet?

[noize]

Thanks for your feedback, @noize.

I am a bit confused. Are you making suggestions for the GUI or the CLI version?
The support for large files will be added when I have time. That's what I wrote here in the todo-list.
The wordlist that comes with the GUI version is not large, I don't want you to download gigabytes of a wordlist if you only want a program. (Or did I upload something wrong?)

Of course, I'm not complaining that you gave a small wordlist; that's surely fair. I'm just saying that with that wordlist (that is not a big wordlist), GUI locks and CLI says that it's too large.

So you want the user to enter the alphabet within the program or do you want it to use the default alphabet?

Well, I always like better when I have every choice for the way the program goes. So I would do like -d,--default (if -a is present or if -f is present and valid -d gets overridden) for default alphabet; -a,--alphabet [alphabet] for direct alphabet input; -f [file] (or whatever) for alphabet-file.

[Deque]

Thanks for your feedback, @noize.

I am a bit confused. Are you making suggestions for the GUI or the CLI version?
The support for large files will be added when I have time. That's what I wrote here in the todo-list.
The wordlist that comes with the GUI version is not large, I don't want you to download gigabytes of a wordlist if you only want a program. (Or did I upload something wrong?)

Of course, I'm not complaining that you gave a small wordlist; that's surely fair. I'm just saying that with that wordlist (that is not a big wordlist), GUI locks and CLI says that it's too large.

So you want the user to enter the alphabet within the program or do you want it to use the default alphabet?

Well, I always like better when I have every choice for the way the program goes. So I would do like -d,--default (if -a is present or if -f is present and valid -d gets overridden) for default alphabet; -a,--alphabet [alphabet] for direct alphabet input; -f [file] (or whatever) for alphabet-file.

I reread the first post a few times and I think I get you now. Thanks for your feedback. The bugs are odd. I don't get them. I will test my programs again. Do you get any error message when starting the GUI version on console?
What is your OS?

[noize]

Thanks for your feedback, @noize.

I am a bit confused. Are you making suggestions for the GUI or the CLI version?
The support for large files will be added when I have time. That's what I wrote here in the todo-list.
The wordlist that comes with the GUI version is not large, I don't want you to download gigabytes of a wordlist if you only want a program. (Or did I upload something wrong?)

Of course, I'm not complaining that you gave a small wordlist; that's surely fair. I'm just saying that with that wordlist (that is not a big wordlist), GUI locks and CLI says that it's too large.

So you want the user to enter the alphabet within the program or do you want it to use the default alphabet?

Well, I always like better when I have every choice for the way the program goes. So I would do like -d,--default (if -a is present or if -f is present and valid -d gets overridden) for default alphabet; -a,--alphabet [alphabet] for direct alphabet input; -f [file] (or whatever) for alphabet-file.

I reread the first post a few times and I think I get you now. Thanks for your feedback. The bugs are odd. I don't get them. I will test my programs again. Do you get any error message when starting the GUI version on console?
What is your OS?

I just tried to start it from console and got no errors.
Windows 7 64-bit.

[Deque]

Thanks. I just got an idea what went wrong with the CLI version. Will tell you more when I fixed it.
Don't have any idea with the GUI, though.

[noize]

Thanks. I just got an idea what went wrong with the CLI version. Will tell you more when I fixed it.
Don't have any idea with the GUI, though.

Well, with the GUI it might be a local issue, as long as it appears to be still in 0.3, which I had already used. Will try again after a reboot, later.

[Deque]

I probably fixed the CLI version. Could you try if it works for you now?
http://uppit.com/pgpytrd1tbq9/archivecracker.jar

[noize]

Well, it got to the progress bar, so far, but it stays on 0 words tried.