Please note, this is a STATIC archive of website hashcat.net from 08 Oct 2020, cach3.com does not collect or store any user information, there is no "phishing" involved.

hashcat Forum

Full Version: feature request: new hashtype support SSHA512 (LDAP)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi,

I saw that you recently added AIX-SSHA512 support:
https://hashcat.net/forum/thread-2247.htm...ht=SSHA512

Are you also planing to support SSHA512 (LDAP/Oracle Directory Server Enterprise Edition) in the near future?

Sample:
https://stackoverflow.com/questions/17877...ash-method

{SSHA512}SCMmLlStPIxVtJc8Y6REiGTMsgSEFF7xVQFoYZYg39H0nEeDuK/fWxxNZ
CdSYlRgJK3U3q0lYTka3Nre2CjXzeNUjbvHabYP

thanks,
pwgen
this should go on trac, not the forums
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
Code:
./oclHashcat-plus64.bin --quiet --hex-salt -m 1710 m1710.txt rockyou.txt
4823262e5XXXXc8c55bXXX3c63a4448864ccbXXXX4145ef15501686196XXXXXXf49c4783b8afdXXXXc4d6427XXXX546024XXXXdeadXXXX391adcdaded828XXXX:e3548dbbc769b60f:password
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)
thank you for your fast answer.

I'd like to test your implementation, but didn't find where to download the beta version.
Is the beta publicly available?
Somewhat.
You could ask Atom for a beta key.
Ok, not so straight forward like 'git pull' for john Wink

From what I have seen your last hashcat releases were about ~1 month apart (2013.06.01 -> 2013.06.26), when can we expect a public release that contains the new -m 1711 (SSHA-512) support?