Hash type?

July 3, 2015, 7:56 am

≪ Previous: Viewing current plain text guess

What type?
6879766D75076D00 (in clear password is 12345678)
6879766D75076D007F (in clear password is 123456789)
6879766D75076D007F1D (in clear password is 1234567899 )
60727C60790863017F (in clear password is 999999999 )
60727C60790863017F1D746072 (in clear password is 9999999999999 )
I get it from Oracle db.

↧

Newb Question

July 3, 2015, 6:59 pm

≫ Next: OpenCart hash

≪ Previous: Hash type?

Hi,

I have a cap file with two WPA handshakes - A and B. How do I make oclHashcat check both of these hashes against several dictionaries?

↧

OpenCart hash

July 4, 2015, 8:22 am

≫ Next: cannot decrypt -_- why ?

≪ Previous: Newb Question

What about OpenCart?
https://www.opencart.com/

Algorithm is

PHP Code:

sha1(salt . sha1(salt . sha1(password))) 

Where salt is a 8-digit hex-string

Can I crack those hashes?

↧

cannot decrypt -_- why ?

July 4, 2015, 7:21 pm

≫ Next: blue screen

≪ Previous: OpenCart hash

Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Pipe
Hash.Target....: <redacted>
Hash.Type......: MD5
Time.Started...: Sun Jul 05 09:16:38 2015 (30 secs)
Speed.GPU.#1...: 0 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 0
Rejected.......: 0
HWMon.GPU.#1...: 0% Util, 43c Temp, N/A Fan

↧

blue screen

July 4, 2015, 11:54 pm

≫ Next: lm hash

≪ Previous: cannot decrypt -_- why ?

i try to run hashcat with true crypt attack but after 5 min the computer get a blue screen.

ehat can i do?

bob

↧

lm hash

July 5, 2015, 1:54 am

≫ Next: combine many .cap or .hccap

≪ Previous: blue screen

i get a 20 hash off lm.

i try to crack them with a hashcat all the char A-Z,a-z0-9 and ?s but the hashcat success to crack only 6 password?

how it can be? this is a lm!!

↧

combine many .cap or .hccap

July 5, 2015, 6:08 pm

≫ Next: Help with - choosing the right grapchic card for MD5 (oclhashcat).

≪ Previous: lm hash

hello,

how can i combine many .cap or .hccap in one file

↧

Help with - choosing the right grapchic card for MD5 (oclhashcat).

July 6, 2015, 5:06 am

≫ Next: Tesla K80 benchmark

≪ Previous: combine many .cap or .hccap

Hi there, I am customizing a CPU from a friend, I understand that oclhashcat's benchmark for MD5 is [8581 Mh/s 2753 Mh/s 135232 Mh/s 92672 Mh/s]. So I plan to get this, however:

1) Which "AMD graphic card" should I buy to use MD5 oclhashcat?

2) Only this models support MD5? - AMD Radeon™ R9 series graphics?

THANK YOU FOR YOUR TIME SIR/MAM.

↧

Tesla K80 benchmark

July 6, 2015, 9:08 am

≫ Next: Radeon 6990 vs Nvidia 970

≪ Previous: Help with - choosing the right grapchic card for MD5 (oclhashcat).

Hi,

I just ran the cudaHashcat64.bin file in benchmark mode. Specs are Nvidia Tesla K80, Dual CPU Intel Xeon E5-2695, 64 GB DD3 RAM, on a 1 TB RAID 0 SSD virtual drive. OS is Ubuntu 14.04.2 LTS.

Results are shown below :

Code:

cudaHashcat v1.36 starting in benchmark-mode...

Device #1: Tesla K80, 11519MB, 823Mhz, 13MCU

Device #2: Tesla K80, 11519MB, 823Mhz, 13MCU

Hashtype: MD4

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  8775.8 MH/s

Speed.GPU.#2.:  8161.1 MH/s

Speed.GPU.#*.: 16936.9 MH/s

Hashtype: MD5

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  4852.8 MH/s

Speed.GPU.#2.:  4539.7 MH/s

Speed.GPU.#*.:  9392.5 MH/s

Hashtype: SHA1

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  1887.3 MH/s

Speed.GPU.#2.:  1786.6 MH/s

Speed.GPU.#*.:  3673.8 MH/s

Hashtype: SHA256

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:   719.7 MH/s

Speed.GPU.#2.:   677.1 MH/s

Speed.GPU.#*.:  1396.8 MH/s

Hashtype: SHA384

Workload: 256 loops, 256 accel

Speed.GPU.#1.:   203.1 MH/s

Speed.GPU.#2.:   192.9 MH/s

Speed.GPU.#*.:   396.1 MH/s

Hashtype: SHA512

Workload: 256 loops, 256 accel

Speed.GPU.#1.:   198.6 MH/s

Speed.GPU.#2.:   192.9 MH/s

Speed.GPU.#*.:   391.5 MH/s

Hashtype: SHA-3(Keccak)

Workload: 128 loops, 256 accel

Speed.GPU.#1.:   171.7 MH/s

Speed.GPU.#2.:   159.3 MH/s

Speed.GPU.#*.:   331.0 MH/s

Hashtype: RipeMD160

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  1178.2 MH/s

Speed.GPU.#2.:  1104.8 MH/s

Speed.GPU.#*.:  2283.1 MH/s

Hashtype: Whirlpool

Workload: 512 loops, 32 accel

Speed.GPU.#1.: 77280.1 kH/s

Speed.GPU.#2.: 76364.3 kH/s

Speed.GPU.#*.:   153.6 MH/s

Hashtype: GOST R 34.11-94

Workload: 512 loops, 64 accel

Speed.GPU.#1.: 67178.1 kH/s

Speed.GPU.#2.: 66645.0 kH/s

