Making Twitter More Secure: HTTPS

HardOCP News

[H] News
Joined
Dec 31, 1969
Messages
0
According to the official Twitter blog, users now have the ability to switch to HTTPS full time. Not sure why they are waiting but the company says they have plans to make HTTPS the default setting in the future.

To turn on HTTPS, go to your settings and check the box next to “Always use HTTPS,” which is at the bottom of the page. This will improve the security of your account and better protect your information if you’re using Twitter over an unsecured Internet connection, like a public WiFi network, where someone may be able to eavesdrop on your site activity. In the future, we hope to make HTTPS the default setting.
 
Yes because your inane drivel is of such critical importance that your connection must be encrypted... :rolleyes:
 
My guess is load capacity. Twitter is often over capacity as it is, as in the site is literally unavailable at times.

Enforcing HTTPS on all user would compound the problem unless they are offloading SSL on hardware based device.
 
My tweets better be encrypted on the way to Twitterland where anyone and everyone can see them anyway. I don't get it.
 
Well, I guess maybe because some of the high profile Twitter hacks (a couple celebrities). Of course, encrypted or not, using a password of "1234" or "password" or "charlielovescoke" probably isn't going to help.
 
Not all tweets are public.

You can create a private group and only members of the group can see the tweets.

My tweets better be encrypted on the way to Twitterland where anyone and everyone can see them anyway. I don't get it.
 
it seems like it should be common sense to use https whenever logging into any website, considering how many people use the same email, username, and password for many websites
 
My guess is load capacity. Twitter is often over capacity as it is, as in the site is literally unavailable at times.

Enforcing HTTPS on all user would compound the problem unless they are offloading SSL on hardware based device.

Even hardware based devices have limits on SSL. One of the hardware load balancers we have set up for one of our apps can handle 100,000 simultaneous HTTP requests. It can only handle 500 simultaneou SSL requests. It just takes more processing power.
 
it seems like it should be common sense to use https whenever logging into any website, considering how many people use the same email, username, and password for many websites

They do use HTTPS for logins. The debate is whether all communications, including status updates, should be encrypted.
 
Twitter is generally spam, but where it does come into it's own is through disaster updates IMO.
 
Why not till now?
- Depending on the system going from http to https is a 10 to 100 times more CPU load to encrypt every byte.
- Why bother since twitter traffic is mostly public? Identity theft / account hijacking.. on HTTP even with HTTPS logins it is easy to hijack an active session and impersonate a user. Most account systems require the users password again to change it but it might be possible to flip other settings when hijacking a session
 
I'm not going to knock this move. They're using better encryption than most banks do (256-bit with EV), which to me is cool if not generally pointless. They're paying for the stuff, so I'll gladly take advantage of it. Why not, right?
 
You can automatically code this firefox addon so that when you go to any site you don't have to put https in the beginning. Has a lot of ones already preset in the addon. Just have to edit the file it says to edit to add more if you want to.

http://www.eff.org/https-everywhere

One of the best I've seen for making your browsing more secure :)
 
Back
Top