|
Message-ID: <4E412854.9070401@bredband.net> Date: Tue, 09 Aug 2011 14:30:12 +0200 From: magnum <rawsmooth@...dband.net> To: john-dev@...ts.openwall.com Subject: Re: "valid character" class On 2011-08-09 14:02, Solar Designer wrote: > We could also want to introduce a class for control chars, though. > By default, it'd cover whatever chars are usually the control ones on > terminals - see the DumbForce sample. However, for example, > --encoding=cp1251 will turn most chars in the 0x80 to 0x9f range to > non-control, even though they will remain risky to the terminal... ... > So we'll have ?y for valid and ?O for non-control - similar, but > different (as you explained above). Good idea, I think we should go with that. > Oh, and we could want to allocate a consecutive range of character class > letters (maybe a very small range) for user-defined classes. Maybe we > could use digits rather than letters, but then there won't be automatic > complements. Do you mean user-defined as in john.conf, so eg. a ?2 class would correspond to characters defined in some section in the config file? >> One effect of doing so is ability to reject/accept any UTF-8 encoded >> words (from a mixed wordlist like RockYou.txt) using such rules because >> *all* non-ascii characters in UTF-8 contains octets in that range. > > In what range? Sorry, I don't understand what you mean here. There are > UTF-8 characters that are not ASCII yet that do not contain octets in > the 0x80 to 0x9f range. So perhaps you meant something else. No, I was wrong :) The continuation bytes are in the range 0x80-0xBF, I had it as -0x9F in my head. 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.