Quantcast
Channel: hashcat Forum - All Forums
Viewing all 8099 articles
Browse latest View live

Cracking 10 digit password with CudaHashcat

$
0
0
I need help with cracking a 10 digit number that is a WPA password using CudaHashcat. What do I input if I know the first three numbers? The first three numbers are 760 but how do I tell hashcat that? This is what I have so far and it needs work:

Quote:cudahashcat --hash-type 2500 --attack-mode 3 /root/ssid.hccap -1 ?d

Info about hardware

$
0
0
Hello to all of you.
I'm new in this field, and need some advices from experienced users.

I have Dell lap top with i7 mobile version 2670 QM CPU @ 2.2 GHZ, N vidia 525m graphic card and 8 gb od DDR3 ram memory at 1333 mhz.

I'm cracking passwords with aircrack ng on Kali Linux with mu CPU power and after some time my lap top been too hot, also I get 2500 combinations per second average.

I read some articles on the internet, and I find some informations about cracking passwords with GPU power, and here I'm.

I also have a desktop PC with next configuration :

MB : ASRock B75M-GL
CPU : Intel Celeron G1610 @ 2.60GHz
GPU : Sapphire HD 5870 1GB GDDR5 256 bit
RAM : Corsair 4 GB @ 1600 mhz

I want to try this combination with Hashcat and try to crack password with power of my GPU, I also read on the internet that my card is very good for this kind of job.

Can someone tell me, what I can expect from this configuration ( how many combinations per second ), if internet connection is good quality ?

I want to try this because I heard that is the fastes way and I do not want to stress my lap top and CPU because it is too hot after 15 minutes of cracking, and I need much longer time to crack a password.

Thanks in advance for your comments, suggestions and help.

ADL_Overdrive5_Temperature_Get(): -1

oclHashcat v1.30

$
0
0
Download here: https://hashcat.net/oclhashcat/

This release is again focused on performance increase of the kernels and bugfixes. However, the most code intensive change in this version was the new workload dispatcher as it's part of the the oclHashcat core. The old one wasn't that bad, but the new one is simply faster which adds up to the increased performance of the kernels.

As always, make sure to unpack into a new folder. Never reuse an existing oclHashcat folder (because of the cached kernels).

One important thing for AMD users: You will need to update to the latest beta version of catalyst before updating oclHashcat. We've decided to no longer wait for AMD to ship the latest "stable" catalyst driver simply because they aren't any more stable than beta drivers...

There's also one change made to the binaries itself. We now are using our own toolchain (thanks to crosstool-ng) to create our own binaries with an older glibc. That was required to make the binaries compatible to linux distributions using an older glibc. That means you should be able to run cudaHashcat and oclHashcat now without glibc patching on Kali, some (older) Debian systems, CentOS 6.4, etc..


New algorithms

  • Skype
  • Peoplesoft
  • md5($salt.md5($pass))
  • Mediawiki B type
  • Kerberos 5 AS-REQ Pre-Auth etype 23 as fast algorithm (reimplementation)
  • Android FDE
  • scrypt
  • Password Safe v2
  • Lotus Notes/Domino 8

Skype and Peoplesoft are just new parsers as you were already able to crack them with older oclHashcat versions by using the generic hashtypes and by formating the hashes in a way that oclHashcat can load them. By adding parsers we just make it more comfortable for the users to load the hashes as you can use them in their native output.

The md5($salt.md5($pass)) generic algorithm was simply added as it was required for the Mediawiki B type hash-type. It's a simple scheme that does not require any special comment.

The Kerberos 5 algorithm is a reimplementation as fast algorithm type. That is the case if an algorithm is fast enough to require an on-gpu candidate generator. The algorithm actually was fast enough and just by not selecting it as fast hash it lost some performance. By switching it to a fast type we got some speedup for free.

Now it gets interessing. The Android FDE algorithm that was added is the one that is using PBKDF2-HMAC-SHA1 + CBC-ESSIV-AES with 2000 iterations. Only tricky part was the "detection" of a filesystem. Note that this algorithm isn't used anymore in newer android devices. The new one uses scrypt instead of PBKDF2. For details about how the algorithm is working see here: https://hashcat.net/forum/thread-2270.html

