![]() ![]() So if you have 1000 iterations, you call it 8000 times. To produce the required 320 bit key, you call it 8 times. But this is only to produce a 160 bit key. ![]() For each iteration of PBKDF2-HMAC-SHA1 you call 4 times the SHA1 transform. The PBKDF2-HMAC-SHA1 part is what makes the entire calculation slow. No problem so far, many algorithms like WPA are doing the same thing. Actually we are generating a 320 bit key using PBKDF2-HMAC-SHA1 this way but its then truncated to 256 bit. Here is why:ġPassword uses PBKDF2-HMAC-SHA1 to derive a 256 bit key. The reason for the high speed is what I think this might be a design flaw. HWMon.GPU.#4.: 99% Util, 55c Temp, N/A FanĪs you can see, oclHashcat-plus is running with nearly 3Mhash/s using my two hd6990's which is ~ the speed of two hd7970 (a bit faster). Watchdog: Temperature retain trigger set to 80cĭevice #1: Kernel. Watchdog: Temperature abort trigger set to 90c Hashes: 1 total, 1 unique salts, 1 unique digestsīitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes There are other solutions out but they are using CPU to do the AES. So what you see here is worlds first 100% GPU implementation of 1Password keychain. I finally got it working and then ported it to GPU. So I started to dig into AES and experimented a bit with it and the 1Password keychain. However, thats the story so far why I started to add 1Password to oclHashcat-plus. It installed without problems, has nice icons, seemed to be very intuitive and it there is also a browser integration so I thought I should finally move from keepass to 1Password. I quickly downloaded the tool and was impressed how easy it worked. I was happy with keepass and never thought about changing. I did not pay much attention to Agilebits 1Password before. At this time, some guy posted a request on hashcat forum asking for support to crack 1Password Agilebits keychain. How to start digging into AES? I thought the best way is to combine the learning phase with something that uses AES and so add some nice new algorithm. Problem is, I never used AES before and it was totally a new world for me. To finish support for efficiently cracking TrueCrypt there is no way around adding AES to GPU. To finally crack TrueCrypt, you have to decrypt a 448 byte block of data using AES, Serpent or Twofish or some obscure combinations of them. Unfortunately there is another milestone. That is PBKDF2-HMAC-Whirlpool, -RipeMD160 and -SHA512. ![]() This week I finally finished the first milestone, the hashing part of TrueCrypt. ![]() In the last weeks I spend a lot time adding TrueCrypt to oclHashcat-plus since there have been lots of requests for it and I can see how forensic world will benefit from it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |