[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e1ab3edafcb3fe14cd0afc4b52f2732d@smtp.hushmail.com>
Date: Sat, 26 Sep 2015 17:30:28 +0200
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: UTF support on nt-opencl format
On 26/09/15 11:58, Luis Rocha wrote:
> I just tried it out but due to some reason I get a error message "Can't use
> ?L placeholder without --internal-encoding" . Not sure what is wrong. Same
> for ?D and ?U.
>
> $ ./john --list=build-info | head -1
> Version: 1.8.0.6-jumbo-1-1262-g71003d2
>
> $ ./john hashes --internal-encoding=utf-8 --encoding=utf-8
> --mask=?1?1?1?1 -1=?L?D
> Warning: detected hash type "NT", but the string is also recognized as
> "NT-old"
> Use the "--format=NT-old" option to force loading these as that type instead
> Loaded 5118 password hashes with no different salts (NT [MD4 128/128 SSE4.1
> 4x3])
> Can't use ?L placeholder without --internal-encoding
>
> Any idea?
You need to use a legacy codepage for internal encoding. UTF-8 is not a
codepage, it's an encoding. The internal encoding stuff (it should be
called --internal-codepage but that's too late now) relies on an 8-bit
legacy codepage that can hold the characters you need to process. So
there wasn't any bug but I now changed that error output to be more
specific.
$ ../run/john -stdout --mask=?L --internal-encoding=utf8
Can't use ?L placeholder without using a codepage in --internal-encoding
(UTF-8 is not a codepage).
$ ../run/john -stdout --mask=?L --internal-encoding=cp737
α
β
γ
δ
ε
ζ
η
θ
ι
κ
λ
μ
ν
ξ
ο
π
ρ
σ
ς
τ
υ
φ
χ
ψ
ω
ά
έ
ή
ϊ
ί
ό
ύ
ϋ
ώ
34p 0:00:00:00 100.00% (2015-09-26 17:29) 566.6p/s ώ
magnum
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.
