- Strip control characters (ascii colours) from key when found (aircrack-ng issue)
- Check if pid belongs to moscrack when determining if it is running (otherwise false positives possible)
- moscrack.cgi bug "#3 Empty table of connected nodes" fixed
- Fixed bug "#2 nodes.dat.tuning file generation ignores port configurations"
I've begun work on a new web based API for Moscrack. Currently there is a daemon called mosapid that will handle all requests over HTTP. There is an experimental mosctop.mosapid that uses the new interface rather than accessing status.dat directly.
I intend to make certain things work via the API in the future like:
- get status info (working)
- set config options
- stop/start/restart Moscrack
- pass values to Moscrack like wordlist, essid, etc...... read more
I got my Samsung Galaxy S2 SGH-I727R to work as an SSH node with Moscrack.
I am running Cyanogenmod 10 (Android 4.1.2) + a Debian Linux chroot environment, with openssh + aircrack-ng compiled directly on the phone.
It achieved 383 words/sec during tuning. I have an Athlon X2 system that only achieved 458 and my iPhone 3g only managed 43. So I'd say it's not so bad for a phone.
Moscrack Live 0.2b has been released. There is now a persistent USB/raw image in addition to an ISO. They can both be found in the files section.
- Latest mocc daemon and related init scripts
- Friendly instructions after boot
- wpa_supplicant installed for wireless network support
1. I am in the process of fixing bugs that have been reported to me
2. I've recruited someone to help me beta test, hunt for bugs, test for ease of use, documentation, etc....
When done, a new "stable" release will be created and made available! Moscrack will no longer be in beta.
This version includes the plugin framework, 2 plugins and the ability to crack unix password hashes. See release-notes.txt for details.
This version includes a utility called "crypt" which can be used for testing your systems ability to generate hashes of different types. Since dehasher uses your local GLIBC crypt() function, this can be useful in determining it's capabilities.
It looks like the framework for plugins is complete. There may be things I've overlooked and I'll add those as they occur to me.
I moved the code for Pyrit to a plugin, since the original code was kind of a hack to moscrack and didn't quite fit in cleanly.
Plugin abilities (for potential developers) include:
- moscrack --list lists all plugins, description and help option for each
- can execute code or define values on init immediately after global values, config file
and command line options are processed
- ability to pass command line arguments to a plugin via --plugin key=value
- ability to access/define/modify global configuration and command line options
- ability to define a node type like "pluginName/type"
- ability to support either multiple standard node types, select types or custom types cast onto existing types
- ability to provide plugin based status check or use standard checks, or disable checks
- ability to check command output, extract key, extract speed
- ability to enable or disable plugin based on validation techniques
- plugins can be disabled by renaming - only *.def files are loaded
- plugins can be loaded in order by prefixing with numeric values i.e. 015dehasher.def, 020pyrit.def... read more
This version introduces a proper build environment, README and test suite.
Dehasher is really better than Alpha.. it's stable and works nicely.
Since I was looking to add new abilities to Moscrack, like cracking password hashes, I decided to create a plugin framework. I have a working version in SVN. There's a plugin for the "dehasher" utility that I created to demonstrate how it works and add the new feature.
Plugins do not make it really easy to add features to Moscrack, they just give you a standard way of doing it. It still requires understanding how Moscrack works and writing perl code.... read more
Originaly "shahash", now "dehasher". Cracks anything your systems crypt() understands, like SHA, MD5 and Blowfish.
Multithreaded and faster than John the ripper. Small and easy to install. Tested on Linux/Solaris. Don't bother on FreeBSD or Cygwin.
I made a sha bruteforce cracker. I wanted to work on something in C (I'm pretty new to it) and I couldn't find a good one, so I made this.
It works using the standard crypt() unix function. On Ubuntu Linux, crypt is actually UFC Crypt (Ultra Fast Crypt), an accelerated implementation made for this purpose.
You can pass it anything that matches this format "$id$salt$encrypted". That is the format used by SHA in modern passwd shadow files at least on Linux. It auto detects the number of cores on your system and *might* compile on BSD systems and windows... you need to pass arguments at compile time and such and I haven't tested any of that.... read more
I found a few bugs in 2.05b shortly after release. I have decided to release a bug fix version to correct them shortly. However, you may be interested in what they are.
- Sample moscrack.conf has a number of comments that are missing a preceding '#'. This results in a failure to load the configuration file. This is pretty easy to fix yourself, just look for missing # signs.
- moscrack --help doesn't display the -C|--config command line option which allows the use of an alternate config file.
- moscrack doesn't handle empty nodes.dat lines very well, it should just skip them silently not give errors... read more
You should upgrade, there are tons of new features.
Make note: The format of nodes.dat and moscrack.conf have changed. Use the samples provided with Moscrack.
I've added a command line option to perform a connectivity test of all nodes. It's useful if you want all your nodes to be up before starting and aren't sure if they are. I thought this would be useful as I've had a desire for it sometimes, especially when working with Amazon EC2 nodes.
It connects to each node using it's normal connectivity method (the same way Moscrack does status checks). All nodes are connected in parallel, so it's pretty fast even with a large cluster.
Moscrack works with Amazon EC2. I knew it would, but had to test it to verify. I was disappointed with the results, but I've decided to share them anyways.
I can't afford to pay for high-performance virtual nodes, so I used the free ones (micro images). They are slow as hell. They start fast, get slower over time. They are no good for Moscrack, so don't bother trying.
I managed to connect to 20 nodes at once, no problems. The micro nodes report themselves as being capable of 700 w/s, but they get slower as they use CPU bursting. They are closer to 300 w/s. ... read more
Moscrack 2.04b uses Net::SSH::Perl, a pure perl implementation of the SSH protocol. It's hard to install and has too many dependencies.
I just noticed it was eating up CPU like crazy on my Moscrack server and can't figure out why. Sorry if this was affecting anyone. My server is a quad core, so until I loaded it with 15 SSH nodes at once, the problem wasn't apparent.
I've replaced it with Net::SSH2 which seems nice because it uses libssh2 directly - it's not a wrapper. I may also replace the external scp command with Net::SSH2 calls later on, but for now it remains the same.... read more
Do you have the need to process your whole word list at once, without repeatedly loading small chunks onto your nodes? oneShot does just that. The feature is not for everyone. This will result in a very large chunk size for large word lists. Large chunks amplify some types of errors/failures/etc... Moscrack will also be unable to provide you with any feedback/results until nodes finish, which will take longer.... read more
Moscrack now as a new feature that automatically determines an optimal chunk size based on the time in seconds that you'd like your nodes to process chunks for.
E.g. moscrack.conf file
autoChunkSize = 1
autoChunkSizeTime = 300
This would enable auto chunk sizing, and set the chunk size to whatever your slowest node can process in 300 seconds. Because of the variable chunk size feature in Moscrack, a node twice as fast, will still get twice as much data and therefore still take approximately 300 seconds to process.... read more
Moscrack has a new option in it's configuration file:
useAllNodes - Force using all nodes 1 or 0. Automaticaly reduces your chunkSize if it would otherwise prohibit all nodes from being used. This is useful for when the word list size is small relative to the cluster. This will not make things faster if one or a few nodes can process the whole word list in a short period of time, it will actually make things slower due to the overhead. Enable when splitting a small word list across all nodes would be faster.... read more
I've started on an early Moscrack CGI. It's quite nice to use and so far does everything that mosctop does, but in your browser with colours and such.
I'm going to put up a screen shot in a moment, check it out.
"moscrack.cgi" is available in SVN. You need to edit one line in it. "my $statusFile =" needs to be set to your moscrack working directory/status file.
I have none!
If you've been using Moscrack, please send me anything you can. Even if it's simple stuff. I'm looking to friends to try and find someone willing to help go though everything, but I'm not sure how far I'll get.
Examples of things you can send me your comments on:
-Ease of use
-Feature requests / ideas
These are some of the features to look forward to in the next release of Moscrack. They are currently available in SVN.
-Use tcp instead of ping for status checks, allows use of a single port
-Captures int and term signals and handles them gracefully
-Use actual node speed intead of multipliers (except for somethings internally)
-Added expire value to nodes.dat for moscc/moscd so auto-configurured nodes will expire if they aren't updating
-Allow you to define ports per node in nodes.dat for rsh and ssh
-Allow you to set default ports for rsh and ssh in moscrack.conf
-Node prioritization based on actual speed, not multiplier
-Estimates speed of cluster (for your pleasure)
-Hung node detection kills nodes that are taking too long based on their estimated time of completion
-Improved various aspects of moscd and moscc
-mosctop auto screen size detection
-mosctop more space for node name
The Live CD and documentation are available in the download area.
Moscrack has an experimental LiveCD. The only things on it of importance are
aircrack-ng and moscc (Moscrack Client).
2. How it works
- Enable moscd (Moscrack Daemon) on your Moscrack server
- Boot your node(s) using the live CD
That's it. The moscc daemon will find your moscrack server by sending a
a broadcast message on to your LAN. Both client(s) and server will auto
configure themselves. If all works properly, you can run moscrack
and it will use the new nodes without further configuration.
A new experimental feature. It consists of a daemon for nodes and a daemon for the moscrack server. The node will broadcast onto the network that it wants to be a node of a certain type. The server will listen for these broadcasts and configure itself to use the node as requested. The client will receive a user name and ssh public key from the server and configure itself with them to accept incoming connections from Moscrack. ... read more