That's why we've added scrypt to GPU. And what should I tell, it's PITA. The goal of scrypt to run slow on GPU has been fulfilled. Just one note about that. The intention (if I understood currectly) was to make the computuation slow because the memory access is slow. Well that's not what made it slow actually. It's simply the lack of the total memory available on the card. Note that, to run fast with GPGPU, you have to run many tasks in parallel. That means that you have to allocate a huge amount of memory for each parallel task and this is what kills the gpu, not the access time. Also note that this scrypt variant is the real scrypt, not the minimal version that is used for litecoin. The litecoin version uses extreme low settings for N, r and p such that it is not required to work on global memory for all operations. We're using a fully functional scrypt in which you can set N, r and p dynamically. For the benchmark, we're using the defaults of 16k, 8, 1.

The Password Safe v2 was also very interessting. This algorithm actually runs slower than the current one used in Password Safe v3, which is also supported with hash-type 5200. On my AMD hd7970, the v2 version runs with 101 kH/s while the v3 version runs with 506.2 kH/s but I don't think it's too much of a problem. Both run slow enough and are salted.

Last algorithm that was added is Lotus Notes/Domino 8 which was discovered by our own philsmd. Therefore, oclHashcat v1.30 is world's first Lotus Notes/Domino 8 (H-hashes) cracker! For details about how the algorithm is working see here: https://hashcat.net/forum/thread-3550.html


Performance increase


We've added some very special GPU type specific instructions that gave the speed boost. This means the increase of the performance depends on the GPU type. Every GPU type required different changes. It's mostly those chipsets that make the differences in cracking speed, after subtracting the effect that the shader count and clock stepping has.

In other words: Lookup your chipset, then you can apply the percentage change on your current speed with oclHashcat v1.21:

For our Test we used (all stock clocked):

VLIW1: R9 290x
VLIW4: hd6990 (only 1st core)
VLIW5: hd5770

sm_50: gtx 750Ti
sm_21: gtx 560Ti
sm_20: gtx 580


AMD VLIW1 (R9 * and hd7* series, state of the art)

[Image: changes_v130_vliw1.png]

AMD VLIW4 (most of the hd6* series)

[Image: changes_v130_vliw4.png]

AMD VLIW5 (most of the hd5* series)

[Image: changes_v130_vliw5.png]

NVidia sm_50 (Maxwell chipset, ex: 750Ti, future state of the art)

[Image: changes_v130_sm50.png]

NVidia sm_21 (Older vector chipset)

[Image: changes_v130_sm21.png]

NVidia sm_20 (Older scalar chipset)

[Image: changes_v130_sm20.png]

some of the algorithms became a bit slower. That is mostly because of driver changes that we were unable to compensate with more efficient code.

Here's the entire performance change table: https://hashcat.net/misc/p130_img/changes_v130.png


Full changelog v1.21 -> v1.30


Quote:
Type: Driver
File: Kernel
Desc: Added support for AMD Catalyst v14.6 and v14.7 (beta) driver

Type: Driver
File: Kernel
Desc: Added support for NV ForceWare 340.24 driver

Type: Driver
File: Host
Desc: added support for AMD ADL 7.0

Type: Reimplementation
File: Host
Desc: Rewrote dispatcher thread from scratch

Type: Reimplementation
File: Kernel
Desc: Rewrote support for algorithm -m 7500 = Kerberos 5 AS-REQ Pre-Auth etype 23 as fast algorithm

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 23 = Skype
Trac: #474

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 133 = PeopleSoft
Trac: #419

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 3710 = md5($salt.md5($pass))

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 3711 = Mediawiki B type
Trac: #410

Type: Feature
File: Kernel
Desc: Added support for algorithm -m 8800 = Android FDE

Type: Feature
File: Host
Desc: Added support for algorithm -m 8900 = scrypt
Trac: #295

Type: Feature
File: Host
Desc: Added support for algorithm -m 9000 = Password Safe v2

Type: Feature
File: Host
Desc: Added support for algorithm -m 9100 = Lotus Notes/Domino 8

Type: Feature
File: Host
Desc: Added support for --increment with attack-mode 6 and attack-mode 7
Trac: #450

