Exactly, although it is not always possible to identify those US servers (on US territory or not), some IP are well known but if they are not totally idiot they must also run from "innocent" IP servers. Tor is one of the few remaining stuffs that works (with freenet, I2P, JAP used to be good until they used backdoors, removed now but unpopular since), but it has its limits (global attacks, exploits of js, injections of scripts, etc.), and the lattest version is a little fiasco, Windows had Vista and Tor has its version 4.0
I feel unsecure browsing akiba, a website like this one should definetely support HTTPS. A SSL certificate is like $100 a year max nowadays. Heck i'd feel better browsing Akiba on a self signed certificate than over nothing. Is there any plan for it?
if i enable https, there are some things we first have to do. and what's a bigger problem: In Order to get a green ssl-icon i have to tunnel all and every picture, link etc. thorugh https, which means proxing at least all pictures linked in the board, that are not attachements, which means our traffic will rise again, and we have to pay for it which means, some hosts will bann us, since all requests will come from one of our backend-servers and not from the user itself, -which means some have to change the hosts, while there are old ones not working, -which means more hassle about everyhting which means we have to pay more for the traffic -which means: we don't have that much ressources left, since there isn't a sponsor atm which means: we could take donations, but there are some severe limitations of methods we can use but we can wait a bit, what google and firefox will do with their new ssl-thingy, or we can use startssl as cheap althernative. but then again the problems above are still valid. moreover: the only thing why ssl is a good option is to get a better google-ranking. see the posts of ceewan & co
I want to repeat the things I already wrote in my post earlier: The [IMG] and [MEDIA] BBCode also have to be disabled. Otherwise it would break what you want to achieve with HTTPS.
Not all that unlikely since the majority of certificate authorities are located in the US all it would take is a few National Security Letters. Or they could by the same method have forced a cryptographic weakness to be included in the protocol itself, one that wouldn't be readily noticeable unless you know exactly what to look for. Anything cryptography related coming out of the US these days should be highly suspected unless it's open sourced(including the encryption scheme).
Fear does the governments work of suppression for them. If one thinks https is cracked than why bother? Read up a bit on encryption and decryption techiniques though and you see just how implausable it actually sounds (and I assume we are talking "decryption on-the-fly"). It is not as easy as having the right key to open a locked door or having the correct combination for a safe. An academic argument though as no proof has been offered either way. Happy Holidays!
