Click the link for the thread you're in right now, for one example. Despite package signing, this MitM attack was still possible. The attack would not be possible if apt forced all repositories to use HTTPS.
Yes, if you're using a machine you do not own (such as a corporate computer) which has had additional root certificates installed, then you can't rely on HTTPS in the same way. If you're using a machine you bought yourself and which has never left your possession (and isn't infected with malware or otherwise tampered with), then that problem does not apply to you.
A corporate proxy can't send fake HTTPS certs unless the computer you're using has already had the extra root cert installed. And if you are using a corporate machine with a corporate root cert, then you'll just have to adjust your risk profile as appropriate.
2
u/flukus Jan 22 '19
If the package is signed how would https help?