[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d75b6f6c7aa2ced330e03fd0e5f72163@smtp.hushmail.com>
Date: Sat, 13 Feb 2016 20:59:37 +0100
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: Doing raw SHA512 hashes
On 2016-02-13 17:45, Frank Wang wrote:
> Awesome, thanks magnum! I know the opencl_*.c files call the kernels you
> mentioned, but what files actually run the functions in the opencl_*.c
> files?
I don't understand what you mean. The opencl_*.h are headers #include'd
by the kernels. The format calls the kernel. One such format is
opencl_office2013_fmt_plug.c.
magnun
> My goal is write an implementation of just raw SHA256/SHA512 hashes using
> openCL.
>
> Frank
>
> On Thu, Feb 4, 2016 at 1:54 AM, magnum <john.magnum@...hmail.com> wrote:
>
>> On 2016-02-03 21:39, magnum wrote:
>>
>>> On 2016-02-02 23:49, Frank Wang wrote:
>>>
>>>> I am trying to run about 10 million raw SHA 512 hashes in my program and
>>>> offloading it to a GPU will make it substantially faster. It seems like
>>>> John the Ripper has this functionality, but it seems to be intertwined
>>>> with
>>>> the password cracking capabilities. Are there any SHA 512 OpenCL
>>>> implementations that are easy to separate and integrate into my program?
>>>> Possibly that already exist in John the Ripper?
>>>>
>>>
>>> I would think so. Our current GitHub code contains (among other
>>> implementations) generic SHA512 macros in src/opencl_sha512.h which is
>>>
>>
>> Sorry, that should be opencl_sha2.h. The other file is an other
>> implementation that I'm not well acquainted with.
>>
>> 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.