Type: Change
File: Kernel
Desc: Renamed -m 112 = Oracle 11g to -m 112 = Oracle 11g/12c

Type: Change
File: Kernel
Desc: Renamed -m 5200 = Password Safe SHA256 to -m 5200 = Password Safe v3

Type: Change
File: Kernel
Desc: Renamed -m 5800 = Samsung Android Password/PIN to -m 5800 = Android PIN

Type: Bug
File: Kernel
Desc: fixed bug in warp kernels were zero-byte leading plains are incorrectly displayed
Trac: #428

Type: Bug
File: Kernel
Desc: fixed bug in SAP CODVN B (BCODE) misses correct password in rare cases
Trac: #495

Type: Bug
File: Kernel
Desc: Enforce maximum password length for -m 8500 = RACF
Trac: #431

Type: Bug
File: Kernel
Desc: Rule iNX = Insert character X at position N didn't allow to insert a character at the very end of the plain
Trac: #457

Type: Bug
File: Host
Desc: fixed bug in bitmap table leading to uncracked 64-bit based hashes if bitmap_size > 0xffff

Type: Bug
File: Host
Desc: Separator for -m 22 = Juniper Netscreen/SSG (ScreenOS) should always be ':', regardless of --separator
Trac: #454

Type: Bug
File: Host
Desc: fixed memory problem of rules_optimize tool
Trac: #456

Type: Bug
File: Host
Desc: fixed crash with --show when using hash types which use "long" salts, e.g. -m 5600
Trac: #489

Type: Bug
File: Host
Desc: fixed output problem when using --attack-mode 1/6/7, sometimes output was truncated
Trac: #494

Type: Bug
File: Rules
Desc: Reduced generated2.rule file to 64k (65536) rules
Trac: #436

WARN: ADL_Overdrive5_FanSpeedInfo_Get(): -5

R9 280X speed

$
0
0
Hi everyone!

I've got ~42,000 H/s while bruting WPA handshake on Sapphire R9 280X. Is this normal for 280X? Honestly, I was expecting a little better Smile

Or maybe there is some way to increase speed? I would appreciate any help.

P.S. Changing "Accel" and "Loops" settings didn't help.

.cap hash extraction

$
0
0
hoping for help

i had an idea playing with hashcat where it says

Added hashes from file bt.hccap: 1 (1 salts)

is there a way you can make hashcat display the loaded hash/salt or is there any program or website i can use to extract the hash/salt

i tried the following

editcap -v -D 0 BTHub3-MQZX.cap /dev/null wich gave me loads of hashes to many to list

wireshark (had a look around reading a big manual on how to use)

capinfos BTHub3-MQZX.cap which gave me 1 SHA1, RIPEMD160, MD5

md5sum BTHub3-MQZX.cap and bt.hccap gave me MD5 hash ee82e86b4e10b3e9aa761e89fe3fff60 and 6efcd68a648a0255606eef37f9e15f45 respectively

tested all hashes with all different -m 0 - 7600 (hashcat did not work took some time) i know the caps good i tried in aircrack and cowpatty with small passlist
and got KEY FOUND! [ 8d9bb4aee3 ]

i stripped my cap down to just the 4 eapol packets which i then ran the stripped cap through the above programs got different hashes c91ab0c98f27612b40e9a5a7d22107f1

!!!!someone please tell me if i can get the hash/salt from my cap file you should be able to if it can load it then you should be able to see it or if those programs gave the right hash were did i go so wrong!!!!

should stress if you dont want to tell me how (the full command) to do it please point me in the right direction and i will figger it out my self

thanks

newbie but keen2learn

Best CPU/GPU

$
0
0
What CPU or GPU would perform the best I have some serious password recovery needs. I have been budgeted $1000 for the pentest on our network and will be spending it all on a CPU or GPU. Recommendations?

looping problem

$
0
0
hi guys,

been getting this problem with one of my rigs

watching the log and this happens. it seems as though its working, but the logs start duplicating like its stuck in a loop. first 4 rows are ok.


