So I am coveting a rig like this now: https://www.shellntel.com/blog/2017/2/8/how-to-build-a-8-gpu-password-cracke...
4 card GTX 1080 ti set ups are doing NTLM and NetNTLM in the 200 and 100 GigaHashes/s range, respectively... this rig would double that.
For reference, our 3 card GTX 980s do 64 GH/s for NTLM and 35 GH/s for NetNTLMv1 If we built this rig, we'd blow our whole upgrades budget on it and would have to live with our elderly VMware server down here for another round.
I vote to build the bigger password cracking rig with the budget. :-)
On Thu, Aug 17, 2017 at 10:43 AM -0600, "Goble, Andrew" <Goble@dixie.edumailto:Goble@dixie.edu> wrote:
So I am coveting a rig like this now: https://www.shellntel.com/blog/2017/2/8/how-to-build-a-8-gpu-password-cracke...
4 card GTX 1080 ti set ups are doing NTLM and NetNTLM in the 200 and 100 GigaHashes/s range, respectively... this rig would double that.
For reference, our 3 card GTX 980s do 64 GH/s for NTLM and 35 GH/s for NetNTLMv1 If we built this rig, we'd blow our whole upgrades budget on it and would have to live with our elderly VMware server down here for another round.
Whatever you think is best...
On Thu, Aug 17, 2017 at 11:03 AM, Jon Barclay Jon.Barclay@uvu.edu wrote:
I vote to build the bigger password cracking rig with the budget. :-)
On Thu, Aug 17, 2017 at 10:43 AM -0600, "Goble, Andrew" Goble@dixie.edu wrote:
So I am coveting a rig like this now: https://www.shellntel.com/
blog/2017/2/8/how-to-build-a-8-gpu-password-cracker
4 card GTX 1080 ti set ups are doing NTLM and NetNTLM in the 200 and 100 GigaHashes/s range, respectively... this rig would double that.
For reference, our 3 card GTX 980s do 64 GH/s for NTLM and 35 GH/s for NetNTLMv1 If we built this rig, we'd blow our whole upgrades budget on it and would have to live with our elderly VMware server down here for another round.
USHE-assess mailing list USHE-assess@lists.dixie.edu http://lists.dixie.edu/cgi-bin/mailman/listinfo/ushe-assess
I was originally in the: Let's do the responsible thing and upgraded the oldest hardware first camp. Then I thought about it and realized that if that box dies, we can run those vm's on the virtualization environment of any institution (or the USHE gear). Thinking more, I realized that cracking hashes faster would make things a little faster/smoother while on-site for audits. Plus having multiple spots to be able to crack hashes is handy too.
Think the cracking rig is the way to go as long as we are comfortable running basegate workloads from one of the institutions in the event of hardware failure.
Matt
Matt Lorimer IT - Secure Systems Engineering Utah State University 435-797-4242 Matt.Lorimer@usu.edu
On 08/18/2017 09:44 AM, Mark Walton wrote:
Whatever you think is best...
On Thu, Aug 17, 2017 at 11:03 AM, Jon Barclay <Jon.Barclay@uvu.edu mailto:Jon.Barclay@uvu.edu> wrote:
I vote to build the bigger password cracking rig with the budget. :-) On Thu, Aug 17, 2017 at 10:43 AM -0600, "Goble, Andrew" <Goble@dixie.edu <mailto:Goble@dixie.edu>> wrote: So I am coveting a rig like this now: https://www.shellntel.com/blog/2017/2/8/how-to-build-a-8-gpu-password-cracker <https://www.shellntel.com/blog/2017/2/8/how-to-build-a-8-gpu-password-cracker> 4 card GTX 1080 ti set ups are doing NTLM and NetNTLM in the 200 and 100 GigaHashes/s range, respectively... this rig would double that. For reference, our 3 card GTX 980s do 64 GH/s for NTLM and 35 GH/s for NetNTLMv1 If we built this rig, we'd blow our whole upgrades budget on it and would have to live with our elderly VMware server down here for another round. _______________________________________________ USHE-assess mailing list USHE-assess@lists.dixie.edu <mailto:USHE-assess@lists.dixie.edu> http://lists.dixie.edu/cgi-bin/mailman/listinfo/ushe-assess <http://lists.dixie.edu/cgi-bin/mailman/listinfo/ushe-assess>
USHE-assess mailing list USHE-assess@lists.dixie.edu http://lists.dixie.edu/cgi-bin/mailman/listinfo/ushe-assess
Given what we are doing, I've always been just a little more comfortable with the hardware hypervisor separation provided by a standalone box. That said, yes, we could run it in our farm no problem.
I see no signs of imminent hardware failure and I could stock a spare drive or two for the existing box, its just 7 or 8 years old and there are no guarantees.
On Fri, 2017-08-18 at 11:41 -0600, Matt Lorimer wrote:
I was originally in the: Let's do the responsible thing and upgraded the oldest hardware first camp. Then I thought about it and realized that if that box dies, we can run those vm's on the virtualization environment of any institution (or the USHE gear). Thinking more, I realized that cracking hashes faster would make things a little faster/smoother while on-site for audits. Plus having multiple spots to be able to crack hashes is handy too.
Think the cracking rig is the way to go as long as we are comfortable running basegate workloads from one of the institutions in the event of hardware failure.
Matt
On 08/18/2017 09:44 AM, Mark Walton wrote:
Whatever you think is best...
On Thu, Aug 17, 2017 at 11:03 AM, Jon Barclay Jon.Barclay@uvu.edu wrote:
I vote to build the bigger password cracking rig with the budget. :-)
On Thu, Aug 17, 2017 at 10:43 AM -0600, "Goble, Andrew" <Goble@di xie.edu> wrote:
So I am coveting a rig like this now: https://www.shellntel.com /blog/2017/2/8/how-to-build-a-8-gpu-password-cracker
4 card GTX 1080 ti set ups are doing NTLM and NetNTLM in the 200 and 100 GigaHashes/s range, respectively... this rig would double that.
For reference, our 3 card GTX 980s do 64 GH/s for NTLM and 35 GH/s for NetNTLMv1 If we built this rig, we'd blow our whole upgrades budget on it and would have to live with our elderly VMware server down here for another round.
USHE-assess mailing list USHE-assess@lists.dixie.edu http://lists.dixie.edu/cgi-bin/mailman/listinfo/ushe-assess
USHE-assess mailing list USHE-assess@lists.dixie.edu http://lists.dixie.edu/cgi-bin/mailman/listinfo/ushe-assess
USHE-assess mailing list USHE-assess@lists.dixie.edu http://lists.dixie.edu/cgi-bin/mailman/listinfo/ushe-assess
participants (4)
-
Goble, Andrew -
Jon Barclay -
Mark Walton -
Matt Lorimer