Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <07598a6249a635479913013b9e9b8883@smtp.hushmail.com>
Date: Fri, 18 Jan 2019 19:28:34 +0100
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: gnome keyring password length limit

On 2019-01-18 17:13, kc atgb wrote:
> Le , magnum a écrit :
>> Try to explain the encoding problem and I'll try to guide you through
>> it!
> 
> With the release I used initially, I had a lot of trouble to make john
> generate the password with the correct encoding, and then display them
> correctly, and to give the password file correctly encoded to john even
> with forcing things in john.conf.
> 
> I succeeded after I converted john.conf from utf8 to iso8859 format.
> 
> With the current files from git, I have the same troubles and converting
> from utf8 to iso8859 is not working because of a special char in subsets
> section for number 3.

Are you actually on some ancient machine not supporting UTF-8? If not, I 
think you might have derailed here. With a terminal correctly set to 
UTF-8, the Jumbo defaults should work for most situations. Going 
backwards in time will only make things worse.

If you are indeed on a machine not supporting UTF-8, just change a few 
of the config defaults (I can work out which if you give me some time) 
and you should be set.

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.