From 7a03e6fbf48cb700a14c7ffee07bb6ffe0532171 Mon Sep 17 00:00:00 2001 From: Gill-Singh-A Date: Thu, 11 Apr 2024 02:08:09 +0530 Subject: [PATCH] Replaced Mark Down table with Image --- _posts/2024-04-10-password-cracking.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/_posts/2024-04-10-password-cracking.md b/_posts/2024-04-10-password-cracking.md index c73794c..e9d0c55 100644 --- a/_posts/2024-04-10-password-cracking.md +++ b/_posts/2024-04-10-password-cracking.md @@ -232,13 +232,7 @@ That's why you should keep a complex password that uses all of the following Cha * Special Characters Below is the table that shows how much time it would take to crack a hash with certain conditions -| Length | Numbers | Lowercase ASCII Characters | Lowercase ASCII Characters + Numbers | Lowercase ASCII Characters + Uppercase ASCII Characters | Lowercase ASCII Characters + Uppercase ASCII Characters + Numbers | Lowercase ASCII Characters + Uppercase ASCII Characters + Numbers + Special Characters | -|--------|------------|----------------------------|--------------------------------------|---------------------------------------------------------|-------------------------------------------------------------------|----------------------------------------------------------------------------------------| -| 8 | 1 sec | 34.8 min | 7.83 hours | 6.18 days | 25.27 days | 22.84 years | -| 9 | 10 sec | 15.08 hours | 8.57 days | 162.12 days | 1.8 years | 57.1 years | -| 10 | 1.67 min | 16.28 days | 223.03 days | 11.51 years | 47.46 years | 1497.55 years | -| 11 | 16.67 min | 281.93 days | 10.56 years | 199.92 years | 820.928 years | 25843.264 years | -| 12 | 2.78 hours | 9.515 years | 130.341 years | 2463.897 years | 1023042.47 years | 6133565802.2 years | +{% include lazyload.html image_src="/images/password_cracking_time.webp" %}
This table is just an example and not indicative of the actual time taken for hash cracking. A good understanding of multithreading and CUDA programming can even accelerate this by a factor. ## Success Rate of Hash Cracking Based on the calculations shown in the previous section, we're convinced that Hash Cracking is difficult. So, one question arises: why does an attacker attempt to crack a hash when it would take such a long time? When an attacker gains access to a list of Hash Protected Passwords (from a Compromised Database or any other method), they run a dictionary attack instead of brute force. Because the main aim here is to crack as many passwords as possible instead of targeting a specific one, the attacker would obtain passwords that were present in the wordlist. In such scenarios, the success rate of Hash Cracking is higher than expected.