Speed.GPU.#*.:   133.8 MH/s

Hashtype: SAP CODVN B (BCODE)

Workload: 1024 loops, 64 accel

Speed.GPU.#1.:   486.5 MH/s

Speed.GPU.#2.:   455.0 MH/s

Speed.GPU.#*.:   941.5 MH/s

Hashtype: SAP CODVN F/G (PASSCODE)

Workload: 1024 loops, 32 accel

Speed.GPU.#1.:   204.9 MH/s

Speed.GPU.#2.:   194.1 MH/s

Speed.GPU.#*.:   399.1 MH/s

Hashtype: SAP CODVN H (PWDSALTEDHASH) iSSHA-1

Workload: 1024 loops, 16 accel

Speed.GPU.#1.:  1345.8 kH/s

Speed.GPU.#2.:  1268.4 kH/s

Speed.GPU.#*.:  2614.2 kH/s

Hashtype: Lotus Notes/Domino 5

Workload: 256 loops, 32 accel

Speed.GPU.#1.: 56339.0 kH/s

Speed.GPU.#2.: 55705.9 kH/s

Speed.GPU.#*.:   112.0 MH/s

Hashtype: Lotus Notes/Domino 6

Workload: 256 loops, 32 accel

Speed.GPU.#1.: 17691.3 kH/s

Speed.GPU.#2.: 17447.6 kH/s

Speed.GPU.#*.: 35139.0 kH/s

Hashtype: Lotus Notes/Domino 8

Workload: 1024 loops, 64 accel

Speed.GPU.#1.:   151.8 kH/s

Speed.GPU.#2.:   143.5 kH/s

Speed.GPU.#*.:   295.3 kH/s

Hashtype: SHA-1(Base64), nsldap, Netscape LDAP SHA

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  1841.2 MH/s

Speed.GPU.#2.:  1768.2 MH/s

Speed.GPU.#*.:  3609.4 MH/s

Hashtype: SSHA-1(Base64), nsldaps, Netscape LDAP SSHA

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  1867.5 MH/s

Speed.GPU.#2.:  1779.1 MH/s

Speed.GPU.#*.:  3646.7 MH/s

Hashtype: descrypt, DES(Unix), Traditional DES

Workload: 128 loops, 64 accel

Speed.GPU.#1.: 56292.2 kH/s

Speed.GPU.#2.: 55702.2 kH/s

Speed.GPU.#*.:   112.0 MH/s

Hashtype: md5crypt, MD5(Unix), FreeBSD MD5, Cisco-IOS MD5

Workload: 1000 loops, 32 accel

Speed.GPU.#1.:  2239.7 kH/s

Speed.GPU.#2.:  2138.0 kH/s

Speed.GPU.#*.:  4377.7 kH/s

Hashtype: sha256crypt, SHA256(Unix)

Workload: 1024 loops, 4 accel

Speed.GPU.#1.:   113.9 kH/s

Speed.GPU.#2.:   108.5 kH/s

Speed.GPU.#*.:   222.4 kH/s

Hashtype: sha512crypt, SHA512(Unix)

Workload: 1024 loops, 8 accel

Speed.GPU.#1.:    34116 H/s

Speed.GPU.#2.:    33014 H/s

Speed.GPU.#*.:    67130 H/s

Hashtype: bcrypt, Blowfish(OpenBSD)

Workload: 32 loops, 2 accel

Speed.GPU.#1.:     1793 H/s

Speed.GPU.#2.:     1769 H/s

Speed.GPU.#*.:     3562 H/s

Hashtype: LM

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:   768.3 MH/s

Speed.GPU.#2.:   758.5 MH/s

Speed.GPU.#*.:  1526.7 MH/s

Hashtype: NTLM

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  8337.2 MH/s

Speed.GPU.#2.:  7975.2 MH/s

Speed.GPU.#*.: 16312.4 MH/s

Hashtype: DCC, mscash

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  2429.9 MH/s

Speed.GPU.#2.:  2290.8 MH/s

Speed.GPU.#*.:  4720.7 MH/s

Hashtype: NetNTLMv1-VANILLA / NetNTLMv1+ESS

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  4958.7 MH/s

Speed.GPU.#2.:  4716.6 MH/s

Speed.GPU.#*.:  9675.4 MH/s

Hashtype: NetNTLMv2

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:   321.2 MH/s

Speed.GPU.#2.:   303.1 MH/s

Speed.GPU.#*.:   624.3 MH/s

Hashtype: Kerberos 5 AS-REQ Pre-Auth etype 23

Workload: 256 loops, 32 accel

Speed.GPU.#1.: 31544.4 kH/s

Speed.GPU.#2.: 31413.7 kH/s

Speed.GPU.#*.: 62958.1 kH/s

Hashtype: EPiServer 6.x < v4

Workload: 512 loops, 256 accel

Speed.GPU.#1.:   949.9 MH/s

Speed.GPU.#2.:   948.5 MH/s

Speed.GPU.#*.:  1898.4 MH/s

Hashtype: EPiServer 6.x > v4

Workload: 512 loops, 256 accel

Speed.GPU.#1.:   657.9 MH/s

Speed.GPU.#2.:   629.7 MH/s

Speed.GPU.#*.:  1287.6 MH/s

Hashtype: MSSQL(2000)

Workload: 512 loops, 256 accel

Speed.GPU.#1.:  1866.2 MH/s

Speed.GPU.#2.:  1769.9 MH/s

Speed.GPU.#*.:  3636.0 MH/s

Hashtype: MSSQL(2005)

Workload: 512 loops, 256 accel

Speed.GPU.#1.:  1827.3 MH/s

Speed.GPU.#2.:  1769.8 MH/s

Speed.GPU.#*.:  3597.1 MH/s

