10-24-2020, 09:49 AM
In the hashcat FAQ it says automatically stopping in case of an overheat is a bad idea and is therefore unsupported. I was under the impression that this was what the "temperature abort trigger" was all about, but I'm on a MacBook, so it was kind of irrelevant to me anyway. (I'm aware of the issues with shared heatsinks on laptops, but this is what I'm stuck with for now... I run reduced workload and keep an eye on the temp)
So I was wondering:
1) If someone could clarify why this is a bad idea and what the distinction is between the unsupported bad idea and whatever the temperature abort trigger is really doing
2) If it would be a welcome and not stupid contribution for me to add temperature monitoring for macOS to hashcat for the benefit of others in my situation
Thanks for your time and for maintaining a wonderful project!
So I was wondering:
1) If someone could clarify why this is a bad idea and what the distinction is between the unsupported bad idea and whatever the temperature abort trigger is really doing
2) If it would be a welcome and not stupid contribution for me to add temperature monitoring for macOS to hashcat for the benefit of others in my situation
Thanks for your time and for maintaining a wonderful project!