From: Pierre Neidhardt <ambrevar@gmail.com>
To: 32332@debbugs.gnu.org
Subject: [bug#32332] Acknowledgement ([PATCH 1/4] gnu: Add hashcat.)
Date: Tue, 31 Jul 2018 12:22:05 +0200 [thread overview]
Message-ID: <877elbhfhu.fsf@gmail.com> (raw)
In-Reply-To: <handler.32332.B.153303209722315.ack@debbugs.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
I've packaged hashcat, hashcat-utils and hcxtools.
I don't have access to OpenCL-compatible hardware at the moment, so I
can't really test hashcat. Anyone?
Also I'm not so sure about hashcat-utils and hcxtools: the code quality
seems rather low at first glance.
hashcat-utils seems to be necessary, e.g. to convert pcap files to the
hccapx format used by hashcat.
aircrack-ng can used in stead of hcxtools. See
https://hashcat.net/wiki/doku.php?id=cracking_wpawpa2.
While the hashcat community recommends hcxtools, I am under the
impression that aircrack-ng is a much more polished tool suite.
What do you think?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-07-31 10:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 10:14 [bug#32332] [PATCH 1/4] gnu: Add hashcat Pierre Neidhardt
2018-07-31 10:17 ` [bug#32332] [PATCH 2/4] gnu: Add hashcat-utils Pierre Neidhardt
2018-07-31 10:17 ` [bug#32332] [PATCH 3/4] gnu: Add hcxtools Pierre Neidhardt
2018-07-31 10:17 ` [bug#32332] [PATCH 4/4] gnu: Add hcxdumptool Pierre Neidhardt
2018-08-13 15:02 ` Leo Famulari
2018-08-13 15:07 ` Pierre Neidhardt
2018-08-14 10:00 ` Pierre Neidhardt
[not found] ` <handler.32332.B.153303209722315.ack@debbugs.gnu.org>
2018-07-31 10:22 ` Pierre Neidhardt [this message]
2018-08-13 14:59 ` [bug#32332] Acknowledgement ([PATCH 1/4] gnu: Add hashcat.) Leo Famulari
2018-08-13 15:01 ` [bug#32332] [PATCH 1/4] gnu: Add hashcat Leo Famulari
2018-08-14 10:02 ` bug#32332: " Pierre Neidhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877elbhfhu.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=32332@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.