[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTiktJBXeGQ3qyMb2ucQgQOXvhV64b1nGdcxUmAk3@mail.gmail.com>
Date: Wed, 19 Jan 2011 17:06:07 -0700
From: RB <aoz.syn@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: Plain Text/No-op Password Format
On Wed, Jan 19, 2011 at 16:14, Solar Designer <solar@...nwall.com> wrote:
> The advantage of the first two is that they allow JtR to trim and ignore
> any whitespace characters before/after the "ciphertexts" or to refuse to
> load such ciphertexts, whereas with #3 and #4 such whitespace, if it
> inadvertently gets into an input file, will affect/distort the results.
Full encoding doesn't bother me, and the reasons for doing so seem
sufficiently more compelling than that of simplicity. The whitespace
problem is definitely something to consider, as anything allowed on
the keyboard should probably be usable.
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.
