Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't pass the "Would you like to split the wordlist?" question #29

Closed
Paul-Courbis-de-Bridiers-de-Villemor opened this issue Jul 24, 2024 · 12 comments

Comments

@Paul-Courbis-de-Bridiers-de-Villemor

Hi

I tried to use ZipRipper but I can't pass teh "Would you like to split the wordlist?" question. I tried to answer OUI (yes) or NON (no) but the question repeats. Peharps is it because I run it on a french Windows ans the retruened answer is neither YES or NO ? (remember years ago I had this issue with the FORMAT command ;-))

Regards

@illsk1lls
Copy link
Owner

illsk1lls commented Jul 25, 2024

Try adding this line to the top of the script

chcp 65001

if it works I’ll add it somewhere into the script

@Paul-Courbis-de-Bridiers-de-Villemor
Copy link
Author

Paul-Courbis-de-Bridiers-de-Villemor commented Jul 26, 2024

Unfortunately this does not change anything

@illsk1lls
Copy link
Owner

illsk1lls commented Sep 4, 2024

I dont have a solution yet.

I am only able to test on english systems as that is my native language

@Paul-Courbis-de-Bridiers-de-Villemor

I'm not sure the problem comes from the language. I removed the question and it works well... Thanks for your work and your support

BTW another stange thing : I have a laptop with a Nvidia GPU RTX 3500 but it is not used by your script. Regards

@illsk1lls
Copy link
Owner

illsk1lls commented Sep 8, 2024

Glad you got it working..

Check and see if the following file is present on your system for nVidia GPU support

C:\Windows\System32\OpenCL.dll

@Paul-Courbis-de-Bridiers-de-Villemor
Copy link
Author

@illsk1lls
Copy link
Owner

Can you type this into cmd prompt and post the results?

WMIC path Win32_VideoController get Name | findstr "."

@Paul-Courbis-de-Bridiers-de-Villemor
Copy link
Author

@illsk1lls
Copy link
Owner

illsk1lls commented Sep 8, 2024

Have you tried the latest version of the script?

I implemented a fix a couple days ago that may correct your issue.

The previously supported nVidia cards would return

NVIDIA Geforce... or NVIDIA Quadro... but your card returns NVIDIA RTX, therefore a previous version of the script would see your card as unsupported

With Geforce there is Geforce GTX and Geforce RTX, nVidia's naming convention is different with yours, and it was already added to the script to support nVidia RTX A**** series professional cards as they also return RTX

@Paul-Courbis-de-Bridiers-de-Villemor

Yes it works great !

Here's the output when starting the new version :

Device 1: NVIDIA RTX 3500 Ada Generation Laptop GPU
Warning: excessive partial hash collisions detected
(cause: the "format" lacks proper binary_hash() function definitions)
Using default input encoding: UTF-8
Loaded 22635 password hashes with 22635 different salts (ZIP-opencl, WinZip [PBKDF2-SHA1 OpenCL])
Loaded hashes with cost 1 (HMAC size) varying from 2824 to 85215
Note: Passwords longer than 21 [worst case UTF-8] to 64 [ASCII] rejected

Juste started it, the GPU usage reported by TakManager is still around 0% but the fans are running faster than normal usage. Don't know if its normal

Here's the speed :

0g 0:00:00:47 0g/s 0p/s 5175Kc/s 5175KC/s zorro..123456
0g 0:00:00:54 0g/s 0p/s 5193Kc/s 5193KC/s 123456..kulotz
0g 0:00:05:56 0g/s 0p/s 5240Kc/s 5240KC/s status..123456

@illsk1lls
Copy link
Owner

it should be using the gpu now..

the speeds look ~ correct

@illsk1lls
Copy link
Owner

illsk1lls commented Sep 9, 2024

I did another update to ensure symbols are being used... They SHOULD have been in the version you have. But just in case I added the flag to force the ASCII char set, and all 93 writeable uppercase, lowercase, numeric, and symbol characters included

It is still rare to see symbols in the status, but if you are seeing them in your current job you can ignore the new version, as the resume feature may break if you change settings

Screenshot 2024-09-08 195200

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants