<![CDATA[hashcat Forum - Organisation and Events]]> https://hashcat.net/forum/ Sat, 04 Apr 2026 16:04:58 +0000 MyBB <![CDATA[DISCORD Server either Crashed or Kicked Me OUT!]]> https://hashcat.net/forum/thread-11235.html Fri, 06 Jan 2023 14:36:30 +0000 shoeboxlogic]]> https://hashcat.net/forum/thread-11235.html
I went into the Discord server, and asked in a few rooms if anyones here, and also posed my main query in the help section, then I was just ejected.  And unable to log back in.  Perhaps the servers crashed, I hope thats all.]]>
I went into the Discord server, and asked in a few rooms if anyones here, and also posed my main query in the help section, then I was just ejected.  And unable to log back in.  Perhaps the servers crashed, I hope thats all.]]> <![CDATA[Shop for advertising]]> https://hashcat.net/forum/thread-10602.html Thu, 27 Jan 2022 19:15:30 +0000 Sondero]]> https://hashcat.net/forum/thread-10602.html is there an official shop for Hoodies / stickers / ... ?]]> is there an official shop for Hoodies / stickers / ... ?]]> <![CDATA[Number of newlines is increasing when editing forum posts]]> https://hashcat.net/forum/thread-10547.html Tue, 21 Dec 2021 20:39:39 +0000 meow]]> https://hashcat.net/forum/thread-10547.html
Is it just me, or are you guys also having a problem with newlines when posting new posts or editing existing posts? The problem is that the more times I edit a post to make changes or to add additional bits of information, the number of new lines increases by one newline for each newline.

Initial post:


Quote:Haxx0r ipsum headers d00dz vi infinite loop semaphore it's a feature ifdef ssh fatal strlen packet sniffer public foad bin. Data void var todo giga sql highjack cache bypass new blob injection ack baz function salt char script kiddies int class Donald Knuth. Wabbit wombat machine code rm -rf null echo *.* epoch.

Cat eof less endif injection infinite loop epoch suitably small values. Overflow crack tcp perl for headers *.* default wombat bytes giga wabbit syn worm. New packet gc ban foad fork thread socket chown over clock I'm sorry Dave, I'm afraid I can't do that ddos cache.


After editing the post once:


Quote:Haxx0r ipsum headers d00dz vi infinite loop semaphore it's a feature ifdef ssh fatal strlen packet sniffer public foad bin. Data void var todo giga sql highjack cache bypass new blob injection ack baz function salt char script kiddies int class Donald Knuth. Wabbit wombat machine code rm -rf null echo *.* epoch.


Cat eof less endif injection infinite loop epoch suitably small values. Overflow crack tcp perl for headers *.* default wombat bytes giga wabbit syn worm. New packet gc ban foad fork thread socket chown over clock I'm sorry Dave, I'm afraid I can't do that ddos cache.


After editing the post twice:


Quote:Haxx0r ipsum headers d00dz vi infinite loop semaphore it's a feature ifdef ssh fatal strlen packet sniffer public foad bin. Data void var todo giga sql highjack cache bypass new blob injection ack baz function salt char script kiddies int class Donald Knuth. Wabbit wombat machine code rm -rf null echo *.* epoch.




Cat eof less endif injection infinite loop epoch suitably small values. Overflow crack tcp perl for headers *.* default wombat bytes giga wabbit syn worm. New packet gc ban foad fork thread socket chown over clock I'm sorry Dave, I'm afraid I can't do that ddos cache.


It's quite a process to clean up all the goo between paragraphs. I click to edit in full editor, and then starting from the first line of the second paragraph, I use Shift and up arrow key to select upwards, ensuring I including the last line of the first paragraph to encompass all hidden characters, then whilst holding down Shift key, I press End key to deselect the good bit of the last line in first paragraph, and lastly I press Delete key to ensure I delete all characters to the right. Then I press Enter two times to get back to proper spacing between paragraphs, just one line worth of spacing.

Then after all that trouble, it all returns again if I edit the post once more, and this time the problem has grown on each newline by one additional newline, so it's growing. Sometimes, somehow, I manage to stop the spread and I don't know how or why, sometimes I'm just lucky I guess. It's like trying to contain a virus, and it just keeps on growing.

I thought you should know about it. I'm sorry if this is not the right place to post about it, or if I'm the only one having this issue. My OCD immediately kicks in when I see this sort of thing.]]>
Is it just me, or are you guys also having a problem with newlines when posting new posts or editing existing posts? The problem is that the more times I edit a post to make changes or to add additional bits of information, the number of new lines increases by one newline for each newline.

Initial post:


Quote:Haxx0r ipsum headers d00dz vi infinite loop semaphore it's a feature ifdef ssh fatal strlen packet sniffer public foad bin. Data void var todo giga sql highjack cache bypass new blob injection ack baz function salt char script kiddies int class Donald Knuth. Wabbit wombat machine code rm -rf null echo *.* epoch.

Cat eof less endif injection infinite loop epoch suitably small values. Overflow crack tcp perl for headers *.* default wombat bytes giga wabbit syn worm. New packet gc ban foad fork thread socket chown over clock I'm sorry Dave, I'm afraid I can't do that ddos cache.


After editing the post once:


Quote:Haxx0r ipsum headers d00dz vi infinite loop semaphore it's a feature ifdef ssh fatal strlen packet sniffer public foad bin. Data void var todo giga sql highjack cache bypass new blob injection ack baz function salt char script kiddies int class Donald Knuth. Wabbit wombat machine code rm -rf null echo *.* epoch.


Cat eof less endif injection infinite loop epoch suitably small values. Overflow crack tcp perl for headers *.* default wombat bytes giga wabbit syn worm. New packet gc ban foad fork thread socket chown over clock I'm sorry Dave, I'm afraid I can't do that ddos cache.


After editing the post twice:


Quote:Haxx0r ipsum headers d00dz vi infinite loop semaphore it's a feature ifdef ssh fatal strlen packet sniffer public foad bin. Data void var todo giga sql highjack cache bypass new blob injection ack baz function salt char script kiddies int class Donald Knuth. Wabbit wombat machine code rm -rf null echo *.* epoch.




Cat eof less endif injection infinite loop epoch suitably small values. Overflow crack tcp perl for headers *.* default wombat bytes giga wabbit syn worm. New packet gc ban foad fork thread socket chown over clock I'm sorry Dave, I'm afraid I can't do that ddos cache.


It's quite a process to clean up all the goo between paragraphs. I click to edit in full editor, and then starting from the first line of the second paragraph, I use Shift and up arrow key to select upwards, ensuring I including the last line of the first paragraph to encompass all hidden characters, then whilst holding down Shift key, I press End key to deselect the good bit of the last line in first paragraph, and lastly I press Delete key to ensure I delete all characters to the right. Then I press Enter two times to get back to proper spacing between paragraphs, just one line worth of spacing.

Then after all that trouble, it all returns again if I edit the post once more, and this time the problem has grown on each newline by one additional newline, so it's growing. Sometimes, somehow, I manage to stop the spread and I don't know how or why, sometimes I'm just lucky I guess. It's like trying to contain a virus, and it just keeps on growing.

I thought you should know about it. I'm sorry if this is not the right place to post about it, or if I'm the only one having this issue. My OCD immediately kicks in when I see this sort of thing.]]> <![CDATA[What's the answer to "what is the current stable version of hashcat"?]]> https://hashcat.net/forum/thread-10535.html Sat, 18 Dec 2021 13:28:25 +0000 meow]]> https://hashcat.net/forum/thread-10535.html
"What is the current stable version of hashcat?"

According to Hashcat announcements forum it's 6.2.0:
https://hashcat.net/forum/forum-16.html

According to Hashcat Wikipedia article it's 6.2.4:
https://en.wikipedia.org/wiki/Hashcat

According to Hashcat download page it's 6.2.5:
https://hashcat.net/hashcat/


This question comes up when signing up for an account on these forums. What am I supposed to type in as the answer?

I tried "6.2.5", "6.2.4" and I just tried "6.2.0". I even tried "v6.2.5", "hashcat v6.2.5" as it's typed out on the download page, and I even went as far as pasting in MD5 hash values of these strings. None of which worked.

If you can't share this secret publicly, can someone send me a PM with the correct answer to the question? Alternatively, can you tell me if the full version number is expected, and if it contains any letters?

Playfully yours,
meow
🐈]]>
"What is the current stable version of hashcat?"

According to Hashcat announcements forum it's 6.2.0:
https://hashcat.net/forum/forum-16.html

According to Hashcat Wikipedia article it's 6.2.4:
https://en.wikipedia.org/wiki/Hashcat

According to Hashcat download page it's 6.2.5:
https://hashcat.net/hashcat/


This question comes up when signing up for an account on these forums. What am I supposed to type in as the answer?

I tried "6.2.5", "6.2.4" and I just tried "6.2.0". I even tried "v6.2.5", "hashcat v6.2.5" as it's typed out on the download page, and I even went as far as pasting in MD5 hash values of these strings. None of which worked.

If you can't share this secret publicly, can someone send me a PM with the correct answer to the question? Alternatively, can you tell me if the full version number is expected, and if it contains any letters?

Playfully yours,
meow
🐈]]> <![CDATA[#hashcat is migrating its IRC presence to Libera Chat]]> https://hashcat.net/forum/thread-10134.html Wed, 26 May 2021 17:56:16 +0000 atom]]> https://hashcat.net/forum/thread-10134.html
The hashcat project has been present on Freenode for almost ten years, and throughout our tenure we have experienced only dedication, care, and professionalism from the network's volunteer staff. When they feel forced to resign and launch a new network, we follow to continue experiencing the same level of care and dedication. We thank Freenode for the many years of great service and collaboration.

All existing users of the #hashcat channel on Freenode are invited to join us in #hashcat on Libera Chat. Chatting will be disabled in #hashcat on Freenode and its presence will be maintained solely to point users to #hashcat on Libera Chat.

If you never tried IRC, take a look at https://libera.chat/]]>
The hashcat project has been present on Freenode for almost ten years, and throughout our tenure we have experienced only dedication, care, and professionalism from the network's volunteer staff. When they feel forced to resign and launch a new network, we follow to continue experiencing the same level of care and dedication. We thank Freenode for the many years of great service and collaboration.

All existing users of the #hashcat channel on Freenode are invited to join us in #hashcat on Libera Chat. Chatting will be disabled in #hashcat on Freenode and its presence will be maintained solely to point users to #hashcat on Libera Chat.

If you never tried IRC, take a look at https://libera.chat/]]> <![CDATA[Hash Olympics - A Hash Cracking Contest Without Good Hardware]]> https://hashcat.net/forum/thread-10115.html Tue, 18 May 2021 19:33:11 +0000 utkusen]]> https://hashcat.net/forum/thread-10115.html
We are organizing a hash cracking contest named "hash olympics" where participants can show their Hashcat skills without good hardware. I created this format so that poor students can learn and have fun with hash cracking. I posted a blog post about the contest format. Your feedback would be highly appreciated.

https://utkusen.com/blog/hash-olympics-h...ntest.html]]>
We are organizing a hash cracking contest named "hash olympics" where participants can show their Hashcat skills without good hardware. I created this format so that poor students can learn and have fun with hash cracking. I posted a blog post about the contest format. Your feedback would be highly appreciated.

https://utkusen.com/blog/hash-olympics-h...ntest.html]]> <![CDATA[Upcoming events]]> https://hashcat.net/forum/thread-9942.html Thu, 18 Mar 2021 18:22:33 +0000 ctrl]]> https://hashcat.net/forum/thread-9942.html <![CDATA[New ISP]]> https://hashcat.net/forum/thread-6647.html Sun, 18 Jun 2017 15:10:12 +0000 atom]]> https://hashcat.net/forum/thread-6647.html
It's possible some threads or posts have been lost during migration phase (~ 1 hour).

If something doesn't work - tell me please.]]>
It's possible some threads or posts have been lost during migration phase (~ 1 hour).

If something doesn't work - tell me please.]]> <![CDATA[Please vote]]> https://hashcat.net/forum/thread-6289.html Fri, 10 Feb 2017 17:39:53 +0000 atom]]> https://hashcat.net/forum/thread-6289.html
I can not guarantee the numbers, but after the change all modes will have the same speed.

The speed will be slower to what combinator-mode is doing right now and depend on the hash-mode.

For NTLM, only half the speed of combinator attack
For SHA256, almost the same speed of combinator attack

Note: This is for fast hashes (NTLM, MD5, VB, etc) only. Slow hashes speeds don't change.]]>
I can not guarantee the numbers, but after the change all modes will have the same speed.

The speed will be slower to what combinator-mode is doing right now and depend on the hash-mode.

For NTLM, only half the speed of combinator attack
For SHA256, almost the same speed of combinator attack

Note: This is for fast hashes (NTLM, MD5, VB, etc) only. Slow hashes speeds don't change.]]> <![CDATA[MTC3 The World Record Challenge]]> https://hashcat.net/forum/thread-5971.html Wed, 19 Oct 2016 22:52:00 +0000 iceman]]> https://hashcat.net/forum/thread-5971.html
Or anyone else of course.

AES, ECB,

http://scienceblogs.de/klausis-krypto-ko...challenge/]]>
Or anyone else of course.

AES, ECB,

http://scienceblogs.de/klausis-krypto-ko...challenge/]]> <![CDATA[HashKiller Contest July 2016 - Registration Open!]]> https://hashcat.net/forum/thread-5527.html Mon, 20 Jun 2016 09:59:07 +0000 blandyuk]]> https://hashcat.net/forum/thread-5527.html
Contest registration is now OPEN:

https://hashkiller.co.uk/contest/

Total hashes: 11,125,022
Total Points: 113,493,040

To register, you must be logged into the forum and be part of the team that is taking part as its your team name that is registered. You can manage who can submit their found passwords via your team system below.

To create a team, go to the Team List page below and click "Create Team":

https://forum.hashkiller.co.uk/team-list.aspx

Also, for the smaller teams who don't have any way of managing the lists, there will be "left" list downloads available.]]>
Contest registration is now OPEN:

https://hashkiller.co.uk/contest/

Total hashes: 11,125,022
Total Points: 113,493,040

To register, you must be logged into the forum and be part of the team that is taking part as its your team name that is registered. You can manage who can submit their found passwords via your team system below.

To create a team, go to the Team List page below and click "Create Team":

https://forum.hashkiller.co.uk/team-list.aspx

Also, for the smaller teams who don't have any way of managing the lists, there will be "left" list downloads available.]]> <![CDATA[hashcat and oclHashcat have gone open source]]> https://hashcat.net/forum/thread-4880.html Fri, 04 Dec 2015 16:02:35 +0000 atom]]> https://hashcat.net/forum/thread-4880.html
There have been so many discussions in the past about why Hashcat isn't open source, and I bet the same people will now ask the opposite: "Why are you going open source now?"" I will explain below, but for now, just take a minute to simply be happy about the fact (at least I hope you are!)

So, Why did I decide to go open source with the Hashcat project?

Actually, I am a big fan of open source software, and I've always held the idea of eventually going open source at some point in the future. The difficult questions were when would we be ready to do so, and when would be the best time to do it.

There are of course several additional reasons as well:

- A huge amount of hashcat/oclHashcat users are penetration testers or forensic scientists. They often have the special need of implementing their own GPU kernels. Not surprisingly, they frequently can't leak/include details about the algorithm, example hashes, or other crucial details about what should be implemented into a kernel due to restrictions placed upon them by their contract/NDA. Creating just an open interface to allow the user to easily add/modify algorithms would not be a very clever solution in this particular case, because performance is of course the thing hashcat/oclHashcat is most known for. I've already implemented most all of the widely-used generic hashing (and even some encryption) algorithms with GPU acceleration. Now they only need to be combined with each other to implement a new algorithm specific to the scheme used. When we would use an interface instead, these generic algorithms had to be reimplemented for each new scheme.

- There is a very important consideration that arises when you want to go open source: the license. My decision is to use the MIT license. This particular license allows an easy integration or packaging for the most common Linux distributions, for instance Ubuntu, but I've also planned to generate packages for The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) Linux which is very popular around penetration testers. The end goal is to make the installation and distribution of the hashcat project as easy as possible, most importantly for oclHashcat.

- After the switch to open source it will be much easier to integrate external libraries. Indeed, it was barely possible before due to license problems. A few crypto libraries have very restrictive licences, and some of them don't allow the integration of their code within binary files or only with very special prerequisites. At this point, hashcat/oclHashcat do not need any external libraries, but sometimes even just the parsing of the hash itself is very complicated and often even more challenging than the GPU kernel itself. GPG is a good example of this, it probably could be added easily if hashcat/oclHashcat were open source.

- Currently there is no native support for OSX. The main reason for this is that Apple does not support "offline" compiling of the kernel code. Technically, the missing piece is what AMD allows through CL_CONTEXT_OFFLINE_DEVICES_AMD in its OpenCL runtime. This would allow the compilation of GPU kernels for devices which are not currently attached to the development system. With an  open source project, you can easily compile the kernels using the Apple OpenCL Runtime "just in time", also known as JIT, and hence lift that restriction. This means that support for oclHashcat on OSX would be possible for the first time.

... and why now especially?

The ultimate reason to decide to go open source was the implementation of the bitsliced DES GPU kernels. To reach maximal efficiency and performance, the salt has to be embedded within the kernel at compile time. The salt itself however depends on the given hash input. This hash of course is only known at run time, but not at compile time. This implies that the kernel needs to be compiled at run time by the system of the user. This type of compilation, with the kernel adapting according to the salt/hash, is only possible if the source code is available. Bit slicing allows to reach a much higher cracking rate of DES-based algorithms (LM, Oracle, DEScrypt, RACF). DEScrypt, for instance, which is well known on Unix-like systems, can reach a performance gain of 300-400% with the bit slice technique. These huge optimizations will be shipped with the release of oclHashcat v2.00, which will be available right after the open source announcement.

... and for those who may think I'm going to leave the project:

No way I'd do that! I'll stay here, providing the same effort as before.

Enough of me now, let the sourcecodes talk: https://github.com/hashcat/

Or simply download the new hashcat v2.00 or oclHashcat v2.00 binaries as you know them from previous versions.]]>
There have been so many discussions in the past about why Hashcat isn't open source, and I bet the same people will now ask the opposite: "Why are you going open source now?"" I will explain below, but for now, just take a minute to simply be happy about the fact (at least I hope you are!)

