Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Tue, 14 Aug 2012 00:19:40 +0200
From: magnum <>
Subject: --field-separator-char (was: Re: 1.7.9-jumbo-6)

On 2012-06-21 18:33, magnum wrote:
> On 2012-06-21 18:24, Frank Dittrich wrote:
>> On 06/21/2012 06:15 PM, jfoug wrote:
>>> Can we remove this from the usage of JtR (at least make it a hidden
>>> option)
>>> --field-separator-char=C  use 'C' instead of the ':' in input and pot
>>> files
>>> I added this, for usage in dynamic, but I really feel it is (or
>>> should be)
>>> deprecated.  $HEX$ in the salt field should be used instead.

I need --field-sep for other formats than Dynamic, and other uses than

>> I think making --field-separator-char=C a hidden option (or not even
>> listing it under --list= hidden-options) is a good idea.
>> (As long as it is a hidden option, bash completion will nevertheless use
>> it when pressing [tab].)
> Done

>> If someone uses this option nevertheless, a warning should be written to
>> stderr, pointing out the correct solution for the problem of hashes
>> containing colons (as part of the salt).
> Not done (I don't have time, please add it if you want to)

On second thought, I disagree. There's no such thing as "the correct
solution" here. We have various options for various situations.


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.