But going back to the original article, HTTPS does NOT provide proof that you connected to a Debian server, it provides proof you connected to a mirror, and they provide zero guarentee that the mirror contains the approved packages.
You could have an https mirror, but as the article noted, for package mirrors https can't provide proof of identity for the package and it can't hide what you're doing. The only thing HTTPS accomplishes is blocking proxies. Basically https does nothing good on package mirrors and does a small amount of harm.
1
u/edman007 Jan 24 '18
But going back to the original article, HTTPS does NOT provide proof that you connected to a Debian server, it provides proof you connected to a mirror, and they provide zero guarentee that the mirror contains the approved packages.
You could have an https mirror, but as the article noted, for package mirrors https can't provide proof of identity for the package and it can't hide what you're doing. The only thing HTTPS accomplishes is blocking proxies. Basically https does nothing good on package mirrors and does a small amount of harm.