jabetizo
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 12, 2013, 01:03:17 PM |
|
If you succeed to decrypt SHA you would have invented infinite data compression. ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) +1
|
|
|
|
JoelKatz
Legendary
Offline
Activity: 1596
Merit: 1012
Democracy is vulnerable to a 51% attack.
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 12, 2013, 01:32:40 PM |
|
You will never have a commercially made ASIC miner for SHA encryption!
Until every organisation on the internet and off the internet changes the way they encrypt their information, you are out of luck.
Reason being: This ASIC hardware could too easily be reverse engineered to decrypt SHA. And with it's small size and power consumption they could be ran almost anywhere barely undetected constantly attacking SHA at an incredible rate. Essentially these devices would put too much power into public hands.
If you are going to continue to pursue this Bitcoin mining game you better load up on FPGAs and GPUs!
Now someone tell me I am wrong.
Thanks.
Ltcfaucet, what you've just said is one of the most insanely idiotic things I have ever heard. At no point in your rambling, incoherent post were you even close to anything that could be considered a rational thought. Everyone on this forum is now dumber for having read it. May God have mercy on your soul.
|
I am an employee of Ripple. Follow me on Twitter @JoelKatz 1Joe1Katzci1rFcsr9HH7SLuHVnDy2aihZ BM-NBM3FRExVJSJJamV9ccgyWvQfratUHgN
|
|
|
Jaw3bmasters
Full Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 196
Merit: 100
Another block in the wall
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 12, 2013, 01:49:21 PM |
|
.........Everyone on this forum is now dumber for having read it. May God have mercy on your soul.
Damn.
|
In Cryptography we trust.
|
|
|
organofcorti
Donator
Legendary
Offline
Activity: 2058
Merit: 1007
Poor impulse control.
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 12, 2013, 02:10:17 PM |
|
You will never have a commercially made ASIC miner for SHA encryption!
Until every organisation on the internet and off the internet changes the way they encrypt their information, you are out of luck.
Reason being: This ASIC hardware could too easily be reverse engineered to decrypt SHA. And with it's small size and power consumption they could be ran almost anywhere barely undetected constantly attacking SHA at an incredible rate. Essentially these devices would put too much power into public hands.
If you are going to continue to pursue this Bitcoin mining game you better load up on FPGAs and GPUs!
Now someone tell me I am wrong.
Thanks.
Ltcfaucet, what you've just said is one of the most insanely idiotic things I have ever heard. At no point in your rambling, incoherent post were you even close to anything that could be considered a rational thought. Everyone on this forum is now dumber for having read it. May God have mercy on your soul. Hey! He only wished (3 times in all) for someone to tell him that he's wrong, not that he's some kind of intelligence-reducing contagious meme producer. Give away insults like that for free and we'll all be out of a job.
|
|
|
|
witherworth
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 12, 2013, 02:41:56 PM |
|
So you see, while it take so incredibly little time to encrypt, the decryption time grows exponentially larger with each little bit of security you add. So, would it be possible for someone to create some ASICs that are designed to break security in use today? Sure, but as soon as that was figured out, everyone would just increase what security strength they use, and all the ASICs become completely useless then. It would be interesting if someone started working on ASICs for 2048 bit encryption of some popular types, then waited for everyone to upgrade (creating rainbow tables or whatever in the meantime), then they could attack several companies at a single time before everyone noes up to 4096. It'd be a bit surprising to jump up in security, only to find it less secure than what everyone was just on.
I'm not quite sure how processing SHA256 hashes using ASICs is "impossible" or that 'they' would never allow it. I suspect a basic lack of understanding of the underlying technologies by the OP. Regarding building ASICs specifically for the purposes of decryption, its already been done a very long time ago. Here is one example I can think of: http://en.wikipedia.org/wiki/EFF_DES_crackerThe principal designer was Paul Kocher, president of Cryptography Research. Advanced Wireless Technologies built 1856 custom ASIC DES chips (called Deep Crack or AWT-4500), housed on 29 circuit boards of 64 chips each. I was sure something existed somewhere. Thanks for the link!
|
|
|
|
mrb
Legendary
Offline
Activity: 1512
Merit: 1028
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 13, 2013, 09:53:52 AM |
|
You will never have a commercially made ASIC miner for SHA encryption!
Until every organisation on the internet and off the internet changes the way they encrypt their information, you are out of luck.
Reason being: This ASIC hardware could too easily be reverse engineered to decrypt SHA. And with it's small size and power consumption they could be ran almost anywhere barely undetected constantly attacking SHA at an incredible rate. Essentially these devices would put too much power into public hands.
If you are going to continue to pursue this Bitcoin mining game you better load up on FPGAs and GPUs!
Now someone tell me I am wrong.
Thanks.
You are wrong ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Nobody has given you a full technical response, so here is one: - First of all SHA256 is hashing, not encryption - Mining ASICs can only do 1 thing (find x such as SHA256(SHA256(x)) has zeros in the low 32 bits). They cannot be used for general attacks (eg. given y, find x such as SHA256(x) = y). - There is no point in reverse engineering them: their design is simple, cryptographers can easily design some to suit their exact problem, and have already done so in the past: http://rijndael.ece.vt.edu/sha3/publications/DATE2012SHA3.pdf- Cryptographers designed SHA256 to resist bruteforce attacks (by ASICs or any fast hardware) thanks to the sheer size of the output hash and conservative design. For example, finding a SHA256 pre-image takes on average 2^256 calls to the compression function. ASICs only bring a relatively tiny performance improvement over FPGAs of at most ~50x (per mm² of die area). 50x is huge for Bitcoin, but tiny cryptographically speaking. So a pre-image attack on ASIC would be equivalent to a 2^250 pre-image attack on FPGA. Big deal. No one cares. This is not a world-changing event. Bottom line: cryptographers already planned for fast SHA256 hardware, this hardware already exists, and this hardware is not constantly breaking the world.
|
|
|
|
dustintrammell
VIP
Full Member
Offline
Activity: 156
Merit: 103
Cleverly disguised as a responsible adult.
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 13, 2013, 10:17:48 AM |
|
Explain!
How am I wrong?
First, you cannot "decrypt" a hash. Go read a cryptography primer.
|
Dustin D. Trammell Twitter: @druidian PGP: E0DC F55C 9386 1691 A67F FB18 F6D9 5E52 FDA6 6E16
|
|
|
nathanrees19
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 13, 2013, 09:24:38 PM |
|
Explain!
How am I wrong?
You've misunderstood pretty much everything.
|
|
|
|
YipYip
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 14, 2013, 01:15:42 AM |
|
Ltcfaucet, what you've just said is one of the most insanely idiotic things I have ever heard. At no point in your rambling, incoherent post were you even close to anything that could be considered a rational thought. Everyone on this forum is now dumber for having read it. May God have mercy on your soul.
I felt superior until u pointed this out ....I hold u responsible for me feeling stupid ![Cry](https://bitcointalk.org/Smileys/default/cry.gif)
|
OBJECT NOT FOUND
|
|
|
witherworth
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 14, 2013, 01:44:07 AM |
|
So you see, while it take so incredibly little time to encrypt, the decryption time grows exponentially larger with each little bit of security you add. So, would it be possible for someone to create some ASICs that are designed to break security in use today? Sure, but as soon as that was figured out, everyone would just increase what security strength they use, and all the ASICs become completely useless then. It would be interesting if someone started working on ASICs for 2048 bit encryption of some popular types, then waited for everyone to upgrade (creating rainbow tables or whatever in the meantime), then they could attack several companies at a single time before everyone noes up to 4096. It'd be a bit surprising to jump up in security, only to find it less secure than what everyone was just on.
I'm not quite sure how processing SHA256 hashes using ASICs is "impossible" or that 'they' would never allow it. I suspect a basic lack of understanding of the underlying technologies by the OP. Regarding building ASICs specifically for the purposes of decryption, its already been done a very long time ago. Here is one example I can think of: http://en.wikipedia.org/wiki/EFF_DES_crackerThe principal designer was Paul Kocher, president of Cryptography Research. Advanced Wireless Technologies built 1856 custom ASIC DES chips (called Deep Crack or AWT-4500), housed on 29 circuit boards of 64 chips each. Really cool read, thanks for the link. However, this is not quite the same as what I proposed. I was talking about building ASICs for security that we'll use in the future, not what security we're using now, or what was used in the past. You could, for instance, figure out what key bit length the government is currently using, double it, and build a massive ASIC far for that. After a few years, when the government upgrades their encryption (hopefully not to a new algorithm, just a new key length), you'll turn your machines on and be cranking away at intercepted messages or passwords. So, while they think they're getting higher security (which they are), they're also stepping into the hands of someone with deep pockets who's ready to break that security. That's a partially dangerous situation for any government.
|
|
|
|
grue
Legendary
Offline
Activity: 2058
Merit: 1434
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 14, 2013, 03:41:17 AM |
|
The U.S. Government is who is preventing ASIC I can almost guarantee you.
proof? inb4 "the lack of proof proves the conspiracy!" logic
|
|
|
|
DeathAndTaxes
Donator
Legendary
Offline
Activity: 1218
Merit: 1079
Gerald Davis
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 14, 2013, 04:11:42 AM |
|
Let's put bitcoin aside, and focus completely on security here, since you've made that a serious concern. Here's the thing with security, it's exponentially more difficult to break, for every small difficulty increase in encrypting. This means it'll always be much easier to increase difficulty, than it will to break the harder difficulty. As technology advances and we get fast machines to break 256 bit encryption, 512 comes out, and after some time, we can then break 512, but it's already been upgraded to 1024, and so on. Well no. Lets ignore that SHA-256 is a hash not encryption and thus with infinite amount of time and infinite amount of energy you can't "decrypt" SHA-256. Still 256 but keys are sufficiently large that even at the thermodynamic limit (i.e. a theoretically perfect computer) there is insufficient energy and matter in our solar system (i.e. kill everything and convert the entire solar system into a super computer which uses the complete output of our star until it dies) to even .... COUNT to 256 bit, much less perform any complex calculations. It is possible that encrypting algorithms will be compromised due to undiscovered flaws which allow attackers to perform attacks at faster than brute force but 256 bit keys will not be brute forced. For information on the energy requirements (using an as on yet not invented perfect computer) required to count to 2^256 ... These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space. http://www.schneier.com/blog/archives/2009/09/the_doghouse_cr.html
|
|
|
|
noncecents
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 74
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 14, 2013, 07:35:53 PM |
|
Now someone tell me I am wrong.
Thanks.
![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fcache.ohinternet.com%2Fimages%2Fthumb%2F2%2F2d%2FTrollface_HD.png%2F618px-Trollface_HD.png&t=665&c=BxF9MnzWk6m3_g)
|
|
|
|
mightycount
Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 101
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 14, 2013, 08:31:28 PM |
|
You are an idiot.... 1. You are a dyed in the wool troll... trolls have no understanding of technology. 2. You cannot 'decrypt a hash' , it would be like trying to see the contents of a black hole. 3. An ASIC is just that.... APPLICATION SPECIFIC INTEGRATED CIRCUIT.... it would be like buying a Skoda and thinking that putting a new set of windscreen wipers in it will make it a Rolls Royce.
You ever see the Top Gear when they compared a Rolls Royce to a Mercedes to a "Bentley" ? http://www.youtube.com/watch?v=OyH-351Z_-0&t=1m17s Give it like a minute or so. Is that a spare they have under the front hood? Hilarious... Almost as hilarious as the dude who started this thread.
|
Personal Bitcoin Black List - Companies and people to avoid! ````` Butterfly Labs...MtGox...ragingazn628...(reserved)... `````
|
|
|
n0ne
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 22, 2013, 02:35:56 AM |
|
Faggot conspiracy theorist OP ran away.
|
|
|
|
mjc
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 22, 2013, 05:48:38 AM |
|
Let's say it was possible, then there should be a change in what is used to secure technology.
Technology is not so tied to an implementation that it cannot change.
One example progression: SSL SSLv2 SSLv3 TLS
Look at the number of ciphers . key lengths and the such that make up the collection of various SSL implementations.
Then look at Rainbow tables and whats happening there with password cracking. As the tables grow the methods used to store passwords change.
The industry will adapt to the evolving threats and live on.
Just to be clear though, as stated earlier, SHA is only a hash and part of an encryption system, not encryption by itself.
Another thought, given that there was a couple million dollars put into the existing ASIC effort, and part of that is profit for the companies creating ASIC, how difficult would it be for large criminal organization or a state entity, spend that sort of money to build it themselves, it is was possible to use it to perform a real attack.
Given BTC @ $16.83 that's just my 0.001188 BTC
|
|
|
|
DobZombie
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 22, 2013, 09:32:39 AM |
|
2. it would be like trying to see the contents of a black hole.
CHALLENGE ACCEPTED!
|
Tip Me if believe BTC1 will hit $1 Million by 2030 1DobZomBiE2gngvy6zDFKY5b76yvDbqRra
|
|
|
Ltcfaucet (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 25, 2013, 06:32:25 PM |
|
Oh hai guys! An Avalon ASIC has shipped, ROFL. I guess I was wrong. ![Grin](https://bitcointalk.org/Smileys/default/grin.gif)
|
|
|
|
BR0KK
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
January 25, 2013, 06:44:47 PM |
|
They said so .... that doesn't imply they did, or shiped a shoe
|
|
|
|
|