[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150814131229.GH25121@openwall.com>
Date: Fri, 14 Aug 2015 16:12:29 +0300
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: plaintext truncation
On Fri, Aug 14, 2015 at 12:18:13AM +0200, magnum wrote:
> The plans we have for interally representing plaintexts as UTF-32
> throughout all of core will fix this and *many* other issues. All such
> figures will always mean characters, not necessarily bytes.
>
> BTW right now I don't really expect that new code to ever (!) merge into
> Jumbo as we know it. It will stay as another fork, whatever name we'll
> give it. As a heads-up, I expect to continue my work mainly in that
> fork. However, all this is just ideas so far, we'll see what actually
> happens. Also, the plans right now has a nice side effect: All format
> plugins will be 100% compatible between those two forks/versions of Jumbo.
"As a heads-up, I expect to continue my work mainly in that fork."
Does this mean someone else will need to volunteer as the new primary
maintainer for jumbo?
Alexander
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.