620021505151964/621931129772220] Uploading 0 b...Cracked 0
620056020300764/621931129772220] Uploading 0 b...Cracked 0
620091084682204/621931129772220] Uploading 0 b...Cracked 0
620126149063644/621931129772220] Uploading 0 b...Cracked 0
620160752071644/621931129772220] Uploading 0 b...Cracked 0
620160752071644/621931129772220] Uploading 0 b...Cracked 0
620160752071644/621931129772220] Uploading 0 b...Cracked 0
620160752071644/621931129772220] Uploading 0 b...Cracked 0
620160752071644/621931129772220] Uploading 0 b...Cracked 0
620160752071644/621931129772220] Uploading 0 b...Cracked 0
620160752071644/621931129772220] Uploading 0 b...Cracked 0
620160752071644/621931129772220] Uploading 0 b...Cracked 0
620160752071644/621931129772220] Uploading 0 b...Cracked 0
620160752071644/621931129772220] Uploading 0 b...Cracked 0
620160752071644/621931129772220] Uploading 0 b...Cracked 0
620160752071644/621931129772220] Uploading 0 b...Cracked 0

oclHashcat v1.30 on AMD no Status Screen, etc..

$
0
0
it running fine I can see cracked hash in output.txt but when I press the folllowing

Code:
[s]tatus [p]ause [r]esume [b]ypass [q]uit

no output text in the screen

Graphic Chipset: AMD Radeon R7 200 Series / AMD Radeon™ HD 7700 Series
Driver: AMD Catalyst 14.7 RC3 (14.200.1004.0 August 11)
OS: Windows 7 x64

hope it fixed soon and thank you.

Massive help

$
0
0
First of all, I'm sorry if I'm not post this where should be.

I'm totally ignorant about this ( Hashcat ), I watch some tutorials but it's all so confusing and I can not handle it. I manage solid in Kali linux and aircrack-ng but here even though tutorials that I seen I can not do anything in Hashcat.

So please if someone skillful user have some time to explain in detail some of the things where I'm wrong.

I want to crack password on my router that have WPA2 password with power of my GPU. I capture a handshake using Kali linux (airodump-ng), and convert it on this site, also create world list in Kali linux using crunch.

I barely managed to find a way to run Hashcat and to enter into settings.
Here are steps what I do :

1. Download HashcatGUI_042.zip from http://www.hashkiller.co.uk/
2. Extract in folder
3. Download 0.43b1 Update App.HashcatGUI.rar - v0.43b1 and extract in folder where is HashcatGUI_042 ( copy and replaced file )
4. Download hashcat v0.47 from here : http://hashcat.net/hashcat/ also extract it in folder where is HashcatGUI_042
5. Download oclHashcat for AMD v1.30 from here : http://hashcat.net/oclhashcat/ and also extract it in folder where is HashcatGUI_042

I have :
dotNET Framework: v4.5
Windows Ultimate 64 bit
GPU : Sapphire HD 5870 1GB GDDR5 256 bit

Then I run App.HashcatGUI and enter the program.
I go to tab oclHashcat and in loaction Hash file I put file that I captured in cali linux and convert it on this site using : https://hashcat.net/cap2hccap/
On hash type I choose WPA/WPA2.
On binary I specify the path : C:\Users\PC\Desktop\HASHCAT\oclHashcat-1.30\oclHashcat64.exe
In Worldlists & Markov I chosse and add my word list that I created in Kali linux (crunch).

All other options are by default, I did not touch anything.
Then I press I'm a hashkiller, on screen appear that I must accept some terms wit YES, I did that and then my graphic card began to be heated, it came to about 70+ degrees and then black screen in full screen for about 5-6 second, then recoverd and I see the error : Display driver AMD driver stopped responding and has successfully recovered. Then I exit everything.

I also updated AMD Catalyst to latest version ( BETA ) because I read somewhere that it should be.

So please if someone can help me where I was in wrong, because I do not want to damage my graphic card. I'm do this on my desktop PC and while this is ON, I do not need to use my PC for other things so my graphic card can run in max, as long as there is no opportunities that card can be damaged.

Thanks in advance.

Passwords14 - Presentation slides

how to get cudaHashcat going on Ubuntu 14.04 on Amazon GPU instance?

$
0
0
Can anyone tell me how to get cudahashcat running on the Amazon cloud?

I tried it on an Unbuntu 14.04 version, but I couldn't make the CUDA drivers work. I followed this tutorial:

