c-jwt-cracker
c-jwt-cracker copied to clipboard
How long does it take to decrypt?
eyJhbGciOiJBMjU2S1ciLCJjdHkiOiJKV1QiLCJlbmMiOiJBMjU2R0NNIiwidHlwIjoiSldUIn0.y2qOedKZ9ARDRplnqi_BKF4xNFRT_efQP_UnzcgQGyLZ34z8rbtoyg.uZUm__embCk8O75x.T45_PBiTnEm81KHomFnVdZeekbW7wrSiGXCIVgUV54y8X5gwI6GI6TWdCHTJuyQo7P4RHNhF4USlOUkBJmUozo_XAUWdEd7QKNPDfo-Udw9Ih1Ah8cLBUaJGZbbjVLrphbeu-QPZc_1qi4F80ehzDOEITCjKE0MhW1CdJtxfHOVtWAnIc2bck_jFhDe4AkO-jB1VmpsO210CPx3I7jAO4GdQDpKvehF3iN1MnU9nJE9uMnWsFHnjEHGhrR12fdf5RPGqi03NsENkfYhTYTIfq4GEAgGStQndRUaRJjHWvWDOv8d_BBOMmNh-PByCb-nTdqCQ5wZyEujRQw05mX0USePdJBMJNAhVTrayeewvVQHopECXnAD8S0qK9GMNcTh29caTs1EsHwXtP3-Qier-6rOaVZlQwkd0sMk7CI_KWUyClF3bjAhx8zqyjanTYmwoZ1c2VqBheFydUE7SQjWPUOBB_cx7tXe2l_Z8XLRwT_cJWLCnrLShBg5DzHpEiT74wTSmvx8Q5OAtwnkdGYJezRZiF6sNSjckiq-E3lo_ZlTXL58aG_Ph0mByJ9R-IrguiPN6ICu6rlJZ0e63lWD2qKXyD7Rj86MEhl_X42ntGPQUhugwb4dNaTvB8jWMaW3mDJtfbHeuPknemYEnNdq_d3R0gfaM0FQZcrxLgDLIHcpflu4O3aotxIVZ5Z89H5TJQmB_adZce8KQ4mQafvPMBu6Ebwq7wYiJp8DilrHSwzlRUYCsUG-0NsRGI07liqDeoIKsf4ZUi-no7GOrWRkfUH_dceZ5lGi1nRr85Cmxvz9YJmEe5Cc0OT0JT3R36S1y910M_WQ7srwz4IA.BKR51ksUIxmLeYWMY632Lw
I don't know, but your token can be "kidnapped" because it has no expiration time.
Depends on secret length and number of threads available.
I've been doing some testing on AWS with a c5.24xlarge which has 96 cpus (although only 62 get used) and my unscientific wall time figures are as follows:
4 characters -- 17ms 5 characters -- 0.79s 6 characters -- 1m2s 7 characters -- 32m30s
Any secrets longer than this, and single machine cpu-based cracking starts to become a bit unreasonable.
我的双路E5 2660 C2 花了3个小时跑完这个脚本,出现了No solution found :-(
Waiting for ./jwtcrack eyJhbGciOiJodHRwOi8vd3d3LnczLm9yZy8yMDAxLzA0L3htbGRzaWctbW9yZSNobWFjLXNoYTI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE2NjIwNjU2NzAsImV4cCI6MTk3NzY4NDg3MCwiSWQiOiI0YjRjMjhmNS0wNTM2LTQ3YjMtOWM4NC00MjQ2OTVhOTNhNDIiLCJTZXNzaW9uSWQiOiI3MmM2YThiYy05MWM4LTRlNjUtODY4Mi00ZDk4OTI0ZWUwZWEiLCJFbWFpbCI6ImpvaG55ZGVub3VtZWFAZ21haWwuY29tIn0.qo3Gnu-MbKEXeSENUlKKo6lKjh1hIeFYBi42YfHH0UQ
..