On Sun, Nov 15, 2026 at 09:05:55PM +0100, Marco d'Itri wrote:
> On Nov 15, Steve McIntyre <[email protected]> wrote:
> 
> > IMHO we *absolutely* need to fix this awful anti-pattern of packages
> > embedding and using their own certificate stores like this. On other
> I agree: we need a new policy saying that applications MUST use the system
> certificate store.
> 
> This may not be easy for some packages, but it cannot be an excuse to
> a) not fix the easy ones, and
> b) not take note of the others that will still need to be fixed.
> 
> In most cases all that is needed is replacing at build time the embedded
> certificates bundle with a symlink.
> 
> Is there a volunteer to draft the policy?

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

-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini <[email protected]>

Attachment: signature.asc
Description: PGP signature

Reply via email to