[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADjXMSeGaqLCd6pWBzSCibUNr7qCLXeNaLUm4vPiFrj0vBA9YQ@mail.gmail.com>
Date: Sun, 12 Jan 2014 16:12:46 -0800
From: C GPS <nro117gm@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: How to use Wordlists with John The Ripper
It's now running.
NRO117:~ L7$ cd magnumripper
NRO117:magnumripper L7$ ./run/john sha512.txt
Loaded 1 password hash (PBKDF2-HMAC-SHA512, GRUB2 / OS X 10.8+
[PBKDF2-SHA512 128/128 SSE4.1 2x])
Press 'q' or Ctrl-C to abort, almost any other key for status
0g 0:00:00:31 0.90% 2/3 (ETA: 17:02:03) 0g/s 57.44p/s 57.44c/s 57.44C/s
summit..sunfire
Back to my original question: I assume that JTR is using built in
wordlists. Is it helpful for me to supply additional wordlists? If so -
will they work in conjunction with the built in wordlists?
I have downloaded the paid version of wordlists from openwall.com which
supplies a folder containing:
all.lst
languages (folder)
mangled.lst
passwords (folder)
pub (folder)
and of course the README and LICENSE txt files
If I can now determine the command line needed to utilize these I'm unsure
which file within the folder to load. I have read the options in order to
make an attempt at loading a wordlist but it does not specify which file to
open or what all of these other files are.
Again: Yes, I'm green but if it helps I am learning fast. Almost afraid to
ask the above question.
Thanks again! Infinitely
On Sun, Jan 12, 2014 at 1:30 PM, C GPS <nro117gm@...il.com> wrote:
> What excellent instruction. Thank you.
> It seems to be loaded.
>
> I got to:
> :run L7$ ls -l john
>
> Resut:
>
> -rwxr-xr-x 1 L7 staff 2869952 Jan 12 13:22 john
>
>
> I also then ran
>
>
> cd ../run
>
> ./john --test
>
>
> and it went through a whole series of Benchmarking.
>
> So.. I think it's native.
>
>
> On Sun, Jan 12, 2014 at 12:44 PM, Frank Dittrich <
> frank_dittrich@...mail.com> wrote:
>
>> On 01/12/2014 08:48 PM, C GPS wrote:
>> > One final question and thanks for all of your help thus far. I've
>> learned
>> > a lot with this thread.
>> >
>> > What disambiguated hash did you load? In other words I know one doesn't
>> > load the long form hash as I entered it above, and the disambiguations
>> I've
>> > come up with seem to be incorrect. Can you tell me the short form you
>> > entered?
>>
>> Your Pro version will not load this hash at all.
>> On he other hand, the latest development snapshot
>> will load the hash exactly in that long form you posted in your previous
>> mail.
>>
>> But that means, you'll have to download and build the latest development
>> snapshot from the link Solar gave you, beacause support of that hash
>> type has only recently been added to the (upcoming) JtR-jumbo version:
>>
>> https://github.com/magnumripper/JohnTheRipper/tarball/bleeding-jumbo
>>
>> This will provide a compressed tar archive from the latest available
>> development version.
>> Currently the file is named
>> magnumripper-JohnTheRipper-1.8.0-4923-g9aaa81d.tar.gz, but the g.......
>> part will change when someone changes the source code.
>> So, in case of problems, you might to remember and report that name.
>> Then we'll know exactly what version you downloaded.
>>
>> After downloading, this file has to be extracted:
>>
>> tar xvzf magnumripper-JohnTheRipper-1.8.0-4923-g*.tar.gz
>> (I used the * wildcard here, so that it will work for any filename
>> following that pattern.)
>>
>> Then, cd into the new directory, and further down into the src directory:
>>
>> cd magnumripper-JohnTheRipper-*/src
>>
>> Then
>>
>> make macosx-x86-64-native
>>
>> Then
>>
>> cd ../run
>>
>> Then
>>
>> ls -l john
>>
>>
>> If building the latest development version worked, you'll see the new
>> john binary here.
>>
>> If not, then may be there's something missing in your build environment.
>> Feel free to ask for help if anything goes wrong in the process.
>>
>> Frank
>>
>
>
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.
