Bitcoin Forum
May 25, 2024, 07:49:10 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 [88] 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 ... 800 »
1741  Economy / Currency exchange / Re: Selling BTC for Prepaid Cards/PayPal (0.5 BTC) on: March 12, 2014, 01:22:04 AM
You could always use BitSimple.com rather than take a risk with a noob buyer.
1742  Bitcoin / Development & Technical Discussion / Re: What if a large number of nodes decide to relay large blocks before small ones? on: March 12, 2014, 01:14:56 AM
E.g., when a small-sized block arrives, delay it for 3-5 seconds, and only rebroadcast it when no new valid, larger block is received during this period. Would it encourage mining pools to increase their blocksize,  or does this behaviour have any bad effect on the network?

I am pretty sure all major miners (pools and solo miners) ensure they are well connected to other miners.  It doesn't really matter if non-mining nodes delay blocks a few seconds.  No miner is going to delay building off a block which extends the longest chain as it would only negatively affect their revenue.
1743  Bitcoin / Bitcoin Discussion / Re: Can we please stop saying that it is improbable to generate an inuse key? on: March 12, 2014, 01:00:10 AM
To make myself clear I've done the calculation of the acumulative probability of a collision as the addresses are generated. This probability increases with the square of the number of generated addrsses. If we consider the most restrictive case: the 160 bit space of the public key hash, a 1% probabiliy of bitcoin addresses collision will be reached when 1.2x10^23 bitcoin addresses are generated. This means that a million machines generating 30 million addresses/second each would need a thousand years to reach a 1% probability of a single collision.

Of course even that overstates the scenario in the OP which is a "inuse key".  Given the size of the key space in the highly improbable event of a collision it is very likely between two unfunded addresses created by the same mass creating entity.
1744  Bitcoin / Bitcoin Discussion / Re: A Proposal for the Mitigation of Bitcoin's Linguistic Transaction Costs on: March 11, 2014, 11:05:37 PM
No.

The problem is there is no central agency of weights and measures for Bitcoin.  So lets say some people adopt your provision and some don't.  You would see people saying "selling my steam game for one million Bitcoins" and other people being utterly confused as to why someone would be willing to pay close to $1B USD for a video game.  You can't force everyone to use your (or any) naming system, so any naming system which attempts to revalue a Bitcoin is dead before the author finished writing it.
1745  Economy / Speculation / Re: New York accepting exchange applications on: March 11, 2014, 08:58:35 PM
We might have a professional NY Bitcoin Exchange by the end of the year...

Maybe even one as successful as MF Global.
1746  Bitcoin / Bitcoin Discussion / Re: Hackers steal data from MtGox server and release it with Mark's reddit account. on: March 11, 2014, 08:40:40 PM
88,267 accounts now, but at the time of the last Mt Gox dump there were 61,020 accounts. You telling me that only 27,247 new accounts were created over the course of approximately two years, in spite of Mt Gox proclaiming that they've had reached 1M customers back in December, 2013?

The 88,267 is accounts which still have a balance with MtGox.  Someone who created an account, got verified, deposited funds, traded them, and withdrew them from the site would not show up in the list.
1747  Economy / Speculation / Re: New York accepting exchange applications on: March 11, 2014, 08:37:18 PM
Did anyone actually read the article?

Companies can submit "applications" despite there being no application process, requirements, or standards and they will be bound by rules which haven't even been written yet but may be written sometime around the end of the 2nd quarter.

In related news I am sure your local car dealership would be glad to sell you a car which doesn't exist yet with features and price to be determined next year.
1748  Economy / Service Discussion / Re: BTC Stolen from Poloniex on: March 11, 2014, 07:55:35 PM
Small bug leads to lost BTC, and a huge revelation. Why aren’t all exchanges doing this?

Because bitcoind "accounts" system doesn't scale beyond a couple hundred users.  If your system relies on it, well that will be an exciting day when you realize you have a complete recode in front of you.  You will notice performance issues at around a thousand accounts or ten thousand transactions.  RPC calls involving accounts will start to takes hundreds and then thousands of milliseconds. 
1749  Bitcoin / Bitcoin Discussion / Re: Can we please stop saying that it is improbable to generate an inuse key? on: March 11, 2014, 07:08:36 PM
How many of us have a way to generate secure(private) random data or even sufficiently random seeds... And I'm using random here for not pseudo-random that is seeded and then algorithmically generated...

Roll a bunch of dice?  Flip a bunch of coins?  It may not be particularly useful for random wallets where a new random private value is needed for each private key however it would be fairly easy to do for a deterministic wallet.
1750  Bitcoin / Bitcoin Discussion / A public service announcement: spotting phishing emails on: March 11, 2014, 03:52:16 PM
I got this email today and here is how it shows up in gmail

