3 ms·
> But, to avoid signature attacks, only signatures made with other keys stored in the repository are retained; that is sufficient to build the web of trust whil
by neilv 7y ago
> But, to avoid signature attacks, only signatures made with other keys stored in the repository are retained; that is sufficient to build the web of trust while eliminating the results of any signature spamming that might have taken place.
I didn't understand how this alone is sufficient to prevent signature spamming, once a single compromised or bad-actor signature is in the repo.
"https://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git/tree/README.rst" https://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git/tree/... suggests a bit different process, which currently seems to require manual importing of individual signatures into one's keyring.
And the automated updating of user's keyring is only of such manually-imported signatures. (And the commit from which the updates are taken must be signed by a key that was signed directly by the key of Torvalds or the user.)