problem solved (as per PM from sakas23).
the hashes are just:
$sip$***Renia*asterisk*REGISTER*sip*192.168.0.38;transport=UDP**2bf3223e****MD5*f7b531XXX
and
$sip$***Renia*asterisk*REGISTER*sip*192.168.0.38;transport=UDP**61b3081d****MD5*e50978XXX
with the XXX replaced with the rest of the MD5 digest. the password is 1234 for both.
The only special thing here is the appended ";transport=UDP" within the URI.
The format itself was already explained dozens of times on github/forum etc and is just:
it depends a lot on the application (asterisk, web auth etc) which fields are used by the "server" in calculating the digest. It's NOT always the same. for instance somtimes the client IP/URI Is important and used to calculate the digest, sometimes in other applications it's ignored. It depends.
remember to not post hashes (and mask them with XXX if the admin/moderator explicitly asks for a masked hash): https://hashcat.net/forum/announcement-2.html
do not waste the times of others to "crack" the hashes. just tell them the (example) password immediately (again, after you got a confirmation by an admin/moderator that you should provide an example with known password).
I will close this thread, since solved
the hashes are just:
$sip$***Renia*asterisk*REGISTER*sip*192.168.0.38;transport=UDP**2bf3223e****MD5*f7b531XXX
and
$sip$***Renia*asterisk*REGISTER*sip*192.168.0.38;transport=UDP**61b3081d****MD5*e50978XXX
with the XXX replaced with the rest of the MD5 digest. the password is 1234 for both.
The only special thing here is the appended ";transport=UDP" within the URI.
The format itself was already explained dozens of times on github/forum etc and is just:
Code:
$sip$*[URI_SERVER]*[URI_CLIENT]*[USERNAME]*[REALM]*[METHOD]*[URI_PREFIX]*[URI_RESOURCE]*[URI_SUFFIX]*[NONCE_SERVER]*[NONCE_CLIENT]*[NONCE_COUNT]*[QOP]*[DIRECTIVE]*[MD5]it depends a lot on the application (asterisk, web auth etc) which fields are used by the "server" in calculating the digest. It's NOT always the same. for instance somtimes the client IP/URI Is important and used to calculate the digest, sometimes in other applications it's ignored. It depends.
remember to not post hashes (and mask them with XXX if the admin/moderator explicitly asks for a masked hash): https://hashcat.net/forum/announcement-2.html
do not waste the times of others to "crack" the hashes. just tell them the (example) password immediately (again, after you got a confirmation by an admin/moderator that you should provide an example with known password).
I will close this thread, since solved