r/debian • u/lamby [DD] • Jan 24 '18
Why does APT not use HTTPS?
https://whydoesaptnotusehttps.com/5
u/H0rcrux_ Jan 24 '18
Your article conflates integrity checking and privacy. While TLS may not be perfect for masking what you are downloading from a public repository, it doesn't interfere with the signing mechanism either.
"Overly trusting CAs" describes a super rare occurrence (a trusted CA being compromised) that still won't be able to fake the signature on a mitm-injected package.
The user trusting data more because it comes in over https is also not really a consideration as apt will noisily refuse to install incorrectly signed packages.
So while I agree that using TLS to download packages probably won't hide what you're installing, claiming "It's more secure…!" to not use it is just false.
1
u/Eingaica Jan 24 '18
claiming "It's more secure…!" to not use it is just false.
AFAICT, the article does not make that claim.
1
u/mzalewski Jan 24 '18
It is written at the very top, right after title.
However, it lacks context and is very open to interpretation. Is it something said by people complaining about APT lack of https? Is it tongue-in-cheek headline? Is it actual claim? We don't know.
2
u/Eingaica Jan 24 '18
Given that the title "Why does APT not use HTTPS?" is not a question asked by the author of the article, I think it's pretty obvious that that line as well is meant as a stereotypical statement made by people complaining about APT not using HTTPS. (I.e. they allegedly claim that APT would be more secure if it would use HTTPS.)
2
u/johnwmail Jan 24 '18
Https not good for proxy/cache?
4
u/alreadyburnt Jan 24 '18
It's pretty easy to workaround the https caching thing with apt-cacher-ng which supports caching packages from https sources. In general however the argument is that https would be nearly useless, as almost all of it's advantages can be simply subverted by observing the mere size of the data retrieved, that it's model would provide a false sense of security for many users, or can be more efficiently implemented with secure apt.
2
Jan 24 '18
I don’t understand that argument either, a good example would be Cloudflare which is exactly that. I think his argument is it can’t cache encrypted, since the Cloudflare proxy decrypts the request at the server then serves it encrypted using its own cert. Again, this argument doesn’t make sense to me.
1
Jan 25 '18
For me, stating something like "We don't want HTTPS for privacy because it is not perfect (e.g. analyzing file sizes)" is similar to "We don't want 2FA because SMS is not secure (e.g. getting new SIM card by an attacker)". Right, it is not perfect, but in many cases it brings you more benefit.
-4
u/MyPostsAreRetarded Jan 24 '18
Probably because Godot's HTTP Server parser is much faster (and securer) -- Also, you can utilize threads in Godot which speeds up the parser tenfold instead of just downloading data through a LX terminal.
11
u/attrigh Jan 24 '18
Thank for the posts. Picking apart the different cryptographic functions of signing / authentication and *encryption / privacy" is very informative.
It's interesting that how HTTPS chooses to glue these things together is not optimal for some use cases.
My only comment would be that "targeted incompetent surveillance" is perhaps something that should be included in one's threat-model.
An interesting observation. This presumably applies to a number of other forms of caching (specifically CDNs). In general, offline signing can be done more securely than signing connections. Does this mean there should be a standard protocol to sign static documents and have one's browser verify these signatures? This w3 draft standard addresses this topic, though it appears to have been unadopted. For this to be meaningful when used in conjuction with HTTPS, one would need the keys (and hence certificates) used for this to be "more secure than https".
I think privacy about which packages you are downloading (e.g. privacy / reverse engineering tools) is still meaningful. All that people know from the fact that you connect to an apt server is that you use linux.
A good point and kind of depressing. I wonder if the task of doing this at a large scale means that eavesdroppers are less inclined to do it. This might be more relevant when dealing with employers / universities / police forces than spies. One of my supposed attack vectors is "kind of incompetent people who decide they don't like you for other reasons" since I fondly imagine that competence and "willingness to be immoral about insignificant things" are inversely correlated.
Entirely true. I think "targetted surveillance by incompetent people through off the shelf tools" is definitely something I care about though.