So, Why did I decide to go open source with the Hashcat project?

Actually, I am a big fan of open source software, and I've always held the idea of eventually going open source at some point in the future. The difficult questions were when would we be ready to do so, and when would be the best time to do it.

There are of course several additional reasons as well:

- A huge amount of hashcat/oclHashcat users are penetration testers or forensic scientists. They often have the special need of implementing their own GPU kernels. Not surprisingly, they frequently can't leak/include details about the algorithm, example hashes, or other crucial details about what should be implemented into a kernel due to restrictions placed upon them by their contract/NDA. Creating just an open interface to allow the user to easily add/modify algorithms would not be a very clever solution in this particular case, because performance is of course the thing hashcat/oclHashcat is most known for. I've already implemented most all of the widely-used generic hashing (and even some encryption) algorithms with GPU acceleration. Now they only need to be combined with each other to implement a new algorithm specific to the scheme used. When we would use an interface instead, these generic algorithms had to be reimplemented for each new scheme.

- There is a very important consideration that arises when you want to go open source: the license. My decision is to use the MIT license. This particular license allows an easy integration or packaging for the most common Linux distributions, for instance Ubuntu, but I've also planned to generate packages for The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) Linux which is very popular around penetration testers. The end goal is to make the installation and distribution of the hashcat project as easy as possible, most importantly for oclHashcat.

