Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191104145011.GA22972@openwall.com>
Date: Mon, 4 Nov 2019 15:50:11 +0100
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: Help needed with with --bilocker: No passwors hash loaded Error

On Mon, Nov 04, 2019 at 09:29:16AM +0000, john difool wrote:
> I'm trying to use JtR to uncrypt a bitlocker-ed image disk on Linux (Debian distribution)
> 
> I've downloaded and compiled last version. Here are some of the output with opencl info

Great.

> in bold characters

You can't really have those on a text only mailing list (no HTML).

> OpenCL support ............................. yes

So yes, you successfully configured for OpenCL, and the build is
supposed to have that or else it wouldn't complete, which I assume it
did (since you quoted a gcc invocation late in the build).

> > john --list=formats

However, you don't have any -opencl formats in the output of this
command.  My guess is you ended up running a "john" binary other than
what you built.  Maybe your system has one installed globally.

To use your local build, you probably need something like:

cd ../run
./john --list=formats

Note the leading "./", which requests running the program from the
current directory.

> I've created a dictionary and generated hashes using John2bitlocker but whatever the hash file I use I get an error "No passwors hash loaded". Why is that?
> 
> > bitlocker2john  -i disk.img
> 
> > cat target_hash
> $bitlocker$3$16$3adb3d7f8dfbe03dc3f4cef931aad1e9$1048576$12$e04a4339a66cd50162000000$60$1e93c2f48241aa8af137dee6e6aa3ad5584febef62857e0462a674cbe8b21268b1dc7633b302fcc5a268cdd52d44adb5b55cb3e1c082c79d724bc903
> 
> > john --format=bitlocker --wordlist=dictionnary.txt target_hash
> 
> Using default input encoding: UTF-8
> No password hashes loaded (see FAQ)

Some of the subtypes of Bitlocker (non-)hashes are only supported by our
OpenCL format (thus, bitlocker-opencl), not the CPU format (bitlocker).

So you actually need an OpenCL-enabled build, and I suggest that you
omit the "--format" option in order to let JtR autodetect whatever
format will accept the hash without you limiting its possible choices.

The command may be like:

./john target_hash

You'll add more options after you get this basic invocation working.

I hope this helps.

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.