Hashtype: MSSQL(2012)

Workload: 256 loops, 256 accel

Speed.GPU.#1.:   199.7 MH/s

Speed.GPU.#2.:   192.5 MH/s

Speed.GPU.#*.:   392.3 MH/s

Hashtype: MySQL323

Workload: 512 loops, 256 accel

Speed.GPU.#1.: 18445.2 MH/s

Speed.GPU.#2.: 17252.9 MH/s

Speed.GPU.#*.: 35698.2 MH/s

Hashtype: MySQL4.1/MySQL5

Workload: 512 loops, 256 accel

Speed.GPU.#1.:   804.8 MH/s

Speed.GPU.#2.:   771.0 MH/s

Speed.GPU.#*.:  1575.8 MH/s

Hashtype: Oracle 7-10g

Workload: 512 loops, 64 accel

Speed.GPU.#1.:   260.3 MH/s

Speed.GPU.#2.:   257.4 MH/s

Speed.GPU.#*.:   517.7 MH/s

Hashtype: Sybase ASE

Workload: 512 loops, 32 accel

Speed.GPU.#1.: 59927.8 kH/s

Speed.GPU.#2.: 57788.1 kH/s

Speed.GPU.#*.:   117.7 MH/s

Hashtype: Oracle 11g/12c

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  1859.8 MH/s

Speed.GPU.#2.:  1773.0 MH/s

Speed.GPU.#*.:  3632.8 MH/s

Hashtype: PostgreSQL Challenge-Response Authentication (MD5)

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  1479.0 MH/s

Speed.GPU.#2.:  1396.0 MH/s

Speed.GPU.#*.:  2875.0 MH/s

Hashtype: MySQL Challenge-Response Authentication (SHA1)

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:   482.2 MH/s

Speed.GPU.#2.:   463.8 MH/s

Speed.GPU.#*.:   946.0 MH/s

Hashtype: OSX v10.4, v10.5, v10.6

Workload: 512 loops, 256 accel

Speed.GPU.#1.:   951.6 MH/s

Speed.GPU.#2.:   935.3 MH/s

Speed.GPU.#*.:  1886.9 MH/s

Hashtype: OSX v10.7

Workload: 128 loops, 256 accel

Speed.GPU.#1.:   202.1 MH/s

Speed.GPU.#2.:   195.2 MH/s

Speed.GPU.#*.:   397.3 MH/s

Hashtype: OSX v10.8+

Workload: 1024 loops, 2 accel

Speed.GPU.#1.:     2629 H/s

Speed.GPU.#2.:     2541 H/s

Speed.GPU.#*.:     5170 H/s

Hashtype: Android PIN

Workload: 1024 loops, 16 accel

Speed.GPU.#1.:  1257.8 kH/s

Speed.GPU.#2.:  1171.8 kH/s

Speed.GPU.#*.:  2429.6 kH/s

Hashtype: Android FDE <= 4.3

Workload: 1024 loops, 32 accel

Speed.GPU.#1.:   186.7 kH/s

Speed.GPU.#2.:   177.2 kH/s

Speed.GPU.#*.:   363.9 kH/s

Hashtype: scrypt

Workload: 1 loops, 64 accel

Speed.GPU.#1.:    26767 H/s

Speed.GPU.#2.:    26735 H/s

Speed.GPU.#*.:    53502 H/s

Hashtype: Cisco-PIX MD5

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  3170.1 MH/s

Speed.GPU.#2.:  3019.8 MH/s

Speed.GPU.#*.:  6189.9 MH/s

Hashtype: Cisco-ASA MD5

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  3191.8 MH/s

Speed.GPU.#2.:  3024.7 MH/s

Speed.GPU.#*.:  6216.5 MH/s

Hashtype: Cisco-IOS SHA256

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:   714.2 MH/s

Speed.GPU.#2.:   675.4 MH/s

Speed.GPU.#*.:  1389.6 MH/s

Hashtype: Cisco $8$

Workload: 1024 loops, 8 accel

Speed.GPU.#1.:    10904 H/s

Speed.GPU.#2.:    10747 H/s

Speed.GPU.#*.:    21651 H/s

Hashtype: Cisco $9$

Workload: 1 loops, 4 accel

Speed.GPU.#1.:      989 H/s

Speed.GPU.#2.:      980 H/s

Speed.GPU.#*.:     1968 H/s

Hashtype: Juniper IVE

Workload: 1000 loops, 32 accel

Speed.GPU.#1.:  2247.5 kH/s

Speed.GPU.#2.:  2128.9 kH/s

Speed.GPU.#*.:  4376.4 kH/s

Hashtype: Citrix NetScaler

Workload: 512 loops, 256 accel

Speed.GPU.#1.:  1609.3 MH/s

Speed.GPU.#2.:  1533.1 MH/s

Speed.GPU.#*.:  3142.4 MH/s

Hashtype: DNSSEC (NSEC3)

Workload: 512 loops, 256 accel

Speed.GPU.#1.:   725.7 MH/s

Speed.GPU.#2.:   692.4 MH/s

Speed.GPU.#*.:  1418.1 MH/s

Hashtype: WPA/WPA2

Workload: 1024 loops, 32 accel

Speed.GPU.#1.:    92043 H/s

Speed.GPU.#2.:    87218 H/s

Speed.GPU.#*.:   179.3 kH/s

Hashtype: IKE-PSK MD5

Workload: 512 loops, 128 accel

Speed.GPU.#1.:   336.3 MH/s

Speed.GPU.#2.:   322.6 MH/s

Speed.GPU.#*.:   658.8 MH/s

Hashtype: IKE-PSK SHA1

Workload: 512 loops, 128 accel

Speed.GPU.#1.:   176.0 MH/s

Speed.GPU.#2.:   166.5 MH/s

