Jens Steube
4f1d33216b
Cleanup -m 1450 kernels to latest standard
2016-03-03 16:58:46 +01:00
Jens Steube
e5c8cea390
Cleanup -m 1440 kernels to latest standard
2016-03-03 16:41:47 +01:00
Jens Steube
4ec867f9bb
Cleanup -m 1430 kernels to latest standard
2016-03-03 16:33:39 +01:00
Jens Steube
c0ccfacea6
Cleanup -m 1420 kernels to latest standard
2016-03-03 16:28:23 +01:00
Jens Steube
70fac6ec16
Cleanup -m 1410 kernels to latest standard
2016-03-03 16:20:32 +01:00
Jens Steube
8f8d98665b
Cleanup -m 1400 kernels to latest standard
2016-03-03 16:15:33 +01:00
Jens Steube
9ba3498e4b
Cleanup -m 1400 kernels to latest standard
2016-03-03 16:05:55 +01:00
Jens Steube
bc3801e14c
Merge pull request #253 from Fist0urs/AxCrypt_RawSHA1_format
...
Updated readme with -m 13200 and 13300
2016-03-02 17:47:16 +01:00
Fist0urs
efd8c57a9d
Updated readme with -m 13200 and 13300
2016-03-02 16:05:44 +01:00
Jens Steube
5e73330c5b
Merge pull request #252 from Fist0urs/AxCrypt_RawSHA1_format
...
New format -m 13300 AxCrypt in memory SHA1
2016-03-02 15:58:49 +01:00
Jens Steube
2a2234bfbb
Merge pull request #251 from Fist0urs/Fix_AxCrypt_test
...
-m 13200 Fix test.pl split
2016-03-02 15:42:54 +01:00
Fist0urs
b0f1cb8a98
New format -m 13300 AxCrypt in memory SHA1
2016-03-02 14:35:10 +01:00
Fist0urs
bb15bdf897
-m 13200 Fix test.pl split
2016-03-02 13:55:24 +01:00
Jens Steube
79efecf56d
Merge pull request #250 from Fist0urs/13100_fix_overflow
...
-m 13100 Fix overflow in input hash parsing
2016-03-02 10:43:52 +01:00
Fist0urs
9811a21098
-m 13100 Fix overflow in input hash parsing
2016-03-02 10:31:54 +01:00
Jens Steube
3fc7620dec
Merge pull request #249 from Fist0urs/AxCrypt_format
...
New format -m 13200 AxCrypt
2016-03-02 10:07:17 +01:00
Fist0urs
ad17fba9b6
New format -m 13200 AxCrypt
2016-03-01 19:11:13 +01:00
Jens Steube
eaaeac4aca
New SIMD code for -a 1 -m 1460
2016-02-28 19:58:16 +01:00
Jens Steube
c788ecdb80
New SIMD code for -a 1 -m 1450
2016-02-28 19:58:13 +01:00
Jens Steube
7b10348f7b
New SIMD code for -a 1 -m 1440
2016-02-28 19:58:09 +01:00
Jens Steube
91c2052e59
New SIMD code for -a 1 -m 1430
2016-02-28 19:58:06 +01:00
Jens Steube
9157996a91
New SIMD code for -a 1 -m 1420
2016-02-28 19:58:02 +01:00
Jens Steube
4931824b26
New SIMD code for -a 1 -m 1410
2016-02-28 19:57:59 +01:00
Jens Steube
6cf3e8324d
New SIMD code for -a 1 -m 1400
2016-02-28 19:57:55 +01:00
Jens Steube
22796465e4
Merge pull request #243 from philsmd/master
...
cast to uint is required with some gcc versions, otherwise we get a shift-negative-value warning
2016-02-28 13:28:29 +01:00
philsmd
93a134e9b6
cast to uint is required with some gcc versions, otherwise we get a shift-negative-value warning
2016-02-27 19:56:20 +01:00
Jens Steube
575dcbfd25
Add missing function append_0x01_2x4_S()
2016-02-27 17:29:27 +01:00
Jens Steube
6a2c293457
Merge pull request #241 from philsmd/master
...
minor: reformatting of recently changed code + use uint instead of unsigned int
2016-02-27 17:20:08 +01:00
jsteube
dad03e394d
Fixed two major problems
...
1) SIMD code for all attack-mode
Macro vector_accessible() was not refactored and missing completely.
Had to rename variables rules_cnt, combs_cnt and bfs_cnt into il_cnt which was a good thing anyway as with new SIMD code they all act in the same way.
2) SIMD code for attack-mode 0
With new SIMD code, apply_rules_vect() has to return u32 not u32x.
This has massive impact on all *_a0 kernels.
I've rewritten most of them. Deep testing using test.sh is still required.
Some kernel need more fixes:
- Some are kind of completely incompatible like m10400 but they still use old check_* includes, we should get rid of them as they are no longer neccessary as we have simd.c
- Some have a chance but require additional effort like m11500. We can use commented out "#define NEW_SIMD_CODE" to find them
This change can have negative impact on -a0 performance for device that require vectorization. That is mostly CPU devices. New GPU's are all scalar, so they wont get hurt by this.
This change also proofes that there's no way to efficiently vectorize kernel rules with new SIMD code, but it enables the addition of the rule functions like @ that we were missing for some long time. This is a TODO.
2016-02-27 17:18:54 +01:00
philsmd
0ea05ab292
minor: reformatting of recently changed code + use uint instead of unsigned int
2016-02-25 11:13:11 +01:00
Jens Steube
e688e94384
Merge pull request #239 from philsmd/master
...
this fixes the beta issue #163 (-d and --opencl-platforms not within valid range)
2016-02-24 19:53:17 +01:00
philsmd
2ea295171c
this fixes the beta issue #163 (-d and --opencl-platforms not within valid range)
2016-02-24 19:50:05 +01:00
Jens Steube
31ee4e67d1
Merge pull request #237 from gpuhash/master
...
Fairly strict stamping of WPA salt components
2016-02-24 15:56:02 +01:00
Jens Steube
18ec554ea0
Cleanup of all raw-SHA1 based algorithms
2016-02-24 15:27:02 +01:00
Jens Steube
12fa3d6bfc
Cleanup of all raw-MD5 based algorithms; small change important for later changes
2016-02-24 13:40:38 +01:00
Jens Steube
7e9fee2155
Cleanup of all raw-MD5 based algorithms; Should be done for all raw-SHA1, -SHA256 and -SHA512 based algorithms as well
2016-02-24 11:35:13 +01:00
Jens Steube
531f72c905
Fix this evil bug, pw->i is u32, not u8
2016-02-23 21:24:03 +01:00
Jens Steube
b50637b26e
Add another example of an old budget GPU that benefits from higher vector width than returned by preferred
2016-02-23 20:53:55 +01:00
gpuhash
541f231c23
Minor bugfix
2016-02-23 22:01:55 +03:00
gpuhash
d56394c849
Fairly strict stamping of WPA salt components
2016-02-23 21:31:18 +03:00
Jens Steube
8c89ef0490
Ensure a minimum length for password candidates in autotune
2016-02-23 18:51:28 +01:00
Jens Steube
2236bb972c
We still need on initial testrun in autotune
2016-02-23 15:36:06 +01:00
Jens Steube
01c847ba94
Do not use values that can actually crack a hash in autotune
2016-02-23 15:00:56 +01:00
Jens Steube
a81162b087
Speed up -m 20 in -a 3 mode
2016-02-23 12:18:47 +01:00
Jens Steube
75c6d28a5f
Fix missing memset after previous fix
2016-02-23 10:52:02 +01:00
Jens Steube
efad2bafac
Evil Bug: Because of not-zeroing a buffer it's possible a hash was cracked but not reported as cracked because it was not in scope, but when it was in scope it was already marked as cracked and therefore not reported
2016-02-23 10:36:43 +01:00
Jens Steube
61f87b2981
Try to load libOpenCL.so.1 if libOpenCL.so was not found
2016-02-23 07:57:52 +01:00
Jens Steube
d9fcf87e1c
Increase salt length for raw-md5 based algorithms
2016-02-22 21:35:37 +01:00
Jens Steube
f9834f3dfa
Zero pws_buf before reuse
2016-02-22 21:33:33 +01:00
Jens Steube
e6e5005a6b
Revert "Zero pws_buf before reuse"
...
This reverts commit b409e5e9e1
2016-02-22 21:32:38 +01:00
