Problems with Truecrypt container

[AntsSymphonie]

Hi,
sorry Noob here. I tried to get the pw of an old TC container. I basically have about 1000 possible passwords that might be right. 
I created a new container with standard settings with pw from this list to test if it works.
AES
RIPEMD-160

I used 

Code:

dd if=test.tc of=test.hash bs=512 count=1

to get a hash file.
I then use 

Code:

hashcat.exe -m 6212 -a 0 -w 3 test.hash dict.txt

but it doesn't find the pw



For any admins reading this. The security question when registering asks for the current stable version but expects v.6.2.5

output:

Code:

hashcat (v6.2.6) starting

Successfully initialized the NVIDIA main driver CUDA runtime library.

Failed to initialize NVIDIA RTC library.

* Device #1: CUDA SDK Toolkit not installed or incorrectly installed.
            CUDA SDK Toolkit required for proper device support and utilization.
            Falling back to OpenCL runtime.

* Device #1: WARNING! Kernel exec timeout is not disabled.
            This may cause "CL_OUT_OF_RESOURCES" or related errors.
            To disable the timeout, see: https://hashcat.net/q/timeoutpatch
nvmlDeviceGetFanSpeed(): Not Supported

OpenCL API (OpenCL 3.0 CUDA 11.6.134) - Platform #1 [NVIDIA Corporation]
========================================================================
* Device #1: NVIDIA GeForce GTX 1660 Ti with Max-Q Design, 5440/6143 MB (1535 MB allocatable), 24MCU

OpenCL API (OpenCL 3.0 ) - Platform #2 [Intel(R) Corporation]
=============================================================
* Device #2: Intel(R) UHD Graphics 630, 6464/13024 MB (2047 MB allocatable), 24MCU

Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 64

dict.txt: Byte Order Mark (BOM) was detected
Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1

Optimizers applied:
* Zero-Byte
* Single-Hash
* Single-Salt
* Slow-Hash-SIMD-LOOP

ATTENTION! Potfile storage is disabled for this hash mode.
Passwords cracked during this session will NOT be stored to the potfile.
Consider using -o to save cracked passwords.

Watchdog: Temperature abort trigger set to 90c

Host memory required for this attack: 1343 MB

Dictionary cache hit:
* Filename..: dict.txt
* Passwords.: 775
* Bytes.....: 60590
* Keyspace..: 775

The wordlist or mask that you are using is too small.
This means that hashcat cannot use the full parallel power of your device(s).
Unless you supply more work, your cracking speed will drop.
For tips on supplying more work, see: https://hashcat.net/faq/morework

Approaching final keyspace - workload adjusted.

Session..........: hashcat
Status...........: Exhausted
Hash.Mode........: 6212 (TrueCrypt RIPEMD160 + XTS 1024 bit (legacy))
Hash.Target......: test.hash
Time.Started.....: Tue Dec 13 15:13:57 2022 (0 secs)
Time.Estimated...: Tue Dec 13 15:13:57 2022 (0 secs)
Kernel.Feature...: Pure Kernel
Guess.Base.......: File (dict.txt)
Guess.Queue......: 1/1 (100.00%)
Speed.#1.........:    4312 H/s (1.39ms) @ Accel:32 Loops:128 Thr:256 Vec:1
Speed.#2.........:        0 H/s (0.00ms) @ Accel:32 Loops:32 Thr:16 Vec:1
Speed.#*.........:    4312 H/s
Recovered........: 0/1 (0.00%) Digests (total), 0/1 (0.00%) Digests (new)
Progress.........: 775/775 (100.00%)
Rejected.........: 664/775 (85.68%)
Restore.Point....: 0/775 (0.00%)
Restore.Sub.#1...: Salt:0 Amplifier:0-1 Iteration:1920-1999
Restore.Sub.#2...: Salt:0 Amplifier:0-0 Iteration:0-32
Candidate.Engine.: Device Generator
Candidates.#1....: $HEX[730069006d006f006e00340079006f0075002300730069006d006f006e00340079006f0075000d00] -> $HEX[00]
Candidates.#2....: [Copying]
Hardware.Mon.#1..: Temp: 55c Util: 23% Core:1756MHz Mem:5994MHz Bus:8
Hardware.Mon.#2..: N/A

[marc1n]

Use this command:

hashcat.exe -m6212 -a0 -w4 --hwmon-disable --status --status-timer=60 --outfile-format=2 test.hash -r rules/dive.rule dict.txt

It will check the rules of your probable passwords from the dict.txt file
more about rules here:

https://hashcat.net/wiki/doku.php?id=rule_based_attack

[AntsSymphonie]

Do I need the -r part? The pw for the test file is in the dict.txt. When I remove it I basically get the same result as before.

Use this command:

hashcat.exe -m6212 -a0 -w4 --hwmon-disable --status --status-timer=60 --outfile-format=2 test.hash -r rules/dive.rule dict.txt

It will check the rules of your probable passwords from the dict.txt file
more about rules here:

https://hashcat.net/wiki/doku.php?id=rule_based_attack

[marc1n]

Do I need the -r part? The pw for the test file is in the dict.txt. When I remove it I basically get the same result as before.

Use this command:

hashcat.exe -m6212 -a0 -w4 --hwmon-disable --status --status-timer=60 --outfile-format=2 test.hash -r rules/dive.rule dict.txt

It will check the rules of your probable passwords from the dict.txt file
more about rules here:

https://hashcat.net/wiki/doku.php?id=rule_based_attack

Once you write possible passwords and once you write that test passwords...and that's a big difference because if you don't have possible ones cracking will be very difficult and time consuming...

[AntsSymphonie]

Do I need the -r part? The pw for the test file is in the dict.txt. When I remove it I basically get the same result as before.

Use this command:

hashcat.exe -m6212 -a0 -w4 --hwmon-disable --status --status-timer=60 --outfile-format=2 test.hash -r rules/dive.rule dict.txt

It will check the rules of your probable passwords from the dict.txt file
more about rules here:

https://hashcat.net/wiki/doku.php?id=rule_based_attack

I think we have a misunderstanding. For the test case with known password I already know that it is in the dict.txt, but it still doesn't work. For the real file, I'm relatively sure I have the password in the list, but thats a problem I can tackle once I get the test case working.
Once you write possible passwords and once you write that test passwords...and that's a big difference because if you don't have possible ones cracking will be very difficult and time consuming...

[AntsSymphonie]

Ok, found the mistake.
It was this warning. I changed the dictionary file to utf-8 encoding and it worked for the test file and then also with the actual file.

Code:

dict.txt: Byte Order Mark (BOM) was detected