[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <74ae6625adad29fe591937cd010a24ad@smtp.hushmail.com>
Date: Tue, 21 Feb 2012 10:16:16 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Sorted format list
The format list has grown big in Jumbo. This is a good thing of course,
but it's becoming hard to digest. I have a trivial patch that sorts the
generated list before outputting, like this:
--format=NAME force hash type NAME: afs/bf/bfegg/bsdi/crc32/crypt/
cryptmd5-opencl/cuda-cryptmd5/cuda-cryptsha256/
cuda-cryptsha512/cuda-mscash/cuda-mscash2/cuda-phpass/
cuda-rawsha224/cuda-rawsha256/des/dmd5/dominosec/
dragonfly3-32/dragonfly3-64/dragonfly4-32/
dragonfly4-64/drupal7/dummy/dynamic_n/epi/hdaa/
hmac-md5/hmac-sha1/hmac-sha224/hmac-sha256/
hmac-sha384/hmac-sha512/hmailserver/ipb2/krb4/krb5/lm/
lotus5/md4-gen/md5/md5ns/mediawiki/mscash/mscash2/
mschapv2/mskrb5/mssql/mssql05/mysql/mysql-fast/
mysql-sha1/mysql-sha1-opencl/nethalflm/netlm/netlmv2/
netntlm/netntlmv2/nsldap/nt/nt-opencl/nt2/oracle/
oracle11/pdf/phpass-md5/phpass-opencl/phps/pix-md5/
pkzip/po/rar/raw-md4/raw-md5/raw-md5-opencl/raw-md5u/
raw-sha/raw-sha1/raw-sha1-opencl/raw-sha224/
raw-sha256/raw-sha384/raw-sha512/salted-sha1/sapb/
sapg/sha-crypt-256/sha-crypt-512/sha1-gen/ssh/
ssha-opencl/sybasease/trip/xsha/xsha512/zip
Is this OK? Actually, I'd also like to replace '/' with space, because
IMO it gets much easier to read. It would look like this:
--format=NAME force hash type NAME: afs bf bfegg bsdi crc32 crypt
cryptmd5-opencl cuda-cryptmd5 cuda-cryptsha256
cuda-cryptsha512 cuda-mscash cuda-mscash2 cuda-phpass
cuda-rawsha224 cuda-rawsha256 des dmd5 dominosec
dragonfly3-32 dragonfly3-64 dragonfly4-32
dragonfly4-64 drupal7 dummy dynamic_n epi hdaa
hmac-md5 hmac-sha1 hmac-sha224 hmac-sha256
hmac-sha384 hmac-sha512 hmailserver ipb2 krb4 krb5 lm
lotus5 md4-gen md5 md5ns mediawiki mscash mscash2
mschapv2 mskrb5 mssql mssql05 mysql mysql-fast
mysql-sha1 mysql-sha1-opencl nethalflm netlm netlmv2
netntlm netntlmv2 nsldap nt nt-opencl nt2 oracle
oracle11 pdf phpass-md5 phpass-opencl phps pix-md5
pkzip po rar raw-md4 raw-md5 raw-md5-opencl raw-md5u
raw-sha raw-sha1 raw-sha1-opencl raw-sha224
raw-sha256 raw-sha384 raw-sha512 salted-sha1 sapb
sapg sha-crypt-256 sha-crypt-512 sha1-gen ssh
ssha-opencl sybasease trip xsha xsha512 zip
Also, I'd really like the CUDA formats renamed to eg. cryptmd5-cuda so
they end up in the "right" place in this list. This would make it easier
to notice that a certain format has alternatives.
Even after that, we have inconsistencies like sha-crypt-256 vs.
cryptsha256-cuda. I'm willing to rename sha-crypt-256 to just
cryptsha256 (it's shorter!). There are other cases, like salted-sha1 vs.
ssha-opencl. Perhaps salted-sha1 should be renamed to ssha. BTW I think
I should rename raw-sha to raw-sha0 to avoid confusion.
Another thing we might consider is to drop some of the indentation in
this list to get fewer lines, but that's a matter of taste... it will
become unaligned with the rest of the usage blob.
What do you guys think?
magnum
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
