Hey fromdusktillpwn,
thank you again for this amazing troubleshooting and testing. We appreciate this very much, because we know this can be kinda tedious to test all the commits and find the right one (and always have to make sure that you are testing correctly, with make clean etc)... This is such a great find. Thank you very much!
I've explained your discoveries of course also to atom (main developer of hashcat) and we are currently testing/debating if we can revert this change without any significant disadvantages (other problems or significant speed losses with other setups/GPUs and or problems with macOS/linux drivers etc).
To make the "best" decision it would also be very helpful if we knew if this change would fix also the problem of the original reporter "slawson" because s/he stated that "I have tried Hashcat 5.1, 5.0, & 4.2.1" in the first post of this thread (https://hashcat.net/forum/thread-8605-po...l#pid45765 )... which would be kinda different (or even contradictory) to the discovery that we made here: "only" beta/git versions after 14th of April are affected.
I think it would make sense to try to get an answer from slawson too, but if we do not find any regression with the reverted patch, we should definitely revert this change.
Thank you again !
we just updated the source code to make the changes that fromdusktillpwn tested (https://github.com/hashcat/hashcat/commi...da98eb2443) that should "fix" the problem. Please test the beta version from https://hashcat.net/beta and report back. any feedback could help. thanks
thank you again for this amazing troubleshooting and testing. We appreciate this very much, because we know this can be kinda tedious to test all the commits and find the right one (and always have to make sure that you are testing correctly, with make clean etc)... This is such a great find. Thank you very much!
I've explained your discoveries of course also to atom (main developer of hashcat) and we are currently testing/debating if we can revert this change without any significant disadvantages (other problems or significant speed losses with other setups/GPUs and or problems with macOS/linux drivers etc).
To make the "best" decision it would also be very helpful if we knew if this change would fix also the problem of the original reporter "slawson" because s/he stated that "I have tried Hashcat 5.1, 5.0, & 4.2.1" in the first post of this thread (https://hashcat.net/forum/thread-8605-po...l#pid45765 )... which would be kinda different (or even contradictory) to the discovery that we made here: "only" beta/git versions after 14th of April are affected.
I think it would make sense to try to get an answer from slawson too, but if we do not find any regression with the reverted patch, we should definitely revert this change.
Thank you again !
we just updated the source code to make the changes that fromdusktillpwn tested (https://github.com/hashcat/hashcat/commi...da98eb2443) that should "fix" the problem. Please test the beta version from https://hashcat.net/beta and report back. any feedback could help. thanks