Combine this with exploits into one or more broadly trusted certificate authorities (which surely exist) and it's pretty amazing how much data China would have been able to obtain.
Every time I bring up the following point someone chimes in that it's a bad idea, but I still fail to understand why it's not easy to pick which CAs I want to trust by picking a list of entities/people I trust and then adopting their recommendations for which CAs to trust.
This would be a few clicks of UI to let me be intelligently paranoid while maintaining only a layperson's understanding of why (say) Bruce Schneier decides to trust some and not others.
This should absolutely be exposed in browser UIs, esp Firefox which uses its own store. Why can I not easily select/deselect all, sort by country of origin, issuer, plain text search filters, and so on? The ability to click-through, or even to simply display the "insecure" badge, would still be there.
Or, as you said, being able to subscribe to other recommendations would be cool.
> Combine this with exploits into one or more broadly trusted certificate authorities (which surely exist) and it's pretty amazing how much data China would have been able to obtain.
The attacker doesn't even need to compromise a CA.
If someone hijacks the IP address of example.com, he could easily get a valid Let's Encrypt certificate for that domain.
The party you want to connect to chooses the CA, not you. Are you really not going to use YouTube because you don’t trust the Google CA?
Anyway, redirecting and sniffing traffic is one thing, intercepting and changing encrypted traffic while being undetected is another. It’s quite a stretch really.
I'm continually amazed at how insecure almost every aspect of internet routing is - it mostly boils down to a sort of "gentlemen's agreement" that everybody will follow the rules.
Such is the nature of BGP. Something like SPF (eg: an authorized AS list for an IP block) and DMARC (reporting about who tried to broadcast what IP block and was rejected) would be great, perhaps even have the latter component convey attack info so ISPs could deal with infected clients automatically.
Basic security mechanisms when it comes to large ISP networks are a pipe dream though, instead we get vendors pushing extremely vulnerable Juniper gear cause its reasonably priced, meanwhile these boxes have new root exploits found multiple times a year. None of the vendors give a crap about security, Cisco pays it some lip service (to win gov't contracts) but charges a premium for basic features.
Internet routing (BGP), SMTP, and DNS (not inclusive, just off the top of my head) were developed during the very beginnings of the internet, without much thought into today's use and scale.
Today you'd do better, with hindsight being 20/20.
I'd like to point out that government used to run by agreements that were like that, and look what has happened in that domain. I say this as a warning what the internet could become.
CT and Chinese ISPs have been hijacking user traffic for decades, profiting off of it by selling traffic dump to data exploiting companies, insert ads in webpages, steal social media tokens (for follower boosting and ads retweeting).
> Go ahead, monkey around with BGP, since I have the public key of the recipient of my packets I can detect this and block any type of misdirection.
And how did you get that public key?
An attacker could pretty easily obtain a valid Let's Encrypt certificate using a BGP hijack.
Also, the CA system is in bad shape - CAs have been hacked and certificates were leaked. Not to mention that some of the CAs your browser trusts are not entirely trustworthy or are located in untrustworthy countries. Oh, and from time to time there are attacks against TLS itself (e.g. https://drownattack.com/)
I would guess that the author copied the results into a table and prettified them and added in details like location.
At the top of the screenshot it says "traceroute from London to ..." - no traceroute program knows where it is in the world!
Also the locations of each hop in traceroute NY > Chicago > Ashburn etc., no traceroute program will know where in the world those IPs are. I suspect the author has guestimated based on the reverse DNS record for the IPs and latency.
Traceroute does have the ability to show you the ASNs in a path but that is based on a WHOIS lookup of the IPs that it's discovering. So it could be wrong by assuming the IP address of each hop was announce by the ASN that owns it.
Tangent, but are traceroutes spoofable (barring timing differences), or would they break too many other things to be practical? I'm wondering if anyone might do that to hide their tracks.
I just don’t understand why the telecom agreements are not reciprocal. If no foreign nation is allowed to put a POP in China, then why is China allowed to put POP’s all around the world?
Its not as though our domestic technology vendors care about security. JunOS is constantly having new vulnerabilities found, and Cisco ain't much better, but charges a premium price as they are viewed as the market leader and pay some lip service to security.
[+] [-] resters|7 years ago|reply
Every time I bring up the following point someone chimes in that it's a bad idea, but I still fail to understand why it's not easy to pick which CAs I want to trust by picking a list of entities/people I trust and then adopting their recommendations for which CAs to trust.
This would be a few clicks of UI to let me be intelligently paranoid while maintaining only a layperson's understanding of why (say) Bruce Schneier decides to trust some and not others.
[+] [-] unethical_ban|7 years ago|reply
Or, as you said, being able to subscribe to other recommendations would be cool.
[+] [-] jopsen|7 years ago|reply
Nothing is more embarrassing than getting caught with your fingers in the cookie jar.
Besides I trust CAs will be de-listed if proven compromised.
[+] [-] maltalex|7 years ago|reply
The attacker doesn't even need to compromise a CA.
If someone hijacks the IP address of example.com, he could easily get a valid Let's Encrypt certificate for that domain.
[+] [-] tinus_hn|7 years ago|reply
Anyway, redirecting and sniffing traffic is one thing, intercepting and changing encrypted traffic while being undetected is another. It’s quite a stretch really.
[+] [-] gcb0|7 years ago|reply
having to manually select/add CAs is akin to not having ssl and using pgp everywhere. and you know how well that works out even for technical folks.
[+] [-] raquo|7 years ago|reply
Actual experts aren't respected by the general population enough for this to be a net positive change is my guess.
[+] [-] aaaaaaaaaab|7 years ago|reply
[+] [-] cwkoss|7 years ago|reply
[+] [-] freeflight|7 years ago|reply
[+] [-] commandlinefan|7 years ago|reply
[+] [-] StudentStuff|7 years ago|reply
Basic security mechanisms when it comes to large ISP networks are a pipe dream though, instead we get vendors pushing extremely vulnerable Juniper gear cause its reasonably priced, meanwhile these boxes have new root exploits found multiple times a year. None of the vendors give a crap about security, Cisco pays it some lip service (to win gov't contracts) but charges a premium for basic features.
[+] [-] toomuchtodo|7 years ago|reply
Today you'd do better, with hindsight being 20/20.
[+] [-] jgrahamc|7 years ago|reply
[+] [-] magicbuzz|7 years ago|reply
[+] [-] cm2187|7 years ago|reply
[+] [-] e40|7 years ago|reply
[+] [-] cauldron|7 years ago|reply
I've found China Unicom openly hawking their data mining products. https://imgur.com/a/uNxA50K
[+] [-] hrrsn|7 years ago|reply
[+] [-] burtonator2011|7 years ago|reply
Go ahead, monkey around with BGP, since I have the public key of the recipient of my packets I can detect this and block any type of misdirection.
[+] [-] maltalex|7 years ago|reply
And how did you get that public key?
An attacker could pretty easily obtain a valid Let's Encrypt certificate using a BGP hijack.
Also, the CA system is in bad shape - CAs have been hacked and certificates were leaked. Not to mention that some of the CAs your browser trusts are not entirely trustworthy or are located in untrustworthy countries. Oh, and from time to time there are attacks against TLS itself (e.g. https://drownattack.com/)
[+] [-] martinald|7 years ago|reply
[+] [-] jwbensley|7 years ago|reply
At the top of the screenshot it says "traceroute from London to ..." - no traceroute program knows where it is in the world!
Also the locations of each hop in traceroute NY > Chicago > Ashburn etc., no traceroute program will know where in the world those IPs are. I suspect the author has guestimated based on the reverse DNS record for the IPs and latency.
Traceroute does have the ability to show you the ASNs in a path but that is based on a WHOIS lookup of the IPs that it's discovering. So it could be wrong by assuming the IP address of each hop was announce by the ASN that owns it.
[+] [-] mirimir|7 years ago|reply
[+] [-] mehrdadn|7 years ago|reply
[+] [-] nrki|7 years ago|reply
See also: https://news.ycombinator.com/item?id=5192656
[+] [-] localguy|7 years ago|reply
[+] [-] cronix|7 years ago|reply
http://www.circleid.com/posts/20181105_china_telecom_accused...
[+] [-] DevoidSimo|7 years ago|reply
[+] [-] walrus01|7 years ago|reply
[+] [-] zozbot123|7 years ago|reply
[+] [-] baybal2|7 years ago|reply
[+] [-] furkitolki|7 years ago|reply
[+] [-] ggm|7 years ago|reply
[+] [-] unknown|7 years ago|reply
[deleted]
[+] [-] jmartrican|7 years ago|reply
[+] [-] consumer451|7 years ago|reply
[+] [-] olliej|7 years ago|reply
[+] [-] StudentStuff|7 years ago|reply
[+] [-] gcb0|7 years ago|reply
[+] [-] praneshp|7 years ago|reply