http://askubuntu.com/questions/451672/in...untu-14-04

Amazon has Ubuntu 14.04 and RHEL 7 (there is no 12.04).

Please help how to get cudahashcat running on 14.04 or RHEL 7?

thanks

Facebook

$
0
0
if i forgot the password to a facebook account would this work? also a winrar archive that's been locked?

Not Cracking Passwords With Symbol Followed by Uppercase

$
0
0
Hello! I'm new to the forum and HashCat. For a cybersecurity course at school we were asked to create and crack hashes to certain passwords. However, I noticed that oclHashcat is not cracking hashes (in md5 and sha1 for sure) with symbols followed by uppercase letters, numbers, or other symbols. Also, it did not crack anything with digits before a symbol. When I noticed this, I was trying different small passwords: $A, *A, *3, a*A, and a*a (I believe these were the combos I tried) all did not crack successfully. However, $a and *a worked fine. I used online MD5 and sha1 hash generators.
Is this a known issue, or am I just doing something wrong? The line I passed was
oclHashcat64.exe -m 100 -a 3 -1 ?a --workload-profile=3 -o Cracked.txt test.txt
Thanks for any feedback!

oclHashcat for AMD v1.30 slow with "mask"

$
0
0
Hi.

In case you run a brute force with mask, speed decreases.
oclHashcat32.exe -m 0 -a 3 8fa1c84f6XXXX38ccXXXXf04274a0c52 ?a?a?a?a?a?a?a?a?a?a?a?a
Speed.GPU.#1...: 1108.5 MH/s

oclHashcat32.exe -m 0 -a 3 8fa1c84f6XXXX38ccXXXXf04274a0c52 ?a?a?a?a?a?a?a?akeys
Speed.GPU.#1...: 992.8 MH/s

oclHashcat32.exe -m 0 -a 3 8fa1c84f6XXXX38ccXXXXf04274a0c52 keys?a?a?a?a?a?a?a?a
Speed.GPU.#1...: 10220.0 kH/s



Why does my search mask keys?a?a?a?a?a?a?a?a well as speed decreases?
Thank you for your help.
================
E6600 + ATI5670

NV CUDA 6.5 update

$
0
0
Hey Guys,

just wanted to inform you about a funny new message that the NVCC spits out after updateing to CUDA 6.5:

Quote:nvcc warning : The 'compute_11', 'compute_12', 'compute_13', 'sm_11', 'sm_12', and 'sm_13' architectures are deprecated, and may be removed in a future release.

That means NVidia will drop CUDA support for (example) the old GTX series like my gtx285. They will no longer be supported in a future CUDA versions.

Actually it is a lot of GPU's that are using the sm_1* model. See here to find out which SM_* version is yours: http://developer.nvidia.com/cuda-gpus

--
atom

AMD Radeon R290 - 14.4 Unsupported Driver?

$
0
0
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\root>oclhashcat64.exe -b
oclHashcat v1.30 starting in benchmark-mode...

WARN: ADL_Overdrive5_FanSpeedInfo_Get(): -5

Device #1: Hawaii, 3072MB, 947Mhz, 40MCU

STOP! Unsupported or incorrect installed GPU driver detected!

You are STRONGLY encouraged to use the official supported GPU driver for good reasons

See oclHashcat's homepage for official supported GPU drivers

Also see: http://hashcat.net/wiki/doku.php?id=upgrading_amd_drivers_how_to

You can use --force to override this but do not post error reports if you do so

C:\Users\root>



Hey guys, Hope this isn't too much of a 'newb' post.

GPU is AMD Radeon R290, driver is 14.4

Can anyone help with this? Do I need to downgrade to 13.1 drivers?

I'm currently just running a bruteforce with "--force" and seems to be working fine, however, temp is not displayed for gpu which worries me...


Thanks

Just info seeking/curiosity. The SL3 Story?

$
0
0
Long time reader, 1st time poster.

So I was doing some WPA speed testing as I finally got Linux working on my new laptop. The reason I'm a long time reader and only now posting is because I've always been able to work things out myself. Taking time to research is better than being spoon-fed in my opinion. Even if the research will take up lots of my time, I'll still at least be learning something new.