Speed.GPU.#*.:   342.5 MH/s

Hashtype: Password Safe v2

Workload: 1000 loops, 16 accel

Speed.GPU.#1.:    51923 H/s

Speed.GPU.#2.:    51866 H/s

Speed.GPU.#*.:   103.8 kH/s

Hashtype: Password Safe v3

Workload: 1024 loops, 16 accel

Speed.GPU.#1.:   315.2 kH/s

Speed.GPU.#2.:   304.3 kH/s

Speed.GPU.#*.:   619.5 kH/s

Hashtype: 1Password, agilekeychain

Workload: 1000 loops, 64 accel

Speed.GPU.#1.:   750.0 kH/s

Speed.GPU.#2.:   709.3 kH/s

Speed.GPU.#*.:  1459.4 kH/s

Hashtype: 1Password, cloudkeychain

Workload: 1024 loops, 2 accel

Speed.GPU.#1.:     2313 H/s

Speed.GPU.#2.:     2215 H/s

Speed.GPU.#*.:     4528 H/s

Hashtype: AIX {ssha1}

Workload: 64 loops, 128 accel

Speed.GPU.#1.:  9739.8 kH/s

Speed.GPU.#2.:  9207.7 kH/s

Speed.GPU.#*.: 18947.5 kH/s

Hashtype: TrueCrypt 5.0+ PBKDF2-HMAC-RipeMD160 + AES

Workload: 1024 loops, 64 accel

Speed.GPU.#1.:   275.9 kH/s

Speed.GPU.#2.:   263.5 kH/s

Speed.GPU.#*.:   539.3 kH/s

Hashtype: TrueCrypt 5.0+ PBKDF2-HMAC-SHA512 + AES

Workload: 1000 loops, 16 accel

Speed.GPU.#1.:    91353 H/s

Speed.GPU.#2.:    88535 H/s

Speed.GPU.#*.:   179.9 kH/s

Hashtype: TrueCrypt 5.0+ PBKDF2-HMAC-Whirlpool + AES

Workload: 1000 loops, 8 accel

Speed.GPU.#1.:    11608 H/s

Speed.GPU.#2.:    11448 H/s

Speed.GPU.#*.:    23055 H/s

Hashtype: TrueCrypt 5.0+ PBKDF2-HMAC-RipeMD160 + AES + boot-mode

Workload: 1000 loops, 64 accel

Speed.GPU.#1.:   545.9 kH/s

Speed.GPU.#2.:   519.7 kH/s

Speed.GPU.#*.:  1065.6 kH/s

Hashtype: Office 2007

Workload: 1024 loops, 32 accel

Speed.GPU.#1.:    30840 H/s

Speed.GPU.#2.:    28991 H/s

Speed.GPU.#*.:    59831 H/s

Hashtype: Office 2010

Workload: 1024 loops, 32 accel

Speed.GPU.#1.:    15501 H/s

Speed.GPU.#2.:    14518 H/s

Speed.GPU.#*.:    30019 H/s

Hashtype: Office 2013

Workload: 1024 loops, 4 accel

Speed.GPU.#1.:     1933 H/s

Speed.GPU.#2.:     1858 H/s

Speed.GPU.#*.:     3791 H/s

Hashtype: MS Office <= 2003 MD5 + RC4, oldoffice$0, oldoffice$1

Workload: 1024 loops, 32 accel

Speed.GPU.#1.: 39704.4 kH/s

Speed.GPU.#2.: 39378.0 kH/s

Speed.GPU.#*.: 79082.4 kH/s

Hashtype: MS Office <= 2003 SHA1 + RC4, oldoffice$3, oldoffice$4

Workload: 1024 loops, 32 accel

Speed.GPU.#1.: 49605.2 kH/s

Speed.GPU.#2.: 49294.3 kH/s

Speed.GPU.#*.: 98899.4 kH/s

Hashtype: PDF 1.1 - 1.3 (Acrobat 2 - 4)

Workload: 1024 loops, 32 accel

Speed.GPU.#1.: 55177.5 kH/s

Speed.GPU.#2.: 54740.4 kH/s

Speed.GPU.#*.:   109.9 MH/s

Hashtype: PDF 1.1 - 1.3 (Acrobat 2 - 4) + collider-mode #1

Workload: 1024 loops, 32 accel

Speed.GPU.#1.: 62410.2 kH/s

Speed.GPU.#2.: 62139.3 kH/s

Speed.GPU.#*.:   124.5 MH/s

Hashtype: PDF 1.1 - 1.3 (Acrobat 2 - 4) + collider-mode #2

Workload: 1024 loops, 32 accel

Speed.GPU.#1.:   718.4 MH/s

Speed.GPU.#2.:   681.3 MH/s

Speed.GPU.#*.:  1399.8 MH/s

Hashtype: PDF 1.4 - 1.6 (Acrobat 5 - 8)

Workload: 70 loops, 256 accel

Speed.GPU.#1.:  2780.4 kH/s

Speed.GPU.#2.:  2754.4 kH/s

Speed.GPU.#*.:  5534.8 kH/s

Hashtype: PDF 1.7 Level 3 (Acrobat 9)

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:   716.2 MH/s

Speed.GPU.#2.:   676.3 MH/s

Speed.GPU.#*.:  1392.5 MH/s

Hashtype: PDF 1.7 Level 8 (Acrobat 10 - 11)

Workload: 64 loops, 8 accel

Speed.GPU.#1.:     6951 H/s

Speed.GPU.#2.:     6881 H/s

Speed.GPU.#*.:    13831 H/s

Hashtype: Drupal7

Workload: 1024 loops, 8 accel

Speed.GPU.#1.:    11328 H/s

Speed.GPU.#2.:    10934 H/s

