5 ms·
What's the status of digital signature algorithms? There's much stuff that doesn't need to be encrypted because it's not secret - anybody can read the URL. It j
by Animats 3y ago
What's the status of digital signature algorithms? There's much stuff that doesn't need to be encrypted because it's not secret - anybody can read the URL. It just needs to be protected against forgery.
That's what subresource integrity is for. Only the parent page needs HTTPS. Most of the assets can use HTTP, locked to specific content by subresource integrity.
That's more useful for security than encryption. If someone changes a third party Javascript file, it won't load. This would promote a more stable web.
- magicalhippo 3y ago> Most of the assets can use HTTP, locked to specific content by subresource integrity. That's more useful for security than encryption. This is OK if you're only concerned about getting scammed. It won't work if you're concerned about your privacy. And the problem is you can't change your mind on that after the fact.
- brabel 3y agoThe point OP is making is not everything requires privacy. We shouldn't pay the (higher and higher) price of keeping privacy for cases where it's just not needed.
- lukan 3y agoBut what URLs people visit are very much private information for example. Also one of the ideas in general is, to obfuscate the really private communication by burying them in a sea of also encrypted, but trivial data. If only the very sensitive informations get encrypted, then this is also a very good filter for an attacker to ignore everything else and just go for the high protected ones.
- wh0knows 3y agoGiven domains are not encrypted I’m not sure this holds true. Attackers can already target financial websites, messaging websites, etc…
- deleted 3y ago[deleted]
- sebzim4500 3y agoNot true with ESNI. E.g. if you are connecting to a cloudflare domain an attacker can not tell which one.
- s4mw1se 3y agoI was reading up on how this worked. It’s a really good idea, and a step in the right direction 100%… cloudflare is flexing a little and this mainly works because so many people are on cloudflare. It never ceases to amaze me how complicated privacy is. From cloudflares blog [1] “ What about the IP address? While both DNS queries and the TLS SNI extensions can now be protected by on-path attackers, it might still be possible to determine which websites users are visiting by simply looking at the destination IP addresses on the traffic originating from users’ devices. Some of our customers are protected by this to a certain degree thanks to the fact that many Cloudflare domains share the same sets of addresses, but this is not enough and more work is required to protect end users to a larger degree. Stay tuned for more updates from Cloudflare on the subject in the future” [1] https://blog.cloudflare.com/encrypted-sni https://blog.cloudflare.com/encrypted-sni
- magicalhippo 3y agoMy point is what you might consider a privacy non-issue today might become a privacy issue next year. Using unencrypted communication you can't put the cat back in the bag if circumstances change.
- bawolff 3y ago> That's what subresource integrity is for. Only the parent page needs HTTPS Once you have already opened a TLS connection for the parent page, you might as well keep using it. You've already paid for it, and that way you get confidentiality in addition to integrity. P.S. because nobody actually answered. Hashes like what SRI uses are quantum safe.
- littlestymaar 3y agoYou're missing the point: it's essentially about third party dependencies/assets (say a popular framework from a CDN), and here you cannot reuse the TLS connection. Also, using HTTPS to connect to the third party doesn't prevent tempering on the third party's side, that's what SRI is for.
- bawolff 3y agoOf course you can just not do that, and then problem solved. Historically there is some performance benefit of using a separate CDN, as browsers would share the cache. However modern browsers do not do that. I suppose in theory the CDN might be geo-distributed to be very close to your user, however it seems like the latency of opening a second connection (esp. In http/2 world) would likely outweigh that unless your web server is really bad.
- hinkley 3y agoCloudfront and cloudflare can both present edge cached resources as from the origin domain can’t they? Akamai did not as I recall but that may have changed after I stopped needing to care about them.
- hinkley 3y agoThird party resources are a bane to my existence as a web user and as a person responsible for page load time. I would cry some big fat crocodile tears if that feature got removed. It’s already been curtailed a bit.
- hinkley 3y ago
- littlestymaar 3y agoTrue, although it doesn't really work in practice, because your third party resources change for non-malicious reasons a lot (they wrong doing so, it's bad practice, but bad practice are everywhere, social problems and technical solutions, you know the saying). And if you use SRI you end up with a broken website every once in a while and you need to monitor it and ship a fix ASAP (but there's always downtime if you want to make sure the change wasn't malicious before updating the signatures on your website). Nobody really cares about security, stakeholders just want a good looking enough security theater.
- Animats 3y agoRight. Server resource integrity guarantees that the other guy didn't have a break-in that put a back door into their Javascript that you're including. HTTPS guarantees the other guy controls the domain.
- Nursie 3y agoTLS and more general crypto systems largely provide three different things - Authentication, Integrity and Secrecy. Using a TLS connection should give you all three. Without the TLS connection on assets, you’re missing the secrecy element. Now sure, the data is public, but an attacker could now be in possession of information about what you’re requesting, which may leak information about which pages you’re visiting etc.
- StrauXX 3y agoYou can already provide script tags with a nonce attribute and prevent them from loading if their source changes.
- bawolff 3y agoThat is not what the nonce attribute does (you are thinking of SRI, or maybe csp hash- sources)
- eptcyka 3y agoURLs should definitely be encrypted.
- layer8 3y agoThe issue described by the article is only due to the digital signatures occurring in a TLS handshake, not due to the subsequent (symmetric) encryption of the connection (AES-GCM), which as the article explains is already considered quantum safe. That aside, digital signatures are implemented in terms of asymmetric encryption (with the roles of private and public key reversed), so the quantum safety of asymmetric encryption and of digital signatures, as well as their possible size issues, are really one and the same.
- ramchip 3y ago> digital signatures are implemented in terms of asymmetric encryption No, you're thinking of textbook RSA, which is a special case. Most signature algorithms don't work like that.
- grayhatter 3y ago> What's the status of digital signature algorithms? There's much stuff that doesn't need to be encrypted because it's not secret - anybody can read the URL. It just needs to be protected against forgery. This is obviously not true, what leads you to claim the URI is never sensitive or protected information?
- deleted 3y ago[deleted]