Hi Am Montag, 28. November 2016, 09:41:13 schrieb Adrian Schröter:
On Montag, 28. November 2016, 09:34:04 CET wrote Mathias Homann:
Am Montag, 28. November 2016, 05:40:54 CET schrieb Bernhard M. Wiedemann:
Hi,
when building RPMs in OBS, each of them is signed with a private key that is kept somewhere in the OBS infrastructure.
But it occurred to me, that this might not actually be needed because we sign repository metadata using the same keys and that metadata contains hashes of files, so those are already protected against malicious modification.
Are there tools, processes or people using those sigs on individual rpms?
Yup, rpm itself does. It can be set to refuse unsigned RPMs. You can also check against the digital signature when verifying packages. Lastly, people can always manually download and install packages without adding the repositories.
and osc does. It downloads rpm which may not even pubished at that point of time and validates it (at least when not building in a safe env like kvm)
and newer libzypp/zypper/etc. is using it in case the metadata are not signed. -- Regards Michael Calmer -------------------------------------------------------------------------- Michael Calmer SUSE LINUX GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com -------------------------------------------------------------------------- SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org