From 0d31ee3b53a1981437f5049f3c860d6e93234ed6 Mon Sep 17 00:00:00 2001
From: jsteube <jens.steube@gmail.com>
Date: Sat, 10 Dec 2016 18:12:03 +0100
Subject: [PATCH] Alternative --progress-only in case of multiple salts
 cracking

---
 src/opencl.c | 10 ++--------
 1 file changed, 2 insertions(+), 8 deletions(-)

diff --git a/src/opencl.c b/src/opencl.c
index 6d9c053a1..9411b36b4 100644
--- a/src/opencl.c
+++ b/src/opencl.c
@@ -2006,16 +2006,10 @@ int run_cracker (hashcat_ctx_t *hashcat_ctx, hc_device_param_t *device_param, co
     {
       const double m = (double) innerloop_cnt / innerloop_step;
 
-      device_param->outerloop_msec += device_param->speed_msec[0] * m;
+      device_param->outerloop_msec += device_param->speed_msec[0] * m * hashes->salts_cnt;
     }
-    else
-    {
-      // if this is a --progress-only run, we do not want to break
-      // because we need to sum up all salts
-      // but for a --speed-only or benchmark run this isn't wanted
 
-      if (user_options->speed_only == true) break;
-    }
+    if (user_options->speed_only == true) break;
 
     //status screen makes use of this, can't reset here
     //device_param->innerloop_pos  = 0;