[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <bcbe5e361be718a7c971f23ee018c2e2@smtp.hushmail.com>
Date: Thu, 20 Mar 2025 23:17:21 +0100
From: magnum <magnumripper@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: Custom password pattern
On 2025-03-20 17:41, Kevin Bailey wrote:
> A while back (~2021) I made a custom incremental rule where passwords had 4 letters followed by 4 digits. I've since forgotten that rule, and, looking through the docs, nothing is jogging my memory. Could I ask how one might write such a rule, or would writing a generate() rule be faster?
We wouldn't say "incremental rule". You seem to mean external mode (or
external filter). You can write an external filter that only lets that
pattern through, and use it when training a custom incremental mode from
a (large) set of relevant training data.
A much easier way (no custom training) is combining incremental mode
with mask mode: "-inc:alpha -mask:?w?d?d?d?d -len=8". This will be
"clever" with the letters but just append digits 0000 to 9999 in a less
optimal way.
Easiest approach though: For such a small keyspace, I'd use mask mode
alone for a dumb brute force, eg. "-mask=?l?l?l?l?d?d?d?d" (for
lower-case letters only) or "-mask=?1?1?1?1?d?d?d?d -1=?l?u" (for mixed
case). If attacking a fast hash such as NT, this will exhaust the
keyspace in minutes so no need to make it smarter.
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.