Speed.GPU.#*.:    22262 H/s

Hashtype: HMAC-MD5 (key = $pass)

Workload: 512 loops, 256 accel

Speed.GPU.#1.:   709.3 MH/s

Speed.GPU.#2.:   676.6 MH/s

Speed.GPU.#*.:  1385.9 MH/s

Hashtype: HMAC-MD5 (key = $salt)

Workload: 512 loops, 256 accel

Speed.GPU.#1.:  1353.1 MH/s

Speed.GPU.#2.:  1298.3 MH/s

Speed.GPU.#*.:  2651.4 MH/s

Hashtype: HMAC-SHA1 (key = $pass)

Workload: 256 loops, 256 accel

Speed.GPU.#1.:   120.9 MH/s

Speed.GPU.#2.:   120.1 MH/s

Speed.GPU.#*.:   241.0 MH/s

Hashtype: HMAC-SHA1 (key = $salt)

Workload: 256 loops, 256 accel

Speed.GPU.#1.:   180.0 MH/s

Speed.GPU.#2.:   179.6 MH/s

Speed.GPU.#*.:   359.6 MH/s

Hashtype: HMAC-SHA256 (key = $pass)

Workload: 128 loops, 128 accel

Speed.GPU.#1.:   132.1 MH/s

Speed.GPU.#2.:   127.3 MH/s

Speed.GPU.#*.:   259.4 MH/s

Hashtype: HMAC-SHA256 (key = $salt)

Workload: 128 loops, 128 accel

Speed.GPU.#1.:   296.1 MH/s

Speed.GPU.#2.:   288.2 MH/s

Speed.GPU.#*.:   584.3 MH/s

Hashtype: HMAC-SHA512 (key = $pass)

Workload: 128 loops, 128 accel

Speed.GPU.#1.: 44733.5 kH/s

Speed.GPU.#2.: 42966.8 kH/s

Speed.GPU.#*.: 87700.3 kH/s

Hashtype: HMAC-SHA512 (key = $salt)

Workload: 128 loops, 128 accel

Speed.GPU.#1.: 92564.7 kH/s

Speed.GPU.#2.: 89550.9 kH/s

Speed.GPU.#*.:   182.1 MH/s

Hashtype: IPMI2 RAKP HMAC-SHA1

Workload: 256 loops, 256 accel

Speed.GPU.#1.:   345.1 MH/s

Speed.GPU.#2.:   326.7 MH/s

Speed.GPU.#*.:   671.8 MH/s

Hashtype: Half MD5

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  3108.8 MH/s

Speed.GPU.#2.:  2944.6 MH/s

Speed.GPU.#*.:  6053.4 MH/s

Hashtype: Double MD5

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  1372.8 MH/s

Speed.GPU.#2.:  1298.5 MH/s

Speed.GPU.#*.:  2671.2 MH/s

Hashtype: GRUB 2

Workload: 1024 loops, 2 accel

Speed.GPU.#1.:     9181 H/s

Speed.GPU.#2.:     8862 H/s

Speed.GPU.#*.:    18043 H/s

Hashtype: phpass, MD5(Wordpress), MD5(phpBB3), MD5(Joomla)

Workload: 1024 loops, 32 accel

Speed.GPU.#1.:  1425.2 kH/s

Speed.GPU.#2.:  1378.9 kH/s

Speed.GPU.#*.:  2804.1 kH/s

Hashtype: SIP digest authentication (MD5)

Workload: 1024 loops, 32 accel

Speed.GPU.#1.:   556.1 MH/s

Speed.GPU.#2.:   541.0 MH/s

Speed.GPU.#*.:  1097.1 MH/s

Hashtype: SipHash

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  7175.6 MH/s

Speed.GPU.#2.:  6784.6 MH/s

Speed.GPU.#*.: 13960.2 MH/s

Hashtype: Joomla < 2.5.18

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  4679.9 MH/s

Speed.GPU.#2.:  4449.7 MH/s

Speed.GPU.#*.:  9129.6 MH/s

Hashtype: osCommerce, xt:Commerce

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  2796.3 MH/s

Speed.GPU.#2.:  2667.2 MH/s

Speed.GPU.#*.:  5463.5 MH/s

Hashtype: PrestaShop

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  1635.6 MH/s

Speed.GPU.#2.:  1556.3 MH/s

Speed.GPU.#*.:  3191.9 MH/s

Hashtype: IPB2+, MyBB1.2+

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:   913.6 MH/s

Speed.GPU.#2.:   872.8 MH/s

Speed.GPU.#*.:  1786.4 MH/s

Hashtype: vBulletin < v3.8.5

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  1357.5 MH/s

Speed.GPU.#2.:  1300.1 MH/s

Speed.GPU.#*.:  2657.7 MH/s

Hashtype: PHPS

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:  1369.6 MH/s

Speed.GPU.#2.:  1301.2 MH/s

Speed.GPU.#*.:  2670.8 MH/s

Hashtype: vBulletin > v3.8.5

Workload: 1024 loops, 256 accel

Speed.GPU.#1.:   895.6 MH/s

Speed.GPU.#2.:   861.3 MH/s

Speed.GPU.#*.:  1756.9 MH/s

Hashtype: SMF > v1.1

Workload: 512 loops, 256 accel

Speed.GPU.#1.:   949.4 MH/s

Speed.GPU.#2.:   947.6 MH/s

Speed.GPU.#*.:  1897.1 MH/s

Started: Thu Jun 25 17:24:15 2015

Stopped: Thu Jun 25 17:52:38 2015

Performance seems really low compared to gaming GPUs (like the GTX980 or Titans). Shouldn't I get better results ? BTW driver version is 346.46.

Thanks

↧

Radeon 6990 vs Nvidia 970

July 6, 2015, 9:24 am

