interesting how something so trivial as sockets (but in the context of a http browser) can stir so much talk of decentralization. maybe if people pull their heads out of their asses about web and embrace native apps again...
Agreed. A P2P program with a browser? Come on! We /already have/ wonderful P2P programs. I sense browsers becoming awfully bloated. And for who's benefit? Google's.
I would imaginr that the flat panel could be hooked to a servo and a control loop be used to optimize poiting attitude in real time to compensate for the sun's natural cycle.
Old joke: If you owe the bank a thousand dollars and you can't pay it back, then you have a problem. If you owe the bank a billion dollars and you can't pay it back, then the bank has a problem.
It'd have to get very bad for China to pull out. If China pulls out and damages our economy, our imports will dry up, their exports will dry up and their economy will dry up. I understand that China and the US might not be the best of friends right now, but their interests are generally aligned on US debt.
Its really not. If what you say was true they wouldn't still be actively buying U.S. Debt.
Their hesitation is they wouldn't get all their money back. If China pulled even 25% of its investments out of the U.S. the dollar would free fall. They wouldn't be able to cash out before most of the dollars value was inflated away.
China continues to buy our debt because they don't want the value of their current investment to collapse
This says a lot about the ISP's ethics if they are shown to be consenting to this. One thing I didn't see in the EFF article is something a user could do about it: use SSL! This may eventually force these companies into more nefarulious and active techniques of hijacking, but it should alleviate the basic technique they are employing now, if i am not mistaken.
"And the best protection against the privacy and security risks created by this type of hijacking is to visit sites using HTTPS rather than HTTP, which can easily be achieved using EFF's HTTPS Everywhere Firefox extension"
I don't know why you were downvoted for this, it's a very cogent point— most users would probably click through a big red screen that says "DO NOT VISIT THIS WEB SITE!" We need to be thinking of them when we design our security model.
This is something I keep circling around. The host doesn't seem like a thing you could encrypt, because the intermediaries need to know where to send your packets. It seems like https encrypts the headers: http://stackoverflow.com/questions/187655/are-https-headers-...
but does this include the Location header?
The HTTP request itself is encrypted, but the IP packet (including the source and destination IP addresses) is not. SSL/TLS is application level encryption, and if you wanted to encrypt the actual packet, you need to switch to something like IPsec, but even then you need some sort of routing method (which I can't remember).
IPSec can work in many different ways. One of those is to encapsulate the entire packet as the encrypted payload of a new packet, with the new packet having headers in plain text leading to the other end of the IPSec tunnel. That other end will then decrypt and forward as appropriate (this is called a 'tunnel').
Yes.
SSL / TLS happens below HTTP at the socket layer. This is why you couldn't have vhosts's using SSL on a single IP for a very long time (the webserver wouldn't know which certificate to use).
It was proven on the last jailbreak-via-web - it was amazing to see it work the first time and you really understood the severity of a simple bug. I think it's news now for many people (perhaps not a large bunch of HNers) because the first time was "huh - pretty crazy! But I'm sure it won't happen again" and now it's "holy shit, there IS no security!"
