For images, sure. Not so much for actually passing their client's data through.
GLBSE used cloudflare I think. So I guess if people didn't mind then, they won't mind now. I won't be using it in my projects though. I'd rather go offline to a DDoS than risk customer data to a 3rd party.
Cheers.
It is a good thing we are not passing any sensitive data such as SSN's, credit card numbers, addresses across it to BitFunder then.
If you are worried about passwords being sniffed or man in the middle attacked by CloudFlare itself, or any other network hop in between, then
you should be just as worried about who runs the network in Panama where your server is. I think a local ISP (Like the Linode incidents) that
probably has no auditing or accounting of tech actions is FAR more likely to review a customers website, sniff their data, learn what they do,
and possibly attempt steal any valuable information or in this case, bitcoins than a company as large as CloudFlare who does not even have
access to the server's and that could care less about small time websites that never even show up on their radar.
I would not trust any bitcoin related services to be housed where I did not maintain the servers. Then again, with the linode and other incidents,
I don't think people bother to consider things regularly and ask every site about server security. Probably much the same as they are probably
not worried about CloudFlare securely transmitting their data, and acting as a shield to help prevent all sorts of extra vulnerability attacks such
as being a proxy. It appears you run Apache on your servers, which like most all web daemons has been know for .. at least a few..
major vulnerabilities.
Having a proxy server helps protect the actual servers from most vulnerabilities. If you are not going to use cloudflare, you should at least setup a
reverse proxy of your own in front of the server to protect it.
GLBSE did switch to CloudFlare (and also ran proxies of his own), just as MTGox did for a while. Gox needed a better and more advanced
system than CloudFlare of the time, and switched to Prolexic (I believe). I hope no one at prolexic get's any crazy ideas. Although, I feel
as confident as one can given the situation that Gox's system also has protections in place for this type of situation. I think Mark has
made so to do everything necessary to protect users data and accounts.
Thankfully for us, we do not have any coin wallets tied to the website. So in the slim remote chance that a cloudflare employee decides
to go rouge and risk their job/freedom (not that this has stopped people before) to get a users password to login, there is nothing for
them to gain out of doing so. That is one of the best things about BF. I am setting the site up currently so that 2-fa users could even give
out their user and passwords should they so desire, and people would not be able to do anything with their accounts. (Using means above and
beyond just 2-fa)
I would be more afraid to pass, and put sensitive user data on a $45.99/mo server in another country where I do not know who might mirror hard
drive data at any time, have physical console access to the server/console, and who knows what else.
I would ask as I stated before in the BTCT thread where you also began to cross-post this stuff in, that these types of conversations be be
continued on IRC. I would be happy to continue answering your concerns on how BitFunder is different from BTCT in many ways on IRC as it
really does look like childish public mudslinging to quite a few people as I pointed out there already.
http://polimedia.us/dtng/c/res/17830.htmlI have no intentions to continue these 'back and fourths' in some vain attempt to try to convince, each other? the public? who's ideas are better and why.
I think the whole thing has made us look like fools. Not that it is anything new for me.
As I said in the other thread, and now again, I will be happy to talk to you on IRC about these things and perhaps we can really learn from and help each other.
I have taken quite a few notes from BTCT that I think are great ideas that I plan to implement on BF as well.
Cheers.