≫ Next: New Tyan Build Log

≪ Previous: Tesla K80 benchmark

Hi, I have a question about the comparison of these two graphics cards.
I can't find a benchmark of 6990. Which card is best for hash cracking?

Thank you.

↧

New Tyan Build Log

July 6, 2015, 8:56 pm

≫ Next: Can't launch cudaHashcat on Linux.

≪ Previous: Radeon 6990 vs Nvidia 970

OK this will be a build log on a cracking server I have been waiting to build for a long time. If you hace any tips or sugestones that would be great. Also big thanks to epixoip for the ansering my questions. So the parts list is

- 2 E5 2630-V3
- 130ish gbs of DDR4 crucial Ram 16gb a stick
- 8 tarabytes of HDD space and 120gb samsung 840 evo for boot and stuffs
- Tyan case
- 4 R9 290x's by safier overclocked to 1250mhz (ill add 4 more later)

[Image: 2csf5mg.jpg]

[/img]

All the ramz

[Image: w6vxv9.jpg]

All the storagez

[Image: 2lkrvup.jpg]

↧

Can't launch cudaHashcat on Linux.

June 29, 2015, 9:44 am

≫ Next: Can't run cudaHashcat64 v1.36 with WPA2 hccap

≪ Previous: New Tyan Build Log

When launching cudaHashcat v1.36 it says that "ERROR: No NVidia compatible platform found" even though I have everything required.

I'm running x86_64 Linux Mint 17.1 with GTX 460 and 3.19.0-21-generic kernel.
The Nvidia modules are loaded

Code:

alberts00@Alberts-PC-LM ~/Downloads/cudaHashcat-1.36 $ lsmod | grep nvidia

nvidia               8568832  75 

drm                   344064  3 nvidia

I have 352.21 drivers installed from the ppa-edgers repository.

Code:

alberts00@Alberts-PC-LM /media/alberts00/MISC/Cracking/Tools/cudaHashcat-1.36 $ cat /proc/driver/nvidia/version

NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.21  Tue Jun  9 21:53:31 PDT 2015

GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04

What am I missing?

↧

Can't run cudaHashcat64 v1.36 with WPA2 hccap

June 30, 2015, 12:18 am

≫ Next: Under Kali: Error - X needs to be running...

≪ Previous: Can't launch cudaHashcat on Linux.

