Mask option: date?

[John Doe]

What would be the best approach to limit the key space of a password that contains a date, e.g. DDMM? Rights now I'm scripting a batch of hashcat command with masks like


0?d0?d
1?d0?d
2?d0?d
300?d
310?d
etc.


but that's not the easiest nor the fastest solution. Any ideas for a smarter / faster approach? Thanks!

[ScAnMaG]

Charset 1: 0123
Charset 2: 01
Charset 3: 12
Charset 4: 90
===================================================
Mask: ?1?d?2?d - For DDMM Only
For example: 0712
===================================================
Mask: ?u?l?l?l?u?l?l?1?d?2?d - For AnyNameDDMM
For example: JohnDoe2709
===================================================
Mask: ?u?l?l?l?u?l?l?1?d?2?d?3?4?d?d - For AnyNameDDMMYYYY
For example: JohnDoe27091985 / JohnDoe15112001

[John Doe]

Charset 1: 0123
Charset 2: 01
Charset 3: 12
Charset 4: 90
===================================================
Mask: ?1?d?2?d - For DDMM Only
For example: 0712
===================================================
Mask: ?u?l?l?l?u?l?l?1?d?2?d - For AnyNameDDMM
For example: JohnDoe2709
===================================================
Mask: ?u?l?l?l?u?l?l?1?d?2?d?3?4?d?d - For AnyNameDDMMYYYY
For example: JohnDoe27091985 / JohnDoe15112001

Thanks for your reply. This is not an efficient solution though. It will also try dates (DDMM) like '3919'. There are only 366 possible options. This  means  brute forcing not ~9 bits (366 = 8.5 bits) but 12 bits, expanding the keyspace 8 times (2^(12-9)). This means that I need to buy 7 extra GPUs to make up the inefficiency of the mask  (please note that the crypto data that I'd like to crack consists of a date and way more, making cracking on 1 GPU impossible with current speeds).

[rico]

Stick the masks in a mask file: https://hashcat.net/wiki/doku.php?id=mas...mask_files

[John Doe]

Stick the masks in a mask file: https://hashcat.net/wiki/doku.php?id=mas...mask_files

How will this help? AFAIKS that's automating the problem with an inefficient key space.
What I'm actually looking for is something like:

-1 {01,02,03..,31}
-2 {01,02,03..,12}
-3 {1970,1971,1972..,2016}

And crack dates (DDMMYYYY) with ?1?2?3, with DDMM within 9 bits.

Cheers,

John

[rico]

Oh yeah, forgot about that bit of the puzzle. Maybe rules files then? One with append days, one with months and one with years?

days.rule:
$0 $1
$0 $2
$0 $3
..
$3 $1

months.rule:
$0 $1
$0 $2
$0 $3
..
$1 $2


crack including "-r days.rule -r months.rule" in the command. Not sure how to only use the generated content though. My example rules simply append DDMM combos (including 31st Feb I know) to something else.