Why do you bother going out all day if you could just stay home and accomplish the same thing?
|
|
|
If you search the thread, you'll find some users that claim to have discussed things with them on the phone. Maybe those users ought to give them a ring and see what's up.
|
|
|
I've been getting a U of 12.2 to 12.3 with the 880 firmware. Go GPUMAX.
|
|
|
So the POS device has the ability to empty the private key presented to it?
|
|
|
Which, I suspect, is why they abandoned the LargeCoin unit, since it wouldn't be anywhere close to what they wanted.
Did they actually? I haven't heard from them, but the website is still up. Not sure when they were planning on delivering either. The guy has chatted to some buyers on the phone, maybe they should give him a ring and see what's up.
|
|
|
Are you kidding me? Delta AFB1212. There is no reason to not use industrial fans, no cheap Chinese shit.
Well in that case, why AFB? Why not the TSB or PFB series? lol Such powerful fans need their own boards with separate power circuitry so that they don't insert all kinds of inductive shit into the ground and power planes of the main board electronics.
|
|
|
It's also not really relevant, as it describes public-key encryption (which isn't used in bitcoin) instead of signing.
OK I can see the confusion then.
|
|
|
cuntnicula still posting even though he is an idiot? Sorry to those that don't have his ass ignored.
|
|
|
I don't know... just making an observation based on knowledge that this has happened in the past.
|
|
|
If the trade engine is making an error, they are able to reverse bad trades and delete them from the live graph, which may be what is happening.
|
|
|
In order to run code in an autonomous manner, a server must store the decryption key somewhere, and a hacker can usually find it, rendering the encryption useless. Limited exceptions can be made for keys that are required on boot and not stored, but when that happens they are stored in memory and can possibly still be had by a smart hacker.
walletpassphrase won't help, because the hacker can either: scan your memory cache or just use the same session you are already using. for example, use your own JSON-RPC to send bitcoins. Exactly, and the type of attack depends on how much access the hacker has, and how he got in. If he was able to reset the root password through a control panel for instance (like bitcoinica), he would have root access to plant a keylogger or pick up the passphrase if it were stored on disk. If he broke in through a SQL vulnerability, he could grab the passphrase from memory, even if it were not stored on disk. It's a difficult kind of situation, but HSMs such as what DeathAndTaxes is looking into can mitigate the risk somewhat.
|
|
|
10 GHash/s makes 0.44 btc in 10 minutes. Why would anyone with that much hashpower spend the time to switch everything over to you just to make 0.56 btc or $3. Not really worth their time IMHO.
miners with 50+ ghash/s really ought to have a proxy in place already, which would make it very easy and painless. Centralized point of failure you say ? No thanks ! Interesting idea nonetheless. Not something controlled by someone else, but a box onsite. If coded properly, it will be just as reliable as your internet connection or more so, which is already a point of failure.
|
|
|
Seems decent, except for the "public key cryptography 101" box: analogy with a pair of keys is confusing and wrong. My favorite explanation is the one I stumbled upon on this forum (not sure if Netrin came up with it or he adopted it) - Yeah. Here's a magical analogy for public key cryptography: I generate a private key and numerous public unlocked treasure chests. I give these open treasure chests to all of my friends (it's easy to copy them). Whenever a friend wants to send me a message, they just put the message in my public treasure chest and close the lid. Now even they can not open it again. Only I, with my unique private key, can open the chest.
After I generated the public keys, I don't really need them any more, unless I want to send messages to myself. But no one needs the private key to lock a message. The private key is only required to open a message.
I don't see anything that is technically incorrect about the PKI explanation in the graphic. Do you care to explain what is wrong with it? netrin's quote is cool for the noobs, but it doesn't mean that what is in the graphic is incorrect at all. Both quotes are very correct and explained differently.
|
|
|
Your spinning flash thingy at the bottom still says Bitcoinica. Also, none of them do anything when you click them, should either make them open an associated page in a new tab, or else change the cursor to a standard one and not a hand.
|
|
|
In order to run code in an autonomous manner, a server must store the decryption key somewhere, and a hacker can usually find it, rendering the encryption useless. Limited exceptions can be made for keys that are required on boot and not stored, but when that happens they are stored in memory and can possibly still be had by a smart hacker.
|
|
|
i live in florida and i've been buying up all the ammo i can. 1000+ rnds from this thread so far. The zombies will come, the question is how much more time do we have and when will we start seeing more infections.
Someone must be getting ready to distribute mass amounts of cut LSD xD
|
|
|
|