Archie Cobbs wrote:
On Thu, Aug 11, 2016 at 11:49 AM, Per Jessen
wrote: On Thu, Aug 11, 2016 at 10:02 AM, Andreas Stieger
wrote: HTTPS (signed by *any* CA) is a downgrade in security compared to signed metadata and packages.
True.. but just to be clear, we're talking about a specific (but common) scenario, which is when a user downloads the signing key via zypper ref, automatically answering "Trust Always?" with yes.
In this scenario what we have today is delivery of that key via HTTP. I'm suggesting we change this to HTTPS, which is much more secure.
That key isn't confidential (or is it?), so what might be gained by enabling https ?
Delivery of the key is vulnerable to a man-in-the-middle attack when using only HTTP.
Any once you've installed my bogus signing key, I can sign any bogus package I want with it and you would trust it.
Okay. Well, technically I see there nothing preventing us from enabling https, we could use Let's Encrypt certificates for instance. Forcing https for anything that isn't mirrored should also be possible. I don't have the access to look into it, so maybe write to admin@opensuse.org and propose it. -- Per Jessen, Zürich (15.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org