To clarify, I don't need SL3 support. I would never buy a phone that I couldn't do what I wanted with. I'm mainly looking for more information. So please don't kill (ban) the cat for curiosity or personal opinion lol.

As I understand it based on the little available:

• Manufacturers dreamt up yet another way to shit on the user and made Simlock 3. Something apparently harder for the user reclaim their freedom and break than previous methods.

• Then someone, somewhere would have found GPU accelerated brute forcing to be a viable method of breaking this atrocity.

• Then oclHashcat had it implemented.

• Then, it seems, it got very heated. Apparently there was an influx of noobs. Along with an exploitation of those noobs by someone who passed oclHashcat off as their own for money.

• Along with that unlocking services started popping up. People began to set up dedicated SL3 cracking servers. Presumably servers with a fair amount of GPU's for parallel cracking. Obviously because the GPU's from then could take up to 9 days to crack SL3. (I looked at ATI GPU's from around 2011 on http://golubev.com/gpuest.htm) And again, they charged money for this.

• Things escalated with a torrent of hatred, immaturity and flaming on the forums. And at about the same time, some versions oclHashcat's timebomb were cracked allowing them to be used after the author wanted those versions discontinued. Which better suited those running the dedicated cracking servers as it would obviously allow them to keep the software instead of being forced to upgrade.
However, those running these servers still had to pay for the use of oclHashcat as many were ignorant to the software they were running. This, along with the huge influx of noobs and the cracking of the timebombs apparently enraged atom. So he dropped support for Simlock 3 in future versions. Starting a heated flame war on the thread where he announced it (http://hashcat.net/forum/thread-1887.html).

---

I've never withheld my opinion for fear of reprisal before and I'm not about to start now. I just hope this will be seen as a valid, harmless, opinion. And not needlessly expunged because it conflicts with someone else's opinion or because the topic is simply disliked. No one need read any of this thread if they don’t want to.

Based on the information so far. This entire situation is just awful. Manufacturers really have fucked over the end user once again. It was OK though. Those who wanted to have the freedom to use their phone wherever they damned well felt like it had a method of doing so. Assuming they had decent hardware and could read. Even if it took a month to crack many would still prefer that to forking out cash just to have their operator tell them "Yes, you can now leave our evil grasp and use your phone where you like". Personally, even if it took a year and was 10 times more expensive in electricity alone. I myself would still do it if a manufacturer subjected me to SL3! But for many, it was obviously far cheaper.

There seems to be a lot of defence around the dropping of SL3. I can only presume, and hope, that this is only because there is such a disdain for noobs here. However, it's a terrible move. All it does is play right into the hands of arseholes who subvert the freedom of those poorer than they are. The best thing would of course be for Sim locking and all the rest of that shite like DRM to die a horrible and decisive death. But that wont happen.

When researching what to say. I was unable to find an alternative to hashcat for SL3 unlocking. Admittedly because there was so many links wanting me to buy an unlocking service. But still. If I had a hard time then what chance does someone less tech-savvy than me have? That one option that could have been there, is now mostly gone. To let a disdain for noobs and the actions of a few greedy fuckers grant a free pass to the strangle of mobile users freedoms is a terrible, terrible action. I don't need SL3 cracking. But unfortunately, as long as there is greedy corporations, many do. So if the move was to try and stop greed in general. It has horribly backfired. If it was more against greed from those selling oclHashcat exclusively, you have only slowed them down. But at the expense of allowing the far more subversive and widespread greed of those who impose SL3 to run rampant.

---

Anyway. Any further information would be greatly appreciated.
And I strongly encourage nitpicking. As there seems to be little information on this subject. Grammar Nazis are welcome too lol

Last but certainly not least. A huge shout out to atom and all who help in the development of all hashcats! By far my favourite hash crackers!

--restore Error

$
0
0
I really do hate asking newb questions, but I did search and could not find how to properly use the --restore option. Can someone let me know what I am doing wrong, and also where I could have looked to find out how to do this so that I don't have to bug the experts here again.


Code:
C:\Users\root>oclhashcat64.exe --restore


ERROR: restore file 'oclHashcat.restore': No such file or directory


So far you guys have been really responsive and helpful on other questions I had, thanks.
Viewing all 8099 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>