jwtcrack icon indicating copy to clipboard operation
jwtcrack copied to clipboard

jwtcrack vs hashcat performance

Open quentusrex opened this issue 8 years ago • 2 comments

Have you checked if there is a way to have hashcat try to crack the jwt after it's been transformed/reformatted? I'd be curious how your implementation compares. Code looks good.

quentusrex avatar Jan 21 '17 19:01 quentusrex

I have not checked, but I expect that if hashcat can crack json web tokens, then it is likely faster. jwtcrack makes no use of your GPU, for example.

ojensen5115 avatar Jan 21 '17 19:01 ojensen5115

True, GPU would likely be faster to find collisions, but hashcat does allow you to restrict the computations to the CPU.

On Sat, Jan 21, 2017 at 11:53 AM, Oliver [email protected] wrote:

I have not checked, but I expect that if hashcat can crack json web tokens, then it is likely faster. jwtcrack makes no use of your GPU, for example.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ojensen5115/jwtcrack/issues/1#issuecomment-274284148, or mute the thread https://github.com/notifications/unsubscribe-auth/AALbOD-aO4_Ijq0ICZSys5x8LxGQ6CuAks5rUmIpgaJpZM4LqKc0 .

quentusrex avatar Jan 22 '17 20:01 quentusrex