Latest posts of: finack

#Proof of authentication
Bitcointalk username: finack
Joined campaign :
twitter: https://twitter.com/xanjii2

#Proof of Authentication
Bitcointalk Username: finack
Bitcointalk Profile Link: https://bitcointalk.org/index.php?action=profile;u=15267
Telegram Username: @finack
joined blog campaign
Week 23: 18.01 - 24.01
blog link: https://telegra.ph/MENAPAY-revolutionizing-payment-system-in-the-whole-world-01-23

##PROOF OF AUTHENTICATION##
Week #: 10
Bitcointalk Profile Link: https://bitcointalk.org/index.php?action=profile;u=2042793
Campaign: twitter
ETH Address : 0x17D4c66154Af4372CdfCe94D8b3aEb888E6dB66E

blog: https://medium.com/@finack00/%D0%BE%D0%B3%D0%BB%D1%8F%D0%B4-ico-vena-network-5cdb825dc5fc

https://telegra.ph/Overview-ICO-Vena-Network-11-24

#Proof of Authentication
Twitter URL: https://twitter.com/xanjii2
Telegram Username: @finack

##PROOF OF AUTHENTICATION##
Telegram Username: @finack
Participating in: twitter. telegram

Quote from: haydent on July 03, 2011, 04:56:24 AM

what are you talking about, this is crap

you're crazy, this dude is awesome.

Quote from: cmh on June 30, 2011, 02:31:33 AM

I'd say they are pretty good. Do you think none of the programmers working at dropbox know about bitcoin?... "Hey guys, I just published that password code, see you after lunch!" ... (quick trip to starbucks to download a few wallet.dat files) ... "hey guys, I found a problem with the password code... oops!"

Dropbox staff can access your files directly, no need to introduce a password bug.

Quote from: andyb on June 29, 2011, 08:56:04 PM

BUT they seem to have blacklisted the whole list from mtgox. I tried bulks of 10 from around the list, and they are all listed as "hacked"

That's the point of that url - they combined a bunch of lists of leaked account details - if your email is associated with any of them it tells you. Technically it's "has a hash of my password from a site been released publicly" it doesn't care whether the hash has been cracked or not, and rightly so.

Quote from: gentakin on June 29, 2011, 08:18:30 PM

Hats off to Tycho for blocking botnets automatically! Remember, it's causing a loss of 3% pool fees.

That's not how I read the screenshot. Look at the account's current hash rate, about 4 GH. So he's letting them get work and submit it, he's likely just made it so it isn't accumulating bitcoins for it - meaning instead of a 3% share of their work he's getting a 100% share of it.

Whether or not it applies, sherman act suits are not things that happen very often. Getting a state's attorney office interested is going to be a non-starter. If there was a pool in jurisdiction that actually got attention along these lines, I'm sure they'd just move overseas overnight.

If you really wanted to attack a pool I'd suggest a tax or employment authority. I consider it very unlikely most pools are conducting themselves appropriately in regards to accounting, withholding and employment law.

It's pretty premature to be blaming this on bitcoin content. Google may do a bunch of bad things, but they want people to show ads except for a certain number of known categories - and with those they are upfront about it. They have real problems with clickfraud though, and for sure their algorithms get false positives. Combine that with ultra low traffic ("only making me pennies") and it's not worth their time to care about a identification specifically. In fact, this the best argument that it's not bitcoin related specifically - the site in question was probably too low traffic to have anyone with a pulse ever look at it.

What was your CTR? If your CTR was too high you'll pretty much get autobanned.

Quote from: tictok on June 29, 2011, 01:29:25 AM

SO you think its probably down to either malware or phising?

I'm not ruling it out but I'd be surprised if it was either.

I don't think anyone is saying none of the entries could have come from cracking. Your mentioned 8 character password could easily have been the result of cracking, especially if it had any dictionary word as part of it.

The two things we can say for (pretty darn) sure:

- Whatever cracking was done wasn't applied equally, perhaps they only focused on some entries

- Some of the results are very, very unlikely to have come from cracking

For the ones that fit in the latter category, malware and phishing aren't the only possible answers, though they are probably the most likely. Other possibilities could be password reuse: if the person who published the cracked list ran another bitcoin site that he had set up to log all the passwords in the clear, he could have tried all of them against the hashes to start out. Or, the publisher could be the mt. gox hacker or another person who gained more access to mt. gox than we've been lead to believe - there are a number of ways you could capture the password before it's hashed as someone logged in. Either by changing the site software, modifying the dns/stealing the site certificate, or simply just pulling off a XSS attack that presented a bogus idled out/login page.

There are surely more possibilities than that, they just become even less likely. The only thing you can be (pretty) sure of is it's not hash cracking.

Cheap drugs or possibly a head injury.