Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Milk Sad Disclosure

milksad.info

Post reply on HN
Print view View original

91–100 of 133 posts

Re: Milk Sad Disclosure

#91

Post by nullc »

alchemist1e9 wrote: post #89
werrett wrote: post #88

Earlier quoted context omitted.

It’s not not a myth. Not even really lost to time (or a simple Google search). E.g https://www.reddit.com/r/Bitcoin/comments/1zti1p/17956_hacke... https://www.wired.com/2015/07/brainflayer-password-cracker-s...

FUD!! and you know it if you actually took time to read the post. > I could find the passwords for 17.956 of the addresses. * Only 2 addresses of the hacked brainwallets are currently not empty, and the total money that I could actually steal is 0.00115215 BTC. > Somebody seems to have systematically flooded the blockchain with transaction to brainwallets. E.g. this transaction: https://blockchain.info/tx/ba421da33e5…

> Nobody’s real brain wallets are being hacked! It’s just left over traces from someone running aome testing in early days of bitcoin.

I've talked to a LOT of real people who's real brainwallets were hacked. Certainly there is also some 'testing' but that doesn't change the fact that there have been real and substantial losses.

Brainwallets are very dangerous.

A brainwallet is the same thing as using a user provided password to secure a high value system that has an unsalted and public password hash database. This is a negligent practice. In the corporate world it wouldn't be shocking to learn that a security engineer was instantly fired for implementing such a practice.

Good security advice results in practical security even if the user uses the system less than perfectly. Attacker-originated security "advice" provides security only under unrealistic perfect use. Telling people to use brainwallets is like recommending one-time-pad encryption. In practice the security will be fragile if not outright broken though in theory with it may go okay sometimes.

Correct usage would require secure mechanically generated uniformly random seed phrases with a hundred plus bits of entropy. That isn't generally what people do in practice and the few who have often have issues with retention of the string being inevitably very poor, causing them to lose the funds by forgetting (esp after getting a fever). (Of course, if they're going to write it down and they didn't generate it themselves then it's not something anyone should be calling a brainwallet anymore.)

Re: Milk Sad Disclosure

#92

Post by nullc »

alchemist1e9 wrote: post #90
yieldcrv wrote: post #85

Earlier quoted context omitted.

What would change your view about that? This was one of the best uses of GPUs 10 years ago, people still have those instances running just in case people use “obscure” common phrases from books again instead of mnemonics Its more like anyone that thought they were clever got swept. There arent statistics, just threads on bitcointalk and reddit

If you used common phrases from books you definitely aren’t clever and deserve to have your funds swept.

The person who originated the practice and created the first "brainwallet" site did exactly what you're doing: insisted that it was secure, and insisted that people who lost their funds deserved it. Are you also doing what he did? stealing the funds of the deserving victims yourself?

Eventually taking the weak brainwallets he talked people into creating wasn't enough: He lost his bitcoin (I think via gambling but maybe an exchange hack), whined he was broke for a while, and whined that not many people were making hackable brainwallets, then added a more explicit vulnerability to the site. He vanished after it was caught.

Re: Milk Sad Disclosure

#93

Post by jrockway »

nullc wrote: post #73

Some extra relevant links: https://github.com/libbitcoin/libbitcoin-system/pull/559 The pull request adding the vulnerability, the lack of review or collaboration is worth noticing. The prior code was already dubious in that AFAIK std::random_device library doesn't promise that the randomness is suitable for cryptography. I believe on common systems where this code was run the old code was not likely to be exploitabl…

I love how many references to Stack Overflow that PR added to the codebase. Always a good sign.

Re: Milk Sad Disclosure

#95

Post by nullc »

rebelchicken wrote: post #87
qingcharles wrote: post #84

Earlier quoted context omitted.