Quote
BTC-E no_reply@btc-e.com via smtp.com     5:58 AM (5 hours ago)
to me

Hello!
We inform you that you scan the downloaded document # 14327223 http://ge.tt/... <rest of url redacted> can not be verified for the following reason:
-Specified in the certificate data in a language other than the language passport data
Please provide a new file to check.
Sincerely,

Representative Director
BTC-E Co., Ltd.
Shibuya-ku, Tokyo

One thing to look for is this
Quote
BTC-E no_reply@btc-e.com via smtp.com

what this is saying is the email was sent indicating it was sent from btc-e.com however it actually came from smtp.com.  Now that this isn't that uncommon many sites move their email off their domain however there is a way of authenticating these off email domains and it wasn't done.

So any time you see a "via" in gmail be wary.  There is a high chance it is a phishing attempt.  It could be an uneducated operator or some misconfiguration but your phishing radar should be going off when you see a redirected email.

Looking at the source
Quote
Delivered-To: <redacted>
Received: by 10.170.132.70 with SMTP id y67csp158747ykb;
        Tue, 11 Mar 2014 02:58:50 -0700 (PDT)
X-Received: by 10.66.162.74 with SMTP id xy10mr46827749pab.4.1394531930066;
        Tue, 11 Mar 2014 02:58:50 -0700 (PDT)
Return-Path: <no_reply@btc-e.com>
Received: from mailer134.gate183.sl.smtp.com (mailer134.gate183.sl.smtp.com. [192.40.183.134])
        by mx.google.com with ESMTP id pi6si17253804pbb.10.2014.03.11.02.58.49
        for <gerald@tangiblecryptography.com>;
        Tue, 11 Mar 2014 02:58:50 -0700 (PDT)
Received-SPF: softfail (google.com: domain of transitioning no_reply@btc-e.com does not designate 192.40.183.134 as permitted sender) client-ip=192.40.183.134;
Authentication-Results: mx.google.com;
       spf=softfail (google.com: domain of transitioning no_reply@btc-e.com does not designate 192.40.183.134 as permitted sender) smtp.mail=no_reply@btc-e.com;
       dkim=pass header.i=@smtp.com
Return-Path: <no_reply@btc-e.com>
X-MSFBL: Z2VyYWxkQHRhbmdpYmxlY3J5cHRvZ3JhcGh5LmNvbUAxOTJfNDBfMTgzXzEzNEBz
   bXRwY29tXzExQA==
DKIM-Signature: v=1; a=rsa-sha256; d=smtp.com; s=smtpcomcustomers; c=relaxed/simple;
   q=dns/txt; i=@smtp.com; t=1394531929;
   h=From:Subject:To:Date:MIME-Version:Content-Type;
   bh=EptpTsx18R734YExCd0CN520kmNgDylmBwR2r+Pyuqw=;
   b=f2hvNXaJT9YyFXhXAYg7qRLTST5KlgacBGLJE/rQYLnlNXuiUMbLxMlOvgePe0Mc
   lmS0HCW2hdDJ4BGdqwpVWMxdTIUR8JtiIz8XF4oSkXTYG80GoFz5SWxGfX7w4K9j
   9gqnLIbogpkBa+DxB0xX7pENIlH6Pf/XkyQScWaf1bA=;
Received: from [216.55.179.130] ([216.55.179.130:61625] helo=216-55-179-130.dedicated.codero.net)
   by sl-mta06.smtp.com (envelope-from <no_reply@btc-e.com>)
   (ecelerity 3.5.5.39309 r(Platform:3.5.5.0)) with ESMTPSA (cipher=AES256-SHA)
   id DD/65-01037-95EDE135; Tue, 11 Mar 2014 09:58:49 +0000
From: "BTC-E" <no_reply@btc-e.com>
Message-ID: <DD.65.01037.95EDE135@sl-mta06>
Subject: BTC-E Passport
To: <redacted>
Content-Type: multipart/alternative; boundary="chnq7o2neA2=_nG4ebCT6XPRtS76K4DnFp"
MIME-Version: 1.0
Organization: BTC-E
Date: Tue, 11 Mar 2014 02:58:51 -0700
X-SMTPCOM-Tracking-Number: 755a5166-7a64-405b-9339-37db125228cb
X-SMTPCOM-Sender-ID: 24012
X-SMTPCOM-Spam-Policy: SMTP.com is a paid relay service. We do not tolerate UCE of any kind. Please report it ASAP to abuse@smtp.com


A couple of things in here.  The first is that the sent from and reply to emails are simply lines of text.  There is absolutely no security.  You can send email with a from email address of obama@whitehouse.com as easily as you can type the letters.  So never rely on those.

This show where the email actually originated from
Quote
Received: from mailer134.gate183.sl.smtp.com (mailer134.gate183.sl.smtp.com. [192.40.183.134])

