[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F5BB939.6080601@gmail.com>
Date: Sat, 10 Mar 2012 17:27:37 -0300
From: Claudio André <claudioandre.br@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Fwd: Re: [john-users] Help on SHA-512
I like to hear that. Thanks.
By the way, this git commands could be somewhere in wiki. They are
helpful, at least to newcomers like me.
---
The errors are happening in constants (not in my hardware):
__constant uint64_t k[] = {
0x428a2f98d728ae22LL
Here i changed LL to UL. Worked. I'll do more tests and give you another
patch.
1. when you can run, start using low values to KPC and LWS. Meanwhile,
code is safe and slow.
2. http://gcc.gnu.org/onlinedocs/gcc/Long-Long.html
Claudio
Em 10-03-2012 16:52, magnum escreveu:
> Now we're talking, this compiles. But the OpenCL compile fails:
>
> Compilation log: :11:5: error: 'long long' type is invalid in OpenCL
> :11:27: error: 'long long' type is invalid in OpenCL
> :11:49: error: 'long long' type is invalid in OpenCL
> :12:5: error: 'long long' type is invalid in OpenCL
> :13:5: error: 'long long' type is invalid in OpenCL
> :13:27: error: 'long long' type is invalid in OpenCL
> ...(lots more)...
>
> OpenCL error (CL_INVALID_PROGRAM_EXECUTABLE) in file
> (opencl_cryptsha512_fmt.c) at line (277) - (Error creating kernel.
> Double-check kernel name?)
>
> This might run in AMD-CPU-cpecific mode or whatnot but I can't run it.
>
> magnum
>
>
> On 03/10/2012 08:16 PM, Claudio André wrote:
>> Do i miss anything? (The new diff format attached.)
>> ------------
>>
>> git clone git://github.com/magnumripper/magnum-jumbo jumbo-unstable
>> cd jumbo-unstable
>> git checkout -b openCL_crypt512
>>
>> - Do the job
>>
>> git commit -a -m 'OpenCL Crypt 512 (development)'
>> git format-patch magnum-jumbo --stdout> openCL_crypt512.patch
>>
>> make clean linux-x86-64-opencl
>> ../run/john --test=1 --format=cryptsha512-opencl
>>
>>
>> ------------
>> Do the job means (put new updated content).
>>
>> cd src
>> cp ~/bin/john/novo/src/Makefile .
>> cp ~/bin/john/novo/src/opencl_cryptsha512.h .
>> cp ~/bin/john/novo/src/opencl_cryptsha512_fmt.c .
>> cp ~/bin/john/novo/src/john.c .
>> cp ~/bin/john/novo/src/common-opencl.c .
>> cp ~/bin/john/novo/src/opencl/cryptsha512_kernel.cl ./opencl
>>
>> git add opencl_cryptsha512.h
>> git add opencl_cryptsha512_fmt.c
>> git add opencl/cryptsha512_kernel.cl
>>
>>
>>
>> Em 10-03-2012 15:24, magnum escreveu:
>>> On 03/10/2012 06:55 PM, Claudio André wrote:
>>>> Ok, i "git updated" few days ago, sorry. I suppose the makefile changed
>>>> recently.
>>> That was OK. The problem is I can't compile your code at all.
>>>
>>>> Now i did:
>>>> git clone git://github.com/magnumripper/magnum-jumbo jumbo-unstable
>>>> Do the necessary changes.
>>>> make clean linux-x86-64-opencl
>>>> ../run/john --test=1 --format=cryptsha512-opencl
>>>>
>>>> And git diff to send. Sorry.
>>> This newest patch totally lacked the change in Makefile but this is not
>>> the problem The problem is I can't build your opencl_cryptsha512_fmt.c.
>>> The reason might be trivial but I don't have more time right now.
>>>
>>>> PS: I haven't found exactly what git commands you recommend to send a
>>>> path.
>>> "git format-patch" rocks. It will produce output suitable for non-git
>>> users too.
>>>
>>> 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.
