{ "info": { "author": "Will Boyce", "author_email": "me@willboyce.com", "bugtrack_url": null, "classifiers": [ "Development Status :: 5 - Production/Stable", "Environment :: Console", "License :: OSI Approved :: Apache Software License", "Operating System :: MacOS :: MacOS X", "Operating System :: POSIX", "Programming Language :: Python :: 2.7", "Topic :: Security" ], "description": "ec2hashcat\n==========\n\nPassword Cracking in the Cloud\n\n``ec2hashcat`` is a utility to automate the process of password cracking on the AWS Cloud using GPU Instances.\n\n\nInstallation\n------------\n\n::\n\n % pip install ec2hashcat\n\nThats it!\n\n\nConfiguration\n--------------\n\nAll arguments beginning with ``--`` can be specified in ``~/.ec2hashcat.yml`` and ``$PWD/ec2hashcat.yml``\n\n.. code:: yaml\n\n aws-key: AWS_KEY\n aws-secret: AWS_SECRET\n aws-region: AWS_REGION\n\n ec2-key-name: EC2_KEY_NAME\n ec2-key-file: EC2_KEY_FILE\n\n s3-bucket: S3_BUCKET_NAME\n\n\nUsage\n-----\n\nFor more information, check the online help::\n\n % ec2hashcat --help\n % ec2hashcat --help\n\nExample\n~~~~~~~\n\nA working example using the provided sample files::\n\n % ec2hashcat crack -b examples/batch.ec2\n % ec2hashcat list sessions\n % ec2hashcat list files\n % ec2hashcat cat wordlists hashlist.dic\n % ec2hashcat get wordlists hashlist.dic\n % ec2hashcat delete dumps hashlist.dmp\n\nCracking\n~~~~~~~~\n\nHandles the uploading/downloading of files to/from S3/EC2, starting/stopping of instances and running ``cudaHashcat``.\n\nBasic usage is very similar to the ``hashcat`` family of programs::\n\n % ec2hashcat crack -a3 -m0 \n % ec2hashcat crack -a0 -m0 \n % ec2hashcat crack -a0 -m0 -r \n\nAny arguments not directly handled by ``ec2hashcat`` can be passed to ``cudaHashcat`` using the ``--hashcat-args`` argument::\n\n % ec2hashcat crack -a3 -m0 --hashcat-args='--increment' \n\n``ec2hashcat`` will attempt to detect any filenames passed via ``--hashcat-args`` and handle them appropriatly.\n\nWhen using the ``--rules`` argument, ``ec2hashcat`` will store any custom rules in S3 and exposes access to the builtin rules using the ``builtin:`` keyword::\n\n % ec2hashcat crack -a0 -m0 -r builtin: \n\nBy default ``crack`` will write an updated ``hashlist``, ``dump``, and ``wordlist`` to S3, you can use the ``--no-write-hashlists``, ``--no-write-dumps``, and ``--no-write-wordlists`` arguments respectively.\n\nOnce the main ``crack`` task has completed and any files updated, the machine will be shut down. To keep the instance alive, use the ``--no-shutdown`` argument. Additionally, to drop into a shell once the task has completed, used the ``--shell`` argument. Note that dropping into a shell will block the shutdown until the shell is exited.\n\n``crack`` can also operate in a batch mode, combining multiple attacks into a single session. The batchfile is specified using the ``--batchfile`` argument, and follows the same rules as script name in ``runscript``::\n\n % ec2hashcat crack -b+\n batch> crack -a3 -m0 \n batch> crack -a0 -m0 \n\n % cat < \n crack -a0 -m0 \n\n % cat batch.ec2\n #!/usr/bin/env ec2hashcat -b\n crack -a3 -m0 \n crack -a0 -m0 \n % ec2hashcat crack -b ./batch.ec2\n % ./batch.ec2\n\nFor more information on hashcat usage, see `the hashcat wiki`_.\n\n.. _the hashcat wiki: http://hashcat.net/wiki/\n\nRunning Scripts\n~~~~~~~~~~~~~~~\n\nArbitrary scripts can be run against new or running sessions by following similar syntax to ``crack``. Scripts are executed inside a screen named after the local filename.\n\nRun a script on a new instance::\n\n % ec2hashcat runscript