- After the switch to open source it will be much easier to integrate external libraries. Indeed, it was barely possible before due to license problems. A few crypto libraries have very restrictive licences, and some of them don't allow the integration of their code within binary files or only with very special prerequisites. At this point, hashcat/oclHashcat do not need any external libraries, but sometimes even just the parsing of the hash itself is very complicated and often even more challenging than the GPU kernel itself. GPG is a good example of this, it probably could be added easily if hashcat/oclHashcat were open source.

- Currently there is no native support for OSX. The main reason for this is that Apple does not support "offline" compiling of the kernel code. Technically, the missing piece is what AMD allows through CL_CONTEXT_OFFLINE_DEVICES_AMD in its OpenCL runtime. This would allow the compilation of GPU kernels for devices which are not currently attached to the development system. With an  open source project, you can easily compile the kernels using the Apple OpenCL Runtime "just in time", also known as JIT, and hence lift that restriction. This means that support for oclHashcat on OSX would be possible for the first time.

... and why now especially?

The ultimate reason to decide to go open source was the implementation of the bitsliced DES GPU kernels. To reach maximal efficiency and performance, the salt has to be embedded within the kernel at compile time. The salt itself however depends on the given hash input. This hash of course is only known at run time, but not at compile time. This implies that the kernel needs to be compiled at run time by the system of the user. This type of compilation, with the kernel adapting according to the salt/hash, is only possible if the source code is available. Bit slicing allows to reach a much higher cracking rate of DES-based algorithms (LM, Oracle, DEScrypt, RACF). DEScrypt, for instance, which is well known on Unix-like systems, can reach a performance gain of 300-400% with the bit slice technique. These huge optimizations will be shipped with the release of oclHashcat v2.00, which will be available right after the open source announcement.

