ryan-c

50 ms·

451.
by ryan-c 9y ago
That gets defrauded via a technique called "cookie stuffing". https://en.wikipedia.org/wiki/Cookie_stuffing
452.
by ryan-c 9y ago
Taking money from someone who did not intend to give it to you is a dick move, regardless of legality or technical difficulty of doing so.
453.
by ryan-c 9y ago
No, it's slightly different from SHA3-256. There was a tweak for standardization.
454.
by ryan-c 9y ago
There are multiple parties doing this, at least tens of billions of keys in their databases.
455.
by ryan-c 9y ago
Not worth the effort. You could absolutely make a wallet that does this, but you'd have to either do a lookup with a trusted third party, or keep around a bloom filter of used addresses to query against (probably about a gigabyte). We&
456.
by ryan-c 9y ago
Looks like there was bitcoin left in the address he published the private key for until about 30 minutes ago. I hope that was a deliberate giveaway. https://blockchain.info/tx/2685ff794de17cebdf94eb0f111e8b8c0...
457.
by ryan-c 9y ago
I am actually really surprised it took a month for someone to swipe the BTC he sent to an address with a private key of 0xfacebeef. That could be found via an incremental search in under an hour of CPU search time on one computer. I note th
458.
by ryan-c 9y ago
Mattresses are negotiable. I offered to pay cash and they took like 40% off the price. I was kind of dumbfounded.
459.
by ryan-c 9y ago
I use layer 2 filtering on my home network in order to get direct internet access without going through my "mandatory" ISP-provided gateway that authenticates the port with 802.1x EAP-TLS.
460.
by ryan-c 9y ago
Bitsig.io doesn't put arbitrary text into the blockchain. Given a string, if a Bitcoin address exists with sha256(string) as its private key, bitsig.io will publish the string, address, and first time the address was used. It also has
461.
by ryan-c 9y ago
Bitsig.io and Blockchain.info appear to show everything in UTC. This Gizmodo tweet, screenshotting Spicer, will show up in whatever timezone you set Twitter to https://twitter.com/Gizmodo/status/824635801657114624
462.
by ryan-c 9y ago
The bitcoin transaction happened hours after the tweet.
463.
by ryan-c 9y ago
You're probably talking about me. I actually screwed up when I was moving coins around, and ended up emptying someone's address out, however I put everything back within a few minutes. I haven't had anyone whose coins I touch
464.
by ryan-c 10y ago
No birthday bound. The keyspace reduction is based on the number of addresses with a balance.
465.
by ryan-c 10y ago
They're running a brute force preimage attack against all bitcoin addresses which currently have a balance. The reason they say "collision" is that if they found a key that hadn't been made weak on purpose, it would prob
466.
by ryan-c 10y ago
The wallets they've found most likely were made with weak keys on purpose.
467.
by ryan-c 10y ago
P2SH addresses can be brute forced several orders of magnitude faster than P2PKH. The attacker needs to generate 1-of-2 multisig scripts in the following form: OP_1 [compressed pubkey] [0x02, 29 random bytes, 3 byte counter] OP_2 OP_CHECKMU
468.
by ryan-c 10y ago
They're just doing a naive sequential search.
469.
by ryan-c 10y ago
The use in wget seems a little scary.
470.
by ryan-c 10y ago
United consistently fucks things up.
471.
by ryan-c 10y ago
My pet peeve with CISSP (and all other ISC^2 certifications) is this: https://www.isc2.org/candidate-background.aspx It appears to say that if you ever hung out on IRC and tried to keep your handle private, you're inel
472.
by ryan-c 10y ago
I posted about this on twitter this morning, and it seems appropriate to repeat it here: For most of history, governments have not had the ability to easily monitor the communications of their citizens. Widely available, user friendly encry
473.
by ryan-c 10y ago
Anyone have a better guess than "Foxconn" as to who this guy was impersonating?
474.
by ryan-c 10y ago
I'm pretty sure that's exactly what they figured when they designed it in the first place, and here we are many decades later, still living with it.
475.
by ryan-c 10y ago
> plus one more feature I’ve always wanted: the ability to generate a keypair from a passphrase No. This is a bad feature. It turns your public key into a password hash, subject to cracking. This is a major footgun. Someone implemented t
476.
Missing $10,000 package of PAL SNES games recovered(byuu.org)
366 points by ryan-c 10y ago|117 comments
477.
by ryan-c 10y ago
It was just a random example, but a couple years ago I found 250 BTC with a private key of sha256("how much wood could a woodchuck chuck if a woodchuck could chuck wood"). People use quotes from movies/tv/books/etc
478.
by ryan-c 10y ago
A problem with zxcvbn fails badly at passphrase evaluation - for example it will claim "all your base are belong to us" would take centuries to crack.
479.
by ryan-c 10y ago
My suggestion for you (which I would not give on /r/personalfinance) is that you actually try running the numbers on that - it should be fairly straightforward. Look up "amortization" if you need to.
480.
by ryan-c 10y ago
They don't forward packages for change of address.

More ›