[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 27 Jul 2011 20:31:19 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Found cp1251 issue (and likely 8850-1) or many code
pages.
Am 27.07.2011 19:02, schrieb jfoug:
> The behavior I am working towards, is that when we upcase a string
> with B5 in it (for cp1251/8859-1), that there will be a xB5 left in
> the upcased string in the end.
Hi Jim,
I think this behavior is correct for all hash algorithms that have been
"invented" prior to unicode.
And, the same logic should be applied for all other characters with
their corresponding upper or lower case character not part of the
non-unicode code page.
I would argue that the same is true for characters with an upper case
version of 2 characters (ß -> SS), at least for automatic upcasing for
case agnostic hashes (not necessarily for applying the u rule to a word
for case sensitive hashes).
If later on you need the old logic for some hash algorithms, we could
support that as well by adding some more flags to the format attributes.
So, don't throw away the old logic too fast.
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.
