On Nov 16, Enrico Zini <[email protected]> wrote:

+Similarly, Debian maintains system-wide datasets such as CA certificates or
+timezone information, which is kept current during the lifetime of a release.
+
+Packages should not ship or embed a copy of such databases without a good
+reason, as it would increase the effort of restoring system security or
+functionality in a timely manner after external events such as a key compromise
+or a timezone update. Exceptions should be documented in ``README.source``.
+
.. _s-readmesource:

I do not think that "should" is enough: the goal is to have a single source of trust anchors, both for the benefit of the security team and for local policy decisions, so this should be a "must". Exceptions due to technical reasons should be fixed with technical work, but until then they are still bugs. Of course, it may still make sense to ignore them for release purposes.

This would also fix policy bug #1150960 (DNSSEC trust anchors).

So I would make this policy both more narrow in scope and more prescriptive. My proposal:

  Similarly, Debian maintains packages containing trust anchors (e.g.
  WebPKI certificate authorities, DNSSEC root zone trust anchors, RPKI
  trust anchor locators) which are kept current during the lifetime of
  a release.

  Other packages which use this information must depend on the appropriate
  data packages and not contain duplicated copies of such trust anchors,
  as it would increase the effort of managing a local policy or restoring
  system security or functionality in a timely manner after external
  events such as an unplanned key revocation or a scheduled rollover.

(This does not mean that I do not see duplicated time zones data as a problem, but it is not a security-sensitive problem hence it could have less strict rules.)

--
ciao,
Marco

Attachment: signature.asc
Description: PGP signature

Reply via email to