Author

Topic: Hacker going to demonstrate open source tool to crack Hashes with speed of 154 B (Read 1709 times)

full member
Activity: 196
Merit: 100
Web Dev, Db Admin, Computer Technician
legendary
Activity: 4326
Merit: 3041
Vile Vixen and Miss Bitcointalk 2021-2023
If we truly understood physics, there would be an anti-gravity vehicle in everyones backyard. Cheesy
According to Boyd Bushmen, retired senior engineer for Lockheed>Martin, there are 8 fundamental forces and we barely understand 5 of them.

However, the relationship between entropy and energy is one of the few things we do understand.
full member
Activity: 196
Merit: 100
Web Dev, Db Admin, Computer Technician
If we truly understood physics, there would be an anti-gravity vehicle in everyones backyard. Cheesy
According to Boyd Bushmen, retired senior engineer for Lockheed>Martin, there are 8 fundamental forces and we barely understand 5 of them.
legendary
Activity: 1904
Merit: 1002
Well, a distributed cracker is only limited by the size of the cluster, the larger the cluster the less billions of years it would take. An intelligently redesigned oclvanitygen could reduce those billions of years even more. Cheesy

The other limit is physics.
full member
Activity: 196
Merit: 100
Web Dev, Db Admin, Computer Technician
Well, a distributed cracker is only limited by the size of the cluster, the larger the cluster the less billions of years it would take. An intelligently redesigned oclvanitygen could reduce those billions of years even more. Cheesy

Edit:
Actual years rounded down to 1434 Quattuordecillion years for one core of a 5850. Now just need to figure out how many cores I will need... Cheesy
rjk
sr. member
Activity: 448
Merit: 250
1ngldh
Why, I can't put 8 or 9 characters into oclvanitygen and generate all possible addresses and their private keys?
Sure but it would take more energy than the Sun and several billions of years.
full member
Activity: 196
Merit: 100
Web Dev, Db Admin, Computer Technician
Why, I can't put 8 or 9 characters into oclvanitygen and generate all possible addresses and their private keys?
rjk
sr. member
Activity: 448
Merit: 250
1ngldh
I just thought of why this could be dangerous:

The distributed/cluster version of OCLvanitygen would be able to get the private key of any BTC address.
Except not. Look up a few older posts by DeathAndTaxes to find out why and to see the math that supports it. Basically impossible unless a flaw is found in the algorithm.
full member
Activity: 196
Merit: 100
Web Dev, Db Admin, Computer Technician
I just thought of why this could be dangerous:

The distributed/cluster version of OCLvanitygen would be able to get the private key of any BTC address.
full member
Activity: 196
Merit: 100
Web Dev, Db Admin, Computer Technician
Sounds like distributed hash cracking to me, not new but hasn't been applied well in the AMD area. Nvidia will no longer be a unique OTS platform for this method. It's about time someone moved forward with this.
hero member
Activity: 770
Merit: 500
You're fat, because you dont have any pics on FB
He does, however, create a market for gently pre-owned GPU farms amongst the hakzorz community once ASIC takes over.


Excellent point..    Smiley

sr. member
Activity: 574
Merit: 250
He does, however, create a market for gently pre-owned GPU farms amongst the hakzorz community once ASIC takes over.
administrator
Activity: 5166
Merit: 12850
Quote
Wonder if this may be relevant for the BTC mining scene?

It's not.

1. Rainbow table attacks are useless against Bitcoin.
2. MD5 hashing is a lot faster than SHA-256.
member
Activity: 98
Merit: 10
(:firstbits => "1mantis")
This could change the world!

Has anyone tried to set up a mining rig by renting out ILM's render farm for a few hours to see what would happen? :-D

I wonder if South Park Studios is mining for bitcoin between episodes Tongue
legendary
Activity: 2352
Merit: 1064
Bitcoin is antisemitic
Wonder if this may be relevant for the BTC mining scene?

http://thehackernews.com/2012/07/hacker-going-to-demonstrate-open-source.html

Quote:
"Yes, that's 154B - as in Billion. It was done entirely with AMD hardware, and involved 9x6990, 4x6970, 4x5870, 2x5970, and 1x7970 - for a total of 31 GPU cores in 6 physical systems." BitWeasil posted.
Jump to: