You are not logged in.
Hi,
I'm currently reading about pacman and checking more specifically how the package signature is checked.
From what I understood, by default pacman use the optional SigLevel option which means package with a signature will be checked and the signature should be valid but packages without signature will be installed as well.
However when installing arch, the /etc/pacman.conf is by default generated and overwrite this default behavior with the line
SigLevel = Required DatabaseOptional
Why not by default require the signature instead of enforcing it in the config file ? Is it a specific design choice ?
Offline
I've never really understood this variety of question: when there are different options that will satisfy different target audiences one must be selected as a default. Whichever one is chosen, some people could ask "why this setting instead of the other".
The pacman.conf for arch linux requires signatures because all of our main repo packages are signed, so we can benefit from the added security requirement.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I'm not judging the choice I was just wondering if there was any reason I couldn't think of (performance, security, whatever).
That's indeed primordial to benefit from the added security requirement.
Thanks for your answer
Offline
I can reason it, but don't know whether that's the actual background.
libalpm started out w/o any package signing support and when that was added it was therefore defaulted to optional to maintain backward compatibility (libalpm is not exclusively used by arch) but the arch configs of course take advantage of the distros support.
Online
oooh okay sense for the backward compatibility indeed.
Thanks for your answer seth !
Offline