Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Wed, 12 Dec 2012 00:27:11 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: OpenCL kernel search path

On 12 Dec, 2012, at 0:09 , Solar Designer <solar@...nwall.com> wrote:
> There was also:
> 
> <hacktalkblog> @solardiz Having some issues with Jumbo 7 OpenCL support in Mac OSX 10.8.2 with ATI Radeon late 2011 macbook pro http://pastebin.com/dPbNDCiE
> 
> The pastebin gives:
> 
> [00:09:24 connection@...DOS.local:~]$ john -form:raw-md5-opencl --device:1 crackme/md5test.txt
> OpenCL platform 0: Apple, 2 device(s).
> Using device 1: ATI Radeon HD 6770M
> OpenCL error (UNKNOWN ERROR :() in file (common-opencl.c) at line (39) - (Source kernel not found!)
> 
> Looks like "john" was found via PATH, in which case argv[0] does not
> give the path to the run directory... or/and maybe the directory did not
> contain the OpenCL kernels in this specific case.
> 
> I am not sure what we want to do about this, if anything.  For
> non-system-wide builds/installs, we can simply state that "john" should
> be invoked with the path specified (at least relative to cwd) - e.g.,
> "./john" in the run directory or "../run/john" if invoking from src.

Yes. Just a documentation issue. OTOH we could add a path in john.conf, for users wanting to place stuff in some specific place. But that might clash with systemwide.

> We'll need to support system-wide installs with OpenCL kernels, though.
> I recall that this topic was brought up on john-users in Gentoo package
> context, but I don't recall whether there was any conclusion or
> determination.

To my surprise it was reported as working fine, with no tweaks. Everything ends up in the /etc direcory if memory serves me, and is found.

magnum

Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.