Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 18 Feb 2013 16:59:54 -0300
From: Claudio André <claudioandre.br@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Bleeding device selection

Em 18-02-2013 16:50, magnum escreveu:
> On 18 Feb, 2013, at 20:42 , Claudio André <claudioandre.br@...il.com> wrote:
>
>> Em 18-02-2013 16:40, magnum escreveu:
>>> On 18 Feb, 2013, at 19:55 , magnum <john.magnum@...hmail.com> wrote:
>>>> Claudio,
>>>>
>>>> Maybe I do something wrong but I currently get these weird results from bleeding on Bull:
>>>> ...
>>>> magnum@...l:src [bleeding-jumbo]$ ../run/john -t -fo:opencl -dev=1
>>>> Device 2: AMD FX(tm)-8120 Eight-Core Processor
>>>> OpenCL error (CL_INVALID_CONTEXT) in file (common-opencl.c) at line (552) - (Error while creating program)
>>>>
>>>>
>>>> Not sure what happens, it used to work fine a while ago.
>>> BTW that example used the new --format=opencl magic, but that is not the cause of the problem. Without that patch, you still get the error for the first opencl format when running "john -t -dev=1".
>>>
>>> magnum
>> The test i mentioned earlier was:
>> ../run/john -t=0 -fo:opencl -de:1 (on bull)
> Ah, of course, thanks. After the sorting of OpenCL format regitration, DES is the first one. I think I'll put those two last for now, or disable them altogether until Sayanyan fixes them.
>
> magnum

The "first" fix attached. mscash 2 works. But, for sure, more tests needed.

Claudio

View attachment "ver" of type "text/plain" (521 bytes)

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