Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMñ<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=571.msg5736#msg5736">Quote from: knightmb on July 25, 2010, 07:44:02 PM</a></div><div class="quote">If I figure out that Public Key 123456 generates Hash ABCD<br/>and<br/>Public Key 654321 also generates Hash ABCD<br/><i>I'm still left without the Private Key.</i><br/><br/>But from what you are saying, all I need is Public Key 654321 and I can spend coin pretending to be Public Key 123456.<br/></div>You would still have to sign it with public key 654321. &nbsp;You need to find a collision using a public key for which you know the private key.<br/><br/>When you claim a Bitcoin Address transaction, you give your public key that matches the hash, then you must sign it with that key.<br/><br/>Red's point is that it's easy to quickly generate insecure public keys which you could break and find the private key after you find a collision.<br/><br/>He points out that if the public key was required to be a secure one, one which must have required significant work to find the prime numbers, that would increase the strength above that of the hash function alone. &nbsp;Someone trying to brute force would have to take time generating a key for each attempt.<br/></div> text/html