On Sun, Jul 11, 2021 at 06:10:09PM +0100, Justin B Rye wrote:
> If we can refer to "webkit" and "khtml" (in the previous line) and
> "Firefox" and "Chromium" (below) without special markup, it's not
> clear why we need make such a big deal about "*webkit2gtk*" and
> "*wpewebkit*" being source package names. I would suggest just:
>
> mentioned here, with the exception of webkit2gtk and
> the new wpewebkit.</para></footnote> are included in
> &releasename;, but not covered by security support. These
> browsers should not be used against untrusted websites.
> The webkit2gtk and wpewebkit engines
> <emphasis>are</emphasis> covered by security support.
Ok, here's a new patch.
Berto
diff --git a/en/issues.dbk b/en/issues.dbk
index d0940906..827ee75f 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -506,12 +506,11 @@ data = ${lookup{$local_part}lsearch{/some/path/$domain_data/aliases}}
engines<footnote><para>These engines are shipped in a number of different
source packages and the concern applies to all packages shipping
them. The concern also extends to web rendering engines not explicitly
- mentioned here, with the exception of <systemitem
- role="source">webkit2gtk</systemitem>.</para></footnote> are included in
- &releasename;, but not
+ mentioned here, with the exception of webkit2gtk and the new
+ wpewebkit.</para></footnote> are included in &releasename;, but not
covered by security support. These browsers should not be used against
untrusted websites.
- The <systemitem role="source">webkit2gtk</systemitem> source package is
+ The webkit2gtk and wpewebkit engines <emphasis>are</emphasis>
covered by security support.
</para>
<para>
