[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 16 Aug 2015 20:11:21 +0200
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: Overstrike rule with UTF-8 characters?
On 2015-08-16 14:50, nyxgeek wrote:
> However, if I try to put in a unicode hex value, I get an error. I’m unable to find a way that it will take a unicode character that is longer than 2 hex digits.
>
> Unicode is possible in other areas with John rules. For example, I can do the following, and it works to INSERT:
>
> <* >\r[00123456789] A\p[z0-9]"\xc3\x94”
>
> This will insert a Ô (latin capital letter O with circumflex) at each character position.
>
> I believe the issue is getting John to see the two hex values as a single UTF-8 character. Quotes around the pair, such as in the example above, won't work with the overstrike. Whether it is “\xF8” or “\xc3\x94” — both return an “unknown command” error.
Yes. We have some wild plans to fork a "Unicode Jumbo" that actually
uses UTF-32 internally. This will ultimately fix problems like this.
For current Jumbo though, you can do it like this:
1. Pick a legacy codepage (maybe ISO-8859-1 has what you need). Create
rules just using the characters verbatim, eg.
o[0-9][ôÔ]
And save your file *encoded as ISO-8859-1*. Finally, run john with
--internal-encoding=iso-8859-1 (unless that is your default already).
This works just fine as long as all characters you use fit in one same
codepage.
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.
