Date: Thu, 10 Jan 2013 11:48:59 +0400 From: Solar Designer <solar@...nwall.com> To: john-dev@...ts.openwall.com Subject: Re: New plugin load order magic On Sat, Jan 05, 2013 at 01:29:25AM +0100, magnum wrote: > Here's another thought: > > All GPU formats are non-plugs, so load order is chosen manually in john.c. I think we should register them before all plugins and maybe even before the core formats. This means: > > - If you have a GPU build and load crypt-md5 hashes without giving --format, the GPU format will load. > - If we register even before core, NT-opencl will take precedence not only before CPU NT, but also before the LM format. > > Thoughts? I can see this is arguable. However, registering eg. wpapsk-opencl before the cpu version is a no-brainer, so I will do some of those if nothing else. I think this broke --show: $ ./john -sho pw OpenCL platform 0: NVIDIA CUDA, 1 device(s). Using device 0: GeForce GTX 570 OpenCL platform 0: NVIDIA CUDA, 1 device(s). Using device 0: GeForce GTX 570 Build log: ptxas info : Compiling entry function 'cryptmd5' for 'sm_20' ptxas info : Function properties for cryptmd5 104 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads ptxas info : Used 32 registers, 44 bytes cmem, 11 bytes cmem, 8 bytes c mem Local worksize (LWS) 128, Global worksize (GWS) 2097152 OpenCL platform 0: NVIDIA CUDA, 1 device(s). Using device 0: GeForce GTX 570 ****Please see 'opencl_bf_std.h' for device specific optimizations**** u2-des:password:2:0:password:: u3-des:computer:3:0:computer:: 2 password hashes cracked, 38 left OpenCL error (CL_INVALID_CONTEXT) in file (opencl_cryptmd5_fmt.c) at line (169) - (Error Unmapping inbuffer) Alexander
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.