Tony Story.. that movie got two thumbs up. "Tony Story" has you laughing straight out of the gate. Billed as an action-comedy, it's the ultimate clash of the titans between machismo and mirth. The film follows our hero, Tony, a middle-aged man who wakes up one morning to find himself inexplicably transformed into a small plastic action figure. The plot thickens as he learns he's the star of a beloved, but sadly disco…

I logged in for the first time in a decade to say that I am sad this movie isn't real.

I am replying to confess that I was wooshed and had sent a note to my partner that we should watch it.

Re: Milk Sad Disclosure

#96

Post by Terr_ »

qingcharles wrote: post #84
Terr_ wrote: post #82

Earlier quoted context omitted.

Wallace Shawn also has some memorable voice roles, such as the T-Rex in Tony Story, and the insurance-company boss in The Incredibles, etc.

Tony Story.. that movie got two thumbs up. "Tony Story" has you laughing straight out of the gate. Billed as an action-comedy, it's the ultimate clash of the titans between machismo and mirth. The film follows our hero, Tony, a middle-aged man who wakes up one morning to find himself inexplicably transformed into a small plastic action figure. The plot thickens as he learns he's the star of a beloved, but sadly disco…

Alas, my new phone doesn't transcribe/edit quite the same as the old one.

Awl sew, thee spiel checquer frowned know tissues bee four eye clacked.

Re: Milk Sad Disclosure

#97

Post by nullc »

nullc wrote: post #73

Some extra relevant links: https://github.com/libbitcoin/libbitcoin-system/pull/559 The pull request adding the vulnerability, the lack of review or collaboration is worth noticing. The prior code was already dubious in that AFAIK std::random_device library doesn't promise that the randomness is suitable for cryptography. I believe on common systems where this code was run the old code was not likely to be exploitabl…

https://twitter.com/evoskuil/status/1689128996120776704

No intent to change. The tweet confused about thinking this was some third party wallet using libbitcoin.

Instead, from the writeup it appears that at least some of the users followed the above BIP39 seed generation instructions to generate a seed that they used with other assorted BIP39 compatible wallets such as typical hardware wallets.

Re: Milk Sad Disclosure

#98

Post by knocte »

jrockway wrote: post #93
nullc wrote: post #73

Some extra relevant links: https://github.com/libbitcoin/libbitcoin-system/pull/559 The pull request adding the vulnerability, the lack of review or collaboration is worth noticing. The prior code was already dubious in that AFAIK std::random_device library doesn't promise that the randomness is suitable for cryptography. I believe on common systems where this code was run the old code was not likely to be exploitabl…

I love how many references to Stack Overflow that PR added to the codebase. Always a good sign.

LOL! The second S.O. link actually goes to show how broken C++ is: https://stackoverflow.com/a/18298965/544947

Re: Milk Sad Disclosure

#99

Post by siwatanejo »

alchemist1e9 wrote: post #89
werrett wrote: post #88

Earlier quoted context omitted.

It’s not not a myth. Not even really lost to time (or a simple Google search). E.g https://www.reddit.com/r/Bitcoin/comments/1zti1p/17956_hacke... https://www.wired.com/2015/07/brainflayer-password-cracker-s...

FUD!! and you know it if you actually took time to read the post. > I could find the passwords for 17.956 of the addresses. * Only 2 addresses of the hacked brainwallets are currently not empty, and the total money that I could actually steal is 0.00115215 BTC. > Somebody seems to have systematically flooded the blockchain with transaction to brainwallets. E.g. this transaction: https://blockchain.info/tx/ba421da33e5…

> A well designed brainwallet is perfectly fine and safe

Especially if the brainwallet adds a salt, which is maybe the problem that the previous poster was referring to. Brainwallets that don't add a salt are definitely a risk.

Re: Milk Sad Disclosure

#100

Post by chx »

yieldcrv wrote: post #4

Are any of the following two things true: Multi signature addresses mitigate this attack vector? With the “taproot+schnoor” upgrade last year, it is impossible to tell if funds are stored in a single signature vs multi signature address?

[flagged]
Post reply on HN