If you use Bitcoin or other payment method simply email me.
You may be interested in a Bitcoin-based merchant service provider, depending on how much time you want to spend on integrating one with your site. That would allow for more automation. Two examples are http://paysius.com/ and http://bit-pay.com/
|
|
|
Closed due to lack of interest.
|
|
|
It seems you are the one not to understand how things work. Not even going to argue this with you. It's really not worth it lol
Oh? You have your own Rackspace account, and you can log in and tell me how it works? I do, but I am not going to waste any more of my time explaining things to a brick wall.
|
|
|
My pictures get posted all the time on /b/ For research purposes only, which ones might those be?
|
|
|
If it doesn't follow Moore's law, shouldn't it be called NOT-MOORE?
|
|
|
Apparently, Zhou Tong, wich had access to the server "temp" folder holding the session data, didn't knew how to invalidate a php session also. Are you trying to tell me that Rackspace still had root access to that server? Pretty slick, actually... Or are you trying to say that the Virtual Machine is not suited to host such a website? Even more slick. One way or the other, their fault, and I don't mean Rackspace No, what I am saying is that the admin console/portal is hosted by rackspace themselves, not bitcoinica. It is the page that allows them to provision new hardware, file support tickets, creeate backups, etc. Bitcoinica has no access to those servers for obvious reasons (other RS customers use the same portal). blah blah blah... Stop kissing Zhou tongs ass, dude. Now tell me: How much money do you have hostage in Bitcoinica at this exact moment? Jesus Christ, I am not responsible for how badly Rackspace fails at server administration, I'm just telling you how the fucking setup WORKS. If you can't comprehend how it works, you have no right to be placing blame. Now obviously, using cloud services in this manner was not a good idea, and there should have been some actual dedicated hardware in use, in a locked cage, "blah blah blah", but it's too late for that now.
|
|
|
Apparently, Zhou Tong, wich had access to the server "temp" folder holding the session data, didn't knew how to invalidate a php session also. Are you trying to tell me that Rackspace still had root access to that server? Pretty slick, actually... Or are you trying to say that the Virtual Machine is not suited to host such a website? Even more slick. One way or the other, their fault, and I don't mean Rackspace No, what I am saying is that the admin console/portal is hosted by rackspace themselves, not bitcoinica. It is the page that allows them to provision new hardware, file support tickets, create backups, etc. Bitcoinica has no access to those servers for obvious reasons (other RS customers use the same portal).
|
|
|
Or if I had 1 person logging in the # of rounds can be high for little cost, but if I had 5 Million people logging in, then the # of rounds becomes a financial question in terms of hardware.
If you have 5 million users, you should have dedicated authorization hardware. And yes, those that use the password "password" or "abc123" deserve to be hacked, because that isn't going to stop someone with a bcrypt database and salt in hand.
|
|
|
The terrible thing is, Rackspace refused to I didn't log the hacker out. They I (still) don't know how to do it.
Fixed that shit for you. Was that a managed server? How much did you pay monthly/yearly to Rackspace for managing the server for you? Um psy, do you know how a cloud works? Virtual machines. Suspend it, and it stops responding - same as physical hardware being put into sleep mode. Even though this was done, the cracker had access to the RS admin console, which is something that they have hosted on their own infrastructure. Apparently they don't know how to invalidate a php session, and so the cracker was able to spin up a new VM instance and load a backup and away goes Mabel with all the data.
|
|
|
It got to be such a huge business that most of the proportional pools finally gave up the ghost or switched to a different method. The major exceptions are Slush, who can still be hopped regardless of his special time weight if you have enough hash to throw at him, and Deepbit, who still offers prop at 3% and PPS at 10%. And Slush is planning to move to DGM like ozco, EMC, etc. but hasn't finished the move yet.
There still may be some small prop pools around, but most of them are either too small to be worth it, or they ban hoppers.
By "have enough hash to throw at him", would ~5.75GH/s be sufficient? I'm putting together a 7x 7970 rig atm. So, if I wanted to at least look into continued hopping with the client I paid for ages ago (CherryPicking), I should check on Slush and Deepbit.. any others I should look into? Well, I don't know the mathematical stuff about it, but if you check out his hash rate you will find that it is surging by upwards of 400 gigahashes per second after each block. I don't know if all of that is necessary to make it happen, but it isn't quite as simple as the 40% stuff that you can use on a standard prop pool. However, organofcorti or Meni Rosenfeld could probably elaborate on what's needed to effectively hop on Slush's pool.
|
|
|
I'll take this one too. I sent you a pm.
lolwut, stocking up for the zombie apocalypse?
|
|
|
dwolla always asked for the photo id verification and if you didn't hit the flag from dwolla this week you will hit it next week so either way they will ask you to provide the photo id. mtgox i think its fair if you stay above the limits they will not ask for the photo ids but if you like to upgrade you might consider giving them the verification details.
I think you misunderstand. Mt.Gox now requires verification to transfer any amount using Dwolla. Effective from Friday 25th of May, any user using Dwolla via Mt.Gox will be required to own a Verified account. So now, all Dwolla is is another PayPal with a useless number system that is even less intuitive than PayPal's own email system. ("Hey guys, send me some money, my number is 123-456-789! No, you can't use my email address because the platform I am using is shit.")
|
|
|
bullshit noise
Couldn't you at least have had the common decency to take it away from this thread as Loup asked you to ever so politely? Also, your arguments are invalid. Your extremely questionable judgement has me worried as well.
|
|
|
Err, pull the plug for the whole dedicated server is that hard?
If I'm not mistaken, it was hosted on RS Cloud Servers (similar to AWS), and I assume that shutting it down would destroy valuable evidence that could remain in memory.
|
|
|
I spy with my little eye... a Lenovo 60 watt AC adapter.
|
|
|
It looks like that arrangement is OUTside of your house, is it? I see an outswing door and a concrete step, as well as siding material.
|
|
|
We need them to be perma-banned, IP or otherwise.
I'm pretty sure they are all over that. Heard of a proxy before? And here I thought that bitcointalk already bans most TOR out nodes. Tor isn't the only proxy... also (apparently) Tor is only disallowed for signups, not regular access.
|
|
|
We need them to be perma-banned, IP or otherwise.
I'm pretty sure they are all over that. Heard of a proxy before?
|
|
|
The next release (after 2.4.1) will have that fix in it At the moment it just puts an extra comma in the config file if you have no GPUs (... just remove the extra comma)
Great, thanks.
|
|
|
Gavin i read the link that you gave me and as far as i know this was a phishing attack according to this phrase : "Our investigation has revealed a customer support interface was used to access your account" meaning the wallet used was ewallet shared on a server.
It was the same incident as Bitcoinica's first 40K+ heist - the cracker(s) compromised the Linode account manager login and reset the root passwords on 8 different boxes, one of which happened to be the Faucet machine.
|
|
|
|