[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7e4f561ddf756a0a80dbb27e7ae00944@smtp.hushmail.com>
Date: Tue, 01 Sep 2015 18:23:46 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: plaintext truncation
On 2015-09-01 09:14, magnum wrote:
> On 2015-08-13 20:57, Solar Designer wrote:
>> On Thu, Aug 13, 2015 at 09:09:06PM +0300, Solar Designer wrote:
>>> To implement this, we probably need to introduce a new format flag.
>>> Should we call it FMT_TRUNC? And what should it mean - target system's
>>> truncation or JtR's truncation at a length below the target system's?
>>
>> OK, I think it should be FMT_TRUNC and it should mean the target
>> system's truncation, which JtR will replicate (like it does now).
>>
>> When that flag is not set, JtR will no longer truncate (it will skip),
>> so the name FMT_TRUNC will make sense (truncate when this flag is set,
>> and do not truncate but rather skip when it is not).
>
> So eg. LM will have FMT_TRUNC whereas our NT format will not.
>
> I opened an issue for this, #1724
This is now implemented (3701702). The following formats got FMT_TRUNC
as of now: DEScrypt, bcrypt, LM, tripcode, nethalflm, netlm, PST, RACF,
sapb and VNC.
Some more may need it but these should be the most important ones.
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.