now as I said before it isn't that uncommon for email to originate off domain however this is the warning sign
Quote
spf=softfail (google.com: domain of transitioning no_reply@btc-e.com does not designate 192.40.183.134 as permitted sender) smtp.mail=no_reply@btc-e.com;

In simple terms it is saying btc-e has not approved the originating server to send email on its behalf.  Google should really make these types of "soft" failures more pronounced with scary warnings but they don't.

Lastly the actual originator is a commercial service.  They provided this information in the header
Quote
X-SMTPCOM-Tracking-Number: 755a5166-7a64-405b-9339-37db125228cb
X-SMTPCOM-Sender-ID: 24012
X-SMTPCOM-Spam-Policy: SMTP.com is a paid relay service. We do not tolerate UCE of any kind. Please report it ASAP to abuse@smtp.com

If your email client gives you the option to report as phishing (not just report as spam) be sure to do so.  Most will forward this back to in this case to abuse@smtp.com.
You can also manually forward it to abuse@smtp.com and report it is phishing.
1751  Bitcoin / Bitcoin Discussion / Re: Password strength on: March 11, 2014, 02:36:48 PM
So can someone tell me why this password wouldn't be secure?

"OnMondayMorningsILikeToWakeUpWithANiceGlassOfOrangeJuiceBeforeEatingMyTooast"
The only issue would be if this phrase is from a book or movie (potentially even one you are unaware of).  That is why systems like diceware exist to create a truly random sequence of words.

Although brute force capabilities have come a long way, passwords consisting of 10 digits (all keyboard symbols) are beyond the brute force (see below before you complain) capabilities of most entities and 12 digits would be beyond the capabilities of nation states in most situations (i.e. no nation is going to expend a year of super computing time at a cost of $500B in order to break your facebook password Smiley ).   If your a significant threat to a nation state and they would be willing to expend billions of dollars to attack you well you should probably push that out to 15 digits.  For those who prefer dicewords that would be 5, 6, and 8 dicewords respectively.

However that assumes the attacker is just doing a pure brute force attack of all possible passwords.  The reality is that beyond 9 digits it starts taking an increasingly incredible amount of time for each additional digits.  So password crackers are going to try a variety of methods which are often much faster (even on much longer passwords).

1) Check the hash against databases of known compromised passwords (you can find on various sites lists of 15M+ previously leaked and broken passwords).  If your passphrase is on that list your toast.  Even some hobbyist with a single CPU can break it in a matter of minutes.

2) Check the hash against phrases from movies, books, memes, pop culture (no doubt Satoshi's genesis block quote is insecure).

3) Check the hash against a dictionary (possibly foreign languages as well).

4) A modified version of #3 is to take the same dictionary and perform derivations (which is why Troub@dor1 is a lot weaker than it may initially seem).

So having a long passphrase is good but it isn't a guarantee that the password is strong (unless it is random).  To ensure it is strong it needs to not be breakable by the four methods above as well.  I noticed in your example you wrote "Tooast" not "Toast".  If that was intentionally then congratulations it ensured it probably isn't going to match any phrase search.
1752  Bitcoin / Bitcoin Technical Support / Re: reindexing blockchain on: March 11, 2014, 02:02:20 PM
As for your situations I can not say for sure one way or another, I can simply say that in majority of cases
the main limitation is the hard drive speed

I said main limitatoin, not only limitation.  In the average computer the hard drive is the limiting factor, speed it up and you speed the sync speed.  You can, of course, get into situations where your hard drive speed is not the limiting factor. (I haven't yet)  

Exactly. Reindexing on a 3Ghz machine with 1GB of RAM and a 5400 RPM drive is going to be slower than reindexing on a 2 Ghz machine with 8 GM of RAM and a fast SDD.  A good CPU helps some especially on the more recent blocks (which are larger, and have more txs to validate) but someone looking for the best bang for their buck when upgrading a system should look at getting a good SSD.
1753  Bitcoin / Press / Re: [2014-03-10] Economist Nouriel Roubini Declares Bitcoin a Ponzi Scheme on: March 11, 2014, 04:01:46 AM
Quote
It is difficult to get a man to understand something, when his salary depends upon his not understanding it.
1754  Bitcoin / Legal / Re: Seeking non-legal opinions - how can this be done? on: March 11, 2014, 03:42:19 AM
Company A would be issuing prepaid access (formerly called stored value) which is regulated activity in most states.
1755  Economy / Scam Accusations / Re: COINABUL wants to file a CTR for deal lower than 10K USD... WTF on: March 11, 2014, 12:56:51 AM
You have been scammed.   Sorry but no sense in getting your hopes up.  Coinabul has a long history of ripping people off.  The CTR is limited to cash (i.e. the real physical currency of the US or foreign nation) and virtual currencies don't meet the requirement, hell even a bank wire in dollars doesn't meet the requirement.  Unless you paid them with a stack of US federal reserve note there is no need for a CTR.   Still that is beside the point, even if a CTR was required it doesn't require any sort of delay not even a single minute.  You have been scammed.
1756  Bitcoin / Bitcoin Discussion / Re: a LOT of 50 BTC transactions right now on: March 10, 2014, 11:20:26 PM
If you look at the parent tx they aren't some long mined unmoved coins.  Someone create a bunch of 50 BTC outputs.  I can only think of one reason and that would be to freak people (who can't follow the blockchain) out.
1757  Bitcoin / Bitcoin Discussion / Re: Wikipedia founder asking for help to learn Bitcoin on: March 10, 2014, 11:13:24 PM
I have no problem with someone convincing a rich person that Bitcoin is useful to them.  I think it is utterly silly for people (who I imagine are not millionaires) deciding they need to help a millionaire like Bitcoin by giving him free money.  To each his own.
1758  Bitcoin / Bitcoin Discussion / Re: Wikipedia founder asking for help to learn Bitcoin on: March 10, 2014, 11:05:41 PM
I sent him .1 .... will send him more later.  If we don't get him at least 100 BTC I am going to be really upset with the bitcoin community.

