Unable to Ctrl+C abort

[FalcoGer]

⚠️IMPORTANT⚠️ if you do not fill this out, we will automatically delete your issue. We will not help anyone that cannot fill out this template.

• Have you read our Wiki page "Common Issues & Their Solutions"?
  Yes

Describe the bug
When running ciphey on a bare, unsalted NT hash using ciphey -f hash.txt -w ~/repositories/SecLists/Passwords/Leaked-Databases/rockyou.txt -v you can abort just fine until it runs into ciphey.basemods.Searchers.ausearch:search:256 - At depth 5.

When it reaches that point, no amount of Ctrl+C can abort it and you have to kill with Ctrl+\ or a kill signal.

Plaintext
⚠️IMPORTANT⚠️ The below code is non-negotiable for "Ciphey didn't decrypt...." problems. If you do not tell us your plaintext, we will not help you.

Hashfile

Thomas:02d90eda8f6b6b06c32d5f207831101f

Plaintext

i<3ruby

Version
⚠️IMPORTANT⚠️ We need this information because different environments will induce different bugs in Ciphey

• OS/Distro: Ubuntu Mate 20.04 (5.4.0-70-generic x86_64 amd)
• Python version: Python 3.8.5
• Ciphey versions:

Name: ciphey
Version: 5.11.1
Summary: Automated Decryption Tool
Home-page: None
Author: Brandon
Author-email: [email protected]
License: MIT
Location: /home/paul/.local/lib/python3.8/site-packages
Requires: click, base58, pylint, loguru, pybase62, appdirs, click-spinner, flake8, pyyaml, rich, cipheydists, base91, cipheycore, yaspin
Required-by: 
---
Name: cipheycore
Version: 0.3.2
Summary: 
Home-page: None
Author: Cyclic3
Author-email: [email protected]
License: None
Location: /home/paul/.local/lib/python3.8/site-packages
Requires: 
Required-by: ciphey
---
Name: cipheydists
Version: 0.3.34
Summary: A collection of distributions, character sets and dictionaries for use in ciphey
Home-page: None
Author: Cyclic3
Author-email: [email protected]
License: None
Location: /home/paul/.local/lib/python3.8/site-packages
Requires: 
Required-by: ciphey

• Did you use Docker? - No

Verbose Output
⚠️IMPORTANT⚠️ Verbose output will tell us why it's not working the way we expected it to be.
Run Ciphey with ciphey -vvv and paste the results into Pastebin.com or a GitHub Gist
ciphey_log.txt

To Reproduce
Steps to reproduce the behavior:

1. Run anything that ciphey can't decode or decrypt
2. wait for it to hang
3. Ctrl+C

Expected behavior
The process traps SIGINT correctly and exits.

Any other information?
Happens with random input as well. I just hammered in some random keys with the -t flag and no wordlist, same behavior.

[bee-san]

Hey, I think thiis is due to cipheycore which is set for being burnt to the ground archival. We're fixing this ASAP as our
#1 priority :D

Will be fixed in 6.0.0 :) #591

[xzl0326]

I also got stuck and couldn't terminate when decrypting base64 using Cipher
Cryptography: Z2V0cHJvcCByby5zeXN0ZW0uYnVpbGQuZmluZ2VycHJpbnR8YXdrIC1GLyAne3ByaW50ICRORn0nfG1kNXN1bXxjdXQgLWMxLTY
Clear text: getprop ro. system. build. fingerprint | awk - F/'{print $NF}' | md5sum | cut - c1-6

[xzl0326]

我是直接用ciphey -t 输入密文的