On 11/16/26 1:31 PM, Enrico Zini wrote:
Here's my attempt at a draft. Can anyone see fundamental flaws?

diff --git i/policy/ch-source.rst w/policy/ch-source.rst
index 5228e0b..d76de4d 100644
--- i/policy/ch-source.rst
+++ w/policy/ch-source.rst
@@ -803,8 +803,8 @@ the list in ``debian/files``.

  .. _s-embeddedfiles:

-Embedded code copies
---------------------
+Embedded code or database copies
+--------------------------------

  Some software packages include in their distribution convenience copies
  of code from other software packages, generally so that users compiling
@@ -817,6 +817,14 @@ libraries already in Debian and the convenience copy is 
not used. If the
  included code is not already in Debian, it should be packaged separately
  as a prerequisite if possible.  [#]_

+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:

  Source package handling: ``debian/README.source``



Enrico


I think the ability to easily deploy, trust, and un-trust CAs is roughly as
important as security updates.  Said another way, I don't think an active
security team that is able to rapidly address compromised CAs should be
sufficient justification for an exception.

I also suspect we should get buy-in from the Firefox team on this.

Best,
Antonio

Reply via email to