Yes sent money to a millionaire in the hopes that it will convince him to let you donate more money to his foundation which relies on donations?

Hell 0.1 BTC could have bought a lot of meals for homeless people but if you want to give money to the 1% to convince them to use Bitcoin well I guess that is your right.
1759  Bitcoin / Bitcoin Discussion / Re: How to steal Satoshi's stash? on: March 10, 2014, 10:15:20 PM
if the network hashrate is 30,000,000 Gh/S,
isn't that 30 million billion hashes per second?  would be the
same as enough computing power to try 30 million billion private
keys per second?

At that rate, it would only take the entire network 359,676 years,
not the billions of years said...

Good logic, but you have a math error I believe.  The network is 30 PH/s which is 30*10^15.  Simple trick is to just count the metric prefixes (each one is a factor of 1000).  So kilohash, megahash, gigahash, terrahash, petahash is 1,2,3,4,5 so 1000^5. The time required with the assumptions you have would be  359,676,102,360,200 years.  If we assume a network one trillion times more powerful it would still be 360 years.  

However even that is unlikely.  A couple points to consider:
1) The network can't do anything but compute hashes but if we assume it could be repurposed to brute force EDSA keys it would take more computing cycles to perform one ECC attempt than it does to perform one SHA-2 hash.  It would be something on the order of 80x as long (although that is some crude estimate on my hardware).  So 30 PH/s wouldn't be 30 PK/s but maybe 1 PK/s (peta keys attempted per second) but his is minor compared to #2 below.

2) The security of ECDSA is 128 bit if the PubKey is known.  If it the PubKey is unknown the only fastest attack is to attempt a preimage of the PubKeyHash.  That has a complexity of 2^160 which is 2^32 larger or ~ 4 billion.  Even if you could break a known PubKey in one year it would take 4 billion years to break the hash of an unknown pubkey.

Keys with 128 bit security are infeasible to break by brute force using classical computing.  However this doesn't mean that they can't be broken by cryptanalysis or quantum computing (which "go around" the problem rather than try to beat it by the pure expenditure of computing power).
1760  Bitcoin / Bitcoin Discussion / Re: Password strength on: March 10, 2014, 09:44:17 PM
Quote
Actually, that XKCD comic is dangerous advice for Joe Average.  It is true only IF those words are chosen completely at random.

But that is not how Joe Average would go about choosing he words. He would go something like "Horse...uhm...Cart...uuhhhm...Galloping...Away!"

Someone that foolish is also likely to use "p@sswordZ1234 as their password instead.  See the @ and the "Z" give it strength.  Even "Horse Cart Galloping Away" is stronger than most passwords (based on the results of password table breaches).


Also, to resist brute force attacks by supercomputers (a realistic threat for high balance bitcoin wallets) you need something like 10-12 words and not 4.

Which is not that much easier to remember than 16 characters.

Please show me the math where it takes 10 to 12 random words from a list of say the diceware list to equal the entropy of 16 random characters.  If you are right and have the math to show it I will give you 100 mBTC.

Don't get excited how about we estimate it like this.  There are 80? 96 characters (upper, lower, number, and symbol) on standard keyboard.

A guestimation game.  Do you think 96^16 >= 7776^10?  If not what x do you think solves this equation 7776^x >= 96^16

For those playing along at home, don't grab a calculator right away.  Just take a guess based on the base and the exponents.



Pages: « 1 ... 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 [88] 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 ... 800 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!