... and for those who may think I'm going to leave the project:

No way I'd do that! I'll stay here, providing the same effort as before.

Enough of me now, let the sourcecodes talk: https://github.com/hashcat/

Or simply download the new hashcat v2.00 or oclHashcat v2.00 binaries as you know them from previous versions.]]> <![CDATA[Another trophy in the Pocket! Win @ CMIYC contest 2015]]> https://hashcat.net/forum/thread-4595.html Mon, 10 Aug 2015 09:40:12 +0000 atom]]> https://hashcat.net/forum/thread-4595.html
There, just as a small note here: We won Crack Me If You Can 2015 @ defcon

http://contest-2015.korelogic.com/stats.html

Congrats to Team CynoSure Prime, they proofed they are a true "pro" team. Of course, congrats to Team InsidePro and Team john-users, too.

Also thanks to KoreLogic for organisation and an amazing contest. We all really loved it this year.]]>
There, just as a small note here: We won Crack Me If You Can 2015 @ defcon

http://contest-2015.korelogic.com/stats.html

Congrats to Team CynoSure Prime, they proofed they are a true "pro" team. Of course, congrats to Team InsidePro and Team john-users, too.

Also thanks to KoreLogic for organisation and an amazing contest. We all really loved it this year.]]> <![CDATA[CMIYC 2015]]> https://hashcat.net/forum/thread-4588.html Thu, 06 Aug 2015 01:54:30 +0000 mastercracker]]> https://hashcat.net/forum/thread-4588.html ]]> ]]> <![CDATA[Forum update]]> https://hashcat.net/forum/thread-4512.html Tue, 07 Jul 2015 20:00:27 +0000 atom]]> https://hashcat.net/forum/thread-4512.html
sadly we had to move from MyBB v1.6 to MyBB v1.8 because v1.6 was marked end-of-life by their developers. That means no security patches etc. I'll try to bring back the look 'n feel from v1.6 but I'm not a CSS expert so I can not guarantee any success. If anyone from you wants to help me with this please contact me.

--
atom]]>
sadly we had to move from MyBB v1.6 to MyBB v1.8 because v1.6 was marked end-of-life by their developers. That means no security patches etc. I'll try to bring back the look 'n feel from v1.6 but I'm not a CSS expert so I can not guarantee any success. If anyone from you wants to help me with this please contact me.

--
atom]]>