After update to v1.36, I can't run cudaHashcat64 with following command:
[color=#FF0000]cudaHashcat64.exe -m 2500 PhuLam\RUBY.hccap Dict\090.txt[/color]
It always give me following result (picture)
[Image: image.png]

It showed Status of Cracked but there was nothing (even with wrong Dictionary). I'm using Forceware v353.
I still can use that command on v1.20 but because it is outdated so I had to change system clock to be cable to use it.

Pls help me to adjust the command of new 1.36.

↧

Under Kali: Error - X needs to be running...

June 30, 2015, 3:12 am

≫ Next: SuperMicro SYS-1028GQ-TRT

≪ Previous: Can't run cudaHashcat64 v1.36 with WPA2 hccap

This isn't directly a HC issue, but I'm hoping someone can make sense of it that is more familiar with the ATI drivers than myself.

I picked up some cheap GPUs and was going to benchmark them with some other cheap hardware I picked up. Not having a spare HDD I decided I would just do a full distro install on a flash drive and since I already had Live Kali 1.1.0a flash drive laying around I figured I would use it to install Kali as a full install on an empty flash drive.

There is a guide on how to install Catalyst on Kali, but it uses packages and it doesn't reference the driver version, so I didn't want to waste my time cluttering up the drive with packages with it likely being the 14.9 drivers.

Instead I just ran the commands referenced in the wiki here to fetch and install Catalyst. It all went mostly good, and even though it said the driver was installed successfully it also said check the log for errors.

The error was it failed to build fglrx against DKMS. I could be mistaken, but I thought DKMS is not explicitly required for it run.

So I go ahead and do:
aticonfig --adapter=all --initial -f
reboot

Instead of bringing up the Kali (gnome based) login it goes straight to console now. So I deleted the xorg.conf it created and rebooted.

The gnome desktop starts up as it should now, but when I:
aticonfig --adapter=all --odgt
It tells me that it is not configured, run aticonfig --initial.

I do that (knowing when I reboot it won't start the gnome desktop), and checkout the file and it all looks right and detected all 3 GPUs.

I then try to get the temp again and it tells me the X server is not running. Clearly this isn't the case since I'm using a gnome desktop X has to be running. Just for grins when I /usr/sbin/Xorg it tells me the Server is already active on display 0.

When I run fgl_glxgears I'm only getting 95 frames per second on the animation, so something is wrong there also.
fglrxinfo tells me my display is :0.0 and screen is 0.
I tried exporting the DISPLAY variable with ":0", ":0.0" "0", etc as well to prevent the error.

Oh... I almost forgot... when installing Catalyst it seems to overwrite libGL.so.1 with the 32 bit version even though it detects my arch as 64. I believe this might be why the installs fails with DKMS based on the logs.

After installing Catalyst if I run fglrxinfo I get an error about that lib having ELFCLASS32. I have to fix it by reinstalling libgl1-mesa-glx
and run ldconfig

After doing those two things fglrxinfo works.

While I'm at it, does anyone know of a setup guide working Kali 1.1.0 for installing Catalyst 14.9 (oclHC compatible)? Installing working packages would probably be quicker to deploy than trying to troubleshoot this. But seeing as there probably isn't since I couldn't find one if anyone has some tips on how to Xorg.conf to run the desktop and aticonfig doesn't think X is running that would great.

I could probably save some heartache by installing a different distro but there are reasons why I need it running under Kali long term than just it being something I already had on hand.

Not that is matters but the GPUs are a Radeon 5970 and 5870. aticonfig detects all 3 cores in the Xorg.conf (which for whatever reason prevents gnome from launching on reboot).

I have no problem with these cards on Windows using the win binaries. I would just run them there but the reason for wanting to put them under Kali is I'm writing code to automate oclHC with some of the other tools in the Kali distro.

I could always just do a Ubuntu install or something if that is the defacto distro for running ATI drivers without a hitch, but I would prefer to get the drivers working under Kali with the Gnome desktop.

Note: After digging a little more, it seems like maybe ATI drivers don't play nicely with gnome. Is anyone here using them with gnome and if not what desktop do you run on your linux rigs?

Just to followup on this... I was able to figure out why the ATI installer was throwing errors about DKMS.

The installer needed patched to work with kernel 3.17 and up. I applied the patch and that gave me a successful build.

However, when the installer finishes it tries to run aticonfig --initial and it threw the same ELFCLASS32 error (meaning the damn thing overwrote libgl1 again with a 32 bit version. I purged out the mesa-glx package and reinstalled to get the 64 bit in there.

Then aticonfig runs fine and builds the xorg.conf as usual. At this point I'm hoping for success, but X will still not start with Xorg.conf config. It just says Fatal Server Error: no screens found

So I look in the xorg log and the problem is when it gets to LoadModule fglrx it says says "Couldn't open module fglrx... failed to load module fglrx (module does not exist, 0)"

So I don't know what is going and why I can't the driver working at this point. I even removed gnome and installed XFCE since I read gnome has issues with the ati driver, but its not even getting to the point where it loads a DM, it can't even start X.

Any thoughts? I already made sure the boot load wasn't using nomodeset.

I've been at this for a couple days with no luck and have google'd to hell and back and tried no less than 50 different things. At this point the package manager is all fuxord anyways so I'm over it. I'm going to throw in the towel but it if anyone knows for future reference how to get Kali 64 bit running with oclhc please advise. I am going to install regular Ubuntu and go from there. I found one post that mentions Kali 32 bit can work, but I'm going to go through the hassle of trying with the chance it might not, and although I wouldn't imagine 32 bit would be slower performance on the GPUs I'm not 100% sure on that either so that is another reason I'm not going to try right now.

Just FYI... Ubuntu 14.04.2 Desktop doesn't appear to work either. I figured it would since the Wiki reference the server edition of the same version. But according to AMD they only support Xorg up to 1.15 on 14.9 and Ubuntu ships with Xorg 1.16.0.

I'm going to switch to Xubuntu 14.02 (.0) and see how that goes since apparently Gnome has been reported to by some to cause issues with 14.9 too.

I need a desktop version for this install and it is turning into a major PITA. Just FYI... the error from Xorg log is because it is trying to load the module "glx" and libglx.so has an undefined symbol.

What a mess it is to get exactly 14.9 installed under linux. I wish I could these GPUs on windows but it just isn't an option.

Welp, I thought I was golden with a fresh install of Xubuntu 14.04... the installer ran without error (just like on Ubuntu 14.04.02), but upon reboot it actually booted into X and the resolution was nice, so clearly it was running a new driver.

aticonfig --lsa
shows all of my GPUs, so I thought I was golden, but no...

aticonfig --adapter=all --odgt
ERROR - OD Get Version failed

fglrxinfo
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 157 (ATIFGLEXTENSION)
...
...
...

oclHashcat.bin -b
modprobe: FATAL: Module fglrx not found
...
...

I looked inside of Xorg.0.log and it doesn't show any errors and fglrx is logged a bunch in there and says it is loaded.

This is the 3rd fresh full OS install I've done and no matter what I've tried I can't get the 14.9 drivers to work.

I tried with Kali 1.1.0a (64), Ubuntu LTS 14.04.02 (64), Xubuntu 14.04 (64)... all produce errors.

FYI for anyone in a similar position. On Xubuntu I clicked on Additional Hardware in settings and saw it was set for ATI/AMD Xorg wrapper. Now this might be what it should say since I installed the drivers from the AMD installer and not using a apt-get package (since that wasn't the right driver version).

I switched it to the "proprietary fglrx driver". It took a while for the settings to apply which led me to believe after the fact it might be downloading a package.

When I reboot it would try to overwrite my xorg.cnf file each time, so I had to comment out some lines in /etc/init/gpu-manager.conf. After that it stopped overwriting my xorg.cfg so I could keep what was written by aticonfig --adapter=all --initial

That allowed me to see all 3 GPUs, set the fan speeds and get temp readings.

The strange thing is HC complains it is not the right driver, but when I do fglrxinfo it says I'm using
Compatibility Profile Context 14.301.1001
and that matches the 14.9 Catalyst installer.

I use the --force option get it to run and it is running a top speed and performs all benchmarks and some of my own tests without a problem so far.

Either I do have the right driver but HC is looking elsewhere and seeing something different or I do in fact have the wrong driver, but if it is the latter it sure is running good with it which would be surprising.

↧

SuperMicro SYS-1028GQ-TRT

June 30, 2015, 9:57 am

≫ Next: Thermaltake Chaser mk-1 with 2 Zotac GTX 980, enough cooling ?

≪ Previous: Under Kali: Error - X needs to be running...

Hello Forum

the following new SuperMicro server looks quite interesting...
http://www.supermicro.com/manuals/brochu...server.pdf
(see page 17)

- What could be the reason that the SuperMicro SYS-1028GQ-TRT doesen't seem to support as well AMD GPU (4 Teslas are supported in a 1U chassis!!)?

- Is there a way to install IB-network-adapters in this server (otherwise it cannot be used in cluster, at least to my knowledge)?

Thank's

Bill

↧

Thermaltake Chaser mk-1 with 2 Zotac GTX 980, enough cooling ?

July 1, 2015, 4:57 am

≫ Next: Getting Stats on Rules and Masks for Analysis

≪ Previous: SuperMicro SYS-1028GQ-TRT

As the Title says, will Thermaltake Chaser mk-1 be able to cool the 2 Zotac GTX 980 ? even with OC ?

http://www.thermaltakeusa.com/products-m...C_00001719

↧

Getting Stats on Rules and Masks for Analysis

July 2, 2015, 12:22 am

≫ Next: Linux Catalyst Tutorial Still Valid?

≪ Previous: Thermaltake Chaser mk-1 with 2 Zotac GTX 980, enough cooling ?

I went through the wiki again just now to make sure it wasn't covered... and I couldn't find this specifically answered, not to say it wasn't. But I'm sure this is done regularly by many of you, and to date I've been doing analysis on known passwords to generate rules and masks but I haven't been doing analysis on the efficiency of rules and masks.

So what I'm wondering is if HC (or other tools with compatible rule/mask) can generate a stats file on the performance of the rule, ideally CSV, compared to known passwords?

Instead of using the rules and masks to generate hashes for comparison to other hashes I would like to have it compare the plaintexts of each rule and/or mask it generates against to a wordlist (known pws) and spit out:
combinations tried,words matched,% efficiency (matched/tried)

For example, the "8 character u-l-d-s compliant" is one I'd like to analyze, but geared to WPA. Since the speed on WPA is so slow it isn't practical to run the whole set of masks. But by getting a report on what masks had the highest efficiency against a word list (known PWs) I could whittle the keyspace down a lot. Off the top of my head I would not be surprised if a group of masks in there representing less than 10% of the total keyspace accounting for at least 20 or 30% of the matches.

I'm pretty sure this could be done by writing shell script to feed OHC one mask at a time from that rule file, but I was hoping maybe there was something like this already before I try to reinvent the wheel.

I read the wiki again, I may have missed something. I saw where you can output matched rules. I will give that a try and see what it does.

So I think creating a script, be it python or shell is probably the best way to handle this since I have a variety of separate rules and attacks I want to analyze at once.

What I wondering is has anyone built a script of some type for cracking that does reports/analysis? I figure if something is already out there it would give me a head start and I would actually like to start collecting this on cracking also and not just for analysis against known words.

What I'd like to do is have several types of attacks, ie: combinator, regular dictionary, dictionary + rules, etc...
and then run those as a batch and capture the key metrics from them as each completes. Like attempts, hits, hashes per second, etc.

Right now everything I'm doing it more one off and just going off memory of what is working, or at best writing some notes. I'd like to have all this info output into a csv or sqlite db so I can analyze the success of various attacks and start optimizing more and creating priorities.

If anyone has done anything like this they are willing to share please post a link to the code. If not, I'm going to start on it as time allows and I will post the code when it is ready.

↧

Linux Catalyst Tutorial Still Valid?

July 2, 2015, 6:51 pm

≫ Next: Viewing current plain text guess

≪ Previous: Getting Stats on Rules and Masks for Analysis

My last server install was a while ago when it was 14.04 (not 14.04.2) and I'm not sure if the tutorial steps will still produce a functional install as listed.

I'm in the process of a new headless install after a fiasco of trying to get Catalyst 14.9 working on a desktop distro. One of the things I am fairly sure of from said fiasco is that 14.9 does not work with X server > 1.5 (possibly it is > 1.6, but AMD specifies 1.5 is the highest version). There is a different method of returning the X version string in later versions that causes the driver compilation to fail.

On the linux server tutorial it says to use 14.04.2. It doesn't really matter if it is subversion 2 or 0 because server doesn't come with X and you have to get it from the Trusty repo anyways.

The version on the Trusty repo is X 1.7. From my experience the drivers will not compile against that version of X, short of perhaps patching the AMD installer.

This is probably my 5th or 6th fresh install so I'm hoping to not botch this one too by getting a bunch of incompatible packages and have to start over again because debian package manager is brutal when things get sideways... makes me yearn for the days when everything was compiled from local source.

I guess the question is... anyone here done a Ubuntu server install with AMD 14.9 drivers recently, as described in the tutorial, without issue... or did you have to patch the amd installer or use legacy repos?

Just FYI... going through the tutorial exactly step by step the installer log says the following packages are missing:
dh-modaliases
execstack
debhelper
lib32gcc1

I'll let you guys know if it requires a patched driver or legacy repo/package of Xorg soon.

Ok, so I think you're SOL these days with a 14.9 driver install on a headless without using an old repo for your package manager or patching the installer.

Everything was going together nicely to my surprise... fglrxinfo shows all the right stuff, clinfo shows the right stuff, the gears test is running at the right speeds...

Everything except for amdconfig.

$ amdconfig --adapter=all --odgt
No protocol specified
amdconfig: This program must be run as root when no X server is active

sudo -i
# amdconfig --adapter=all --odgt
No protocol specified
ERROR - X needs to be running to perform AMD Overdrive(TM) commands

Of course is running because I have the unity login screen now and I can run the gears test also.
# ps aux | grep X
root 2131 1.2 4.6 308404 95392 tty7 Ss+ 19:29 0:08 /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

I'm pretty sure when it checks for Xorg it is looking for the proper version string that existed up until 1.5 (or possibly as late as 1.6).

I'll try to uninstall the drivers, patch the installer and reinstall and see what happens.

My bad... it was due to xhost + not getting ran. I put in /etc/rc.local and now all is good. I was getting the X error before on unpatched installer because that issue only affect GDM, not lightdm.

So to answer my own question... the tutorial is still valid for 14.9 on a server install outside of those 4 dependencies that are not installed already on a fresh install.