18 ms·
They're spoofing identity of non-consenting parties. The cause is noble, but it isn't what the headline would imply. Amazon isn't saying "You can't host encrypt
by unethical_ban 9y ago
They're spoofing identity of non-consenting parties. The cause is noble, but it isn't what the headline would imply. Amazon isn't saying "You can't host encrypted services on our platform", they are saying "You can't use TLS and load balancing hacks to pretend to be us in oppresive countries".
And
>The idea behind domain fronting was that to block a single site, you’d have to block the rest of the internet as well. In the end, the rest of the internet didn’t like that plan.
That they interpret AWS and Google as "the rest of the Internet" is pretty sad, too.
- colechristensen 9y agoIt is not that much of an interpretation. When us-east has problems a huge proportion of Internet sites that people actually use goes down.
- kempbellt 9y agoI agree. The intent is noble, but this headline makes Amazon look like the bad guy for disapproving unauthorized use of one of their domains, which is quite reasonable.
- gue5t 9y agoHardly reasonable. Domains are (in reality, if not in legislative fantasy) property of ICANN and merely rented by everyone else.
- CoryG89 9y agoSo? If we qualify it to preventing unauthorized use of one of their rented domains does that make it any less reasonable?
- caf 9y agoThe conceit here is that you must be "authorized" in order to write an app that puts the domain in question into the SNI field of a TLS connection that it initiates. I don't think that's reasonable. It is of course up to Amazon what their servers then do when presented with such a connection, in particular whether they ensure the Host: header later presented matches the SNI data.
- bdcravens 9y agoSo have they obtained the permission of ICANN? I rent my home, but I still call the police if there's a trespasser.
- mpartel 9y agoAmazon and Google are certainly within their rights to refuse this. Allowing domain fronting is likely to put quite a lot of their money at risk, so this outcome is unsurprising, but it's still the less ethical one. This might be the only possible outcome given a corporation's legal responsibilities to its shareholders etc, I don't know all that well enough, but I think it's still justified to lower my opinion of Google and Amazon because of this.
- mpartel 9y agoI realized I glossed over the fact that this would put other AWS/GAE customers's money at risk too. This complicates matters somewhat, and some (I believe a negligible number of) customers might switch to an unblocked competitor. Personally this weakens my view a little, but is not enough to change it substantially.
- nerpderp83 9y agoThe ethical choice is for AWS and Google to collude and both allow signal to continue to using domain fronting.
- toomuchtodo 9y agoGreat PR opportunity for Cloudflare to pickup the torch. EDIT: Not supported by Cloudflare.
- komuW 9y agoCloudflare is against domain fronting https://arstechnica.com/information-technology/2018/04/google-disables-domain-fronting-capability-used-to-evade-censors/ https://arstechnica.com/information-technology/2018/04/googl...
- illumin8 9y agoDespite the use case for censorship circumvention, many malware command and control bots use domain fronting to bypass corporate web filters that otherwise might block their traffic. CloudFlare, being a security-focused CDN, most definitely does not want to help enable malware authors to bypass security.
- iforgotpassword 9y agothe problem I'm having is that I'm not even sure this qualifies as 'use' really. sure they're putting the domain name in the tls handshake from the client side instead of their own. the handshake itself works the same, everything that happens after is the same. the tls enpoint on googles/amazons servers just makes sure the domain is in its list of known domains, nothing else depends on it.
- jasonmp85 9y agoBecause they are the bad guy.
- confounded 9y agoAm I missing something, or is anyone using a CDN domain fronting?
- icebraining 9y agoAn HTTPS connection sends the domain it wants to connect to in two layers: first unencrypted in the TLS headers, then encrypted in the HTTP header. In a regular connection (even using a CDN), those two will match. Using domain fronting, you put a popular domain in the unencrypted part, and the real domain in a encrypted HTTP header. Due to how they're implemented, the load balancers at Google and Amazon will ignore the first (unencrypted) layer, and will send the traffic to the correct server based only on the encrypted HTTP header. Regular browsers always send the same domain in both layers, only a custom app like Signal can perform domain fronting.
- bscphil 9y agoWhat if Signal sent the correct domain by default, but made it user configurable? Users in oppressive regimes would figure it out pretty quickly.
- icebraining 9y agoMy guess is that Amazon would say "we're not idiots" and shut down their Cloudfront account anyway.
- joombaga 9y ago> only a custom app like Signal can perform domain fronting. Or curl, or openssl s_client. I'm still trying to understand domain fronting, and exactly what is being disallowed now. Do all of my CDN requests have to have identical Host headers and TLS server name indicators now? What if they're mismatched? Does the TLS handshake still succeed, and the traffic just doesn't get passed through the CDN server?
- icebraining 9y ago
- 2close4comfort 9y agoSo AWS finally lost enough money to the Russian blockade that they caved. Sad.
- nasredin 9y agoRussian economy is very very small. Whatever Amazon's reason is it's not that they lost some Russian banks for a week.
- angry_octet 9y agoThe same technique is being used to prevent censorship in a host of countries, like UAE, that have giant piles of cash and influence, and where blocking AWS/Google would have unacceptable consequences. No one gives a damn about a few Russians.
- avip 9y agoSpot on. How about "Amazon threatens to suspend Signal's AWS account over CloudFront ToS violations".
- andrepd 9y agoMorally, it's still the right thing to do, even though I guess it's in amazon's best interests not to allow it.
- analognoise 9y agoHow is it moral for Amazon to shirk their fiduciary duty to shareholders for the sake of a political battle it isn't theirs to wage? I counter it would be more immoral to put, say, the retirement funds of firefighters and teachers arty risk to achieve what is the responsibility of, say, the State Department?
- tanderson92 9y agoThere is no fiduciary duty to shareholders of a public company. This is known as the shareholder value myth -- myth because it is false.
- jessaustin 9y agoYeah if this were the case the private jet market would crater.
- adventured 9y agoBerkshire Hathaway could have never existed if it were actually a legal requirement. For decades they've constantly passed on doing things that could have easily juiced shareholder value, including hostile actions in regards to takeovers. It's why nearly all of their acquisitions come to them instead: an extraordinary reputation. Further, the fiduciary myth is silly as a premise upon any inspection: legally who gets to decide what's the one right ideal path for optimizing shareholder value, such that if you don't follow The One True Path then you're failing shareholders. Any other path than the single best one, would be inherently defined as failing the fiduciary responsibility to maximize shareholder value (which is another way of saying: legally it's an impossible concept to implement; and logically it's stupid, it falls down instantly, no person could know the maximization path at all times). It doesn't pass even a minute of rational intellectual scrutiny.
- dragonwriter 9y ago> The cause is noble The cause is noble, but the mechanism is dubious: it can be viewed as, in effect, saying to oppressive regimes “to harm me, you must harm a bunch of innocent bystanders, too”.
- deleted 9y ago[deleted]
- tonyztan 9y agoThat's the entire point of domain fronting and collateral freedom: to make censorship as expensive as possible for oppresive regimes.
- creddit 9y agoI think it's quite clear what the point is from Signal's attempt at implementation of the theory as well as your freshly minted wiki page. That doesn't change the dubious nature of it. Putting other valuable services at risk for a single service's gain is clearly dubious.
- tonyztan 9y ago> "your Signal" Just to be clear, I am not affiliated with Signal in any way. I am just a user. > "your freshly minted wiki page" I am a regular contributor to Wikipedia, and I created the article on "collateral freedom" in January 2017[1] when I came across the topic because it satisfied Wikipedia's notability guidelines.[2] [1] https://en.wikipedia.org/w/index.php?title=Collateral_freedom&action=history https://en.wikipedia.org/w/index.php?title=Collateral_freedo... [2] https://en.wikipedia.org/wiki/Wikipedia:Notability https://en.wikipedia.org/wiki/Wikipedia:Notability
- creddit 9y agoThat was a typo (now fixed). Didn't mean to imply you were involved with Signal
- 9y ago
- dice 9y ago>You can't use TLS and load balancing hacks to pretend to be us in oppresive countries They're not pretending to be Amazon, they're pretending to initiate a connection to an Amazon domain. The "conversation" goes like so: Clear text request: "Hello, I would like to speak TLS with souq.com" Clear text response: "Why yes, let us do that with these parameters" Encrypted request: "Please give me the page for signal.org/api/whatever" etc...
- simias 9y agoThey're arguably impersonating Amazon on the server side by hosting their service behind Amazon's proxies and using a trick to pretend that they're talking to some Amazon service instead of their own.
- zaroth 9y agoThe beauty of this is they are not doing anything on the server side to impersonate or spoof Amazon.
- collinmanderson 9y agoRight, it’s the _client_ side that’s tricking Amazon’s servers. It seems to me Amazon should just close their loophole rather than threaten to kick signal out of the server side.
- s73v3r_ 9y agoAccording to the article, that's exactly what they're doing.
- simias 9y agoYou're right of course, my comment was too short and factually wrong. What I meant was that what they're doing is effectively renting office space in Amazon's building and then exploiting a loophole in the way mail is distributed to receive packages even though the outside envelope says "c/o amazon.com" (or c/o souq.com in this case). So while they don't do anything fishy on the server side they still took care to put their servers there for a reason. And since they also write the client code it's not difficult to show that the intent is to impersonate Amazon to 3rd parties. Interestingly it seems that amazon couldn't really complain if the people writing the client were independent from those maintaining the servers since the spoofing code is entirely in the client. Although in the end I'm sure if it turned out to be a problem for they they'd just enforce that the domains match the HTTPS query and remove the technical possibility of fronting altogether.
- tony101 9y ago> "They're spoofing identity" That's the entire point. By making it impossible for censors to distinguish Signal traffic from other web traffic going to AWS, domain fronting forces the government censors to either 1) stop censoring, or 2) censor many important websites that people rely upon. The associated economic cost has the tendency to discourage censors, and as shown by Signal, is actually quite an effective deterrent against many oppressive regimes. This concept is known as collateral freedom.[1] Instead of shutting this down, Amazon could have let Signal continue. In fact, all companies should collaborate to make censorship as expensive as possible. Someone here at HN pointed out that it is very difficult for someone under an oppressive regimes to speak out; this makes it all the more important for those of us who can to assist dissidents and support freedom of expression. [1] https://en.wikipedia.org/wiki/Collateral_freedom https://en.wikipedia.org/wiki/Collateral_freedom
- sakarisson 9y agoBut isn't Amazon risking that Souq itself might get banned in these countries if they allow this to happen? Or am I understanding it wrong?
- mattigames 9y agoExactly, free countries (or those who consider themselves as such) should make it fully illegal for private companies to aid in any kind of censorship in behalf of oppressive countries. But what we see in reality is the opposite, all companies trying to make it as cheap and as simple as possible to censor anything every government dislikes; meaning the liberal fantasy of allowing every private company to do as it pleases is not going to cut it in a world where every important event you can't find in Google for all practical matters never happened.
- non_sequitur 9y ago"in a world where every important event you can't find in Google for all practical matters never happened" Except Google isn't in China, and least I heard important events still happen there...the world isn't as FANG centric as western media would want us to believe.
- yndoendo 9y agoReal work example would be a re-mailer. Outside of the envelope shows one address it goes to but inside where others cannot look actually has the true address? Since the plain text has the fake address while the encryption has the true address, I see no issue with this.
- TeMPOraL 9y agoA real world example would be an automated postal sorting/routing center with a bug that lets it be exploited as a remailer. By doing domain fronting, a single party is betting that this postal center is important enough not to get shut down/bombed. Obviously, the postal center isn't happy that you just put it at risk of getting shut down, because they deliver lots of other mail, none of which is obviously less important than your shenanigans. So instead, they opt to patch the bug that allows them to be unwittingly used as a remailer. The core point being: Signal isn't using Amazon as a shield - it's using every single customer of Amazon as a shield.
- smsm42 9y agoBut effectively that is the case. If major providers like AWS and Google ban domain fronting, it is effectively dead - nobody needs domain fronting when you have three domains, three domains can be banned the same way as one. AWS and Google could throw their considerable weight on the side of anti-censorship and openness. They instead chose - as businesses frequently do - to play along with oppressive dictatorial regimes so it won't cost them a couple of bucks extra. That is pretty sad.
- czardoz 9y agoAWS and Google are companies. It's not their job to push for societal changes really. In fact, I hope they don't push for those. I'd prefer them to steer clear of pushing for any higher objectives, that's best left to governments and lawmakers.
- solotronics 9y agoMaybe we should consider AWS differently than Google or FB? "to be Earth’s most customer-centric company, where customers can find and discover anything they might want to buy online, and endeavors to offer its customers the lowest possible prices." - https://www.amazon.jobs/working/working-amazon https://www.amazon.jobs/working/working-amazon "Organize the world’s information and make it universally accessible and useful.” - https://www.google.com/about/our-company/ https://www.google.com/about/our-company/ "Founded in 2004, Facebook's mission is to give people the power to build community and bring the world closer together. People use Facebook to stay connected with friends and family, to discover what's going on in the world, and to share and express what matters to them." - https://investor.fb.com/resources/default.aspx https://investor.fb.com/resources/default.aspx Its interesting how these mission statements present vastly different goals. At what point is something a public utility? If everyone abandons their servers for cloud providers you are at the whim of the corporate political stance of where your machine is hosted..
- smsm42 9y ago> It's not their job to push for societal changes really. Somehow dozens of companies are discussing pushing for societal changes every day. Just recently a bunch of companies discussed severing ties with NRA (which didn't hurt a single living soul) and stopping selling firearms (which would not, indeed, lead to any societal change but at least the declared goal, even if unattainable, is to do exactly that). In another topic, there's a link on political manifesto by SO leadership. Social activism is everywhere in the business world. But when it's about something that may save somebody's life in Iran but cost some $$ to the company, it's suddenly "not their job". Nope, you can't do both. If companies avoided social activism altogether and were completely neutral and apolitical - I could accept that. They are not and haven't been for a long time. You can't just turn on one place and say "we do social activism everywhere but not where it can offend Iran". Or, you can, but that would be, as I said, cowardly and disgusting.
- zmmmmm 9y ago> They're spoofing identity This doesn't seem quite accurate to me. They are not making an assertion that they ARE Amazon or Cloudfront. They are avoiding making an assertion that they are anybody, by using a shared facility. It's a bit like using a public payphone to avoid being identified. When you use a public payphone, presumably the call originates from a line owned by the phone company, but nobody accuses you of attempting to impersonate the telephone company by doing that. This may still be a violation of the TOS, but people should be clear about the actual intent of what is being done.
- aorth 9y agoTechnically true, but this is not really about terms of service or about "spoofing identities of non-consenting parties." This is about Google and Amazon not wanting to become collateral damage and lose business in those countries. Signal is/was connecting to Google or Amazon servers with an HTTP Host header of google.com or souq.com, respectively—and only in Egypt, Oman, UAE, and Iran! Google and Amazon could have easily allowed this or even looked the other way. So basically censorship worked, albeit not how we thought it would. Sad for people in those countries who were relying on Signal for private communication. Who will stand up for us when we lose ours due to some business decision?