I made some test w/ this format... it seems very similar to the supported -m 1710 format (except the output format, but this is just a matter of fast conversion - base64 -d).
See example here:
https://hashcat.net/trac/ticket/188
Maybe someone can tell me what lengths the salts could have, default seems to be 16 chars.
Please also double check if the algo is right in the ticket, s.t. hashcat developers can start implementing it.
Thx
EDIT:
if you run this w/ mode 1710 (-m 1710) I get this
So basically hashcat is already able to crack this, we just need a parser for the base64 format
UPDATE2: added to beta version of oclHashcat plus (also cpu hashcat will support this format soon)
See example here:
https://hashcat.net/trac/ticket/188
Maybe someone can tell me what lengths the salts could have, default seems to be 16 chars.
Please also double check if the algo is right in the ticket, s.t. hashcat developers can start implementing it.
Thx
EDIT:
if you run this w/ mode 1710 (-m 1710) I get this
Code:
./oclHashcat-plus64.bin --quiet --hex-salt -m 1710 m1710.txt rockyou.txt
4823262e5XXXXc8c55bXXX3c63a4448864ccbXXXX4145ef15501686196XXXXXXf49c4783b8afdXXXXc4d6427XXXX546024XXXXdeadXXXX391adcdaded828XXXX:e3548dbbc769b60f:password
UPDATE2: added to beta version of oclHashcat plus (also cpu hashcat will support this format soon)