[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e5b4c4939cc66d10f8605b26bb7974aa@smtp.hushmail.com>
Date: Tue, 21 Feb 2012 20:31:56 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Sorted format list
On 02/21/2012 08:00 PM, Samuele Giovanni Tonon wrote:
> btw opencl is rather new, we still have time to sort/change format
> name to something easier to type, to remember and to look for; any
> suggestion ?
Well you could use -gpu as a prefix. And actually, CUDA formats could
use that prefix too except where they clash (currently crypt-md5 and
phpass).
So an OpenCL build would have ssha-gpu, raw-md5-gpu, nt-gpu,
raw-sha1-gpu, cryptmd5-gpu, phpass-gpu and mysql-sha1-gpu.
A CUDA build would have cryptmd5-gpu, phpass-gpu, cryptsha256-gpu,
cryptsha512-gpu, mscash-gpu, mscash2-gpu, rawsha256-gpu and rawsha224-gpu.
A GPU build (ie. both) would have ssha-gpu, raw-md5-gpu, nt-gpu,
raw-sha1-gpu, cryptmd5-gpu, cryptmd5-cuda, phpass-gpu, phpass-cuda,
mysql-sha1-gpu, cryptsha256-gpu, cryptsha512-gpu, mscash-gpu,
mscash2-gpu, rawsha256-gpu and rawsha224-gpu.
Maybe that would be confusing? But in some ways it would be less
confusing - the user only cares about using GPU, she won't care if it's
CUDA or OpenCL under the hood.
Just thinking out loud here.
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.
