summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSteve McIntyre <steve@einval.com>2021-05-09 01:00:36 +0100
committerSteve McIntyre <steve@einval.com>2021-05-09 01:09:20 +0100
commit6c669d4cdf6ebb034d303ae3acc0e76c6d50ca5b (patch)
tree2489a2bbb30c84cc0262fce924b2e3fc1d654244
parent3c632d741079332fa102c129d37c6679be6fd4a8 (diff)
downloadshim-signed-6c669d4cdf6ebb034d303ae3acc0e76c6d50ca5b.tar.gz
shim-signed-6c669d4cdf6ebb034d303ae3acc0e76c6d50ca5b.zip
Fix duplicated word in the NEWS file
-rw-r--r--debian/shim-signed.NEWS2
1 files changed, 1 insertions, 1 deletions
diff --git a/debian/shim-signed.NEWS b/debian/shim-signed.NEWS
index ddbeb58..4b2bada 100644
--- a/debian/shim-signed.NEWS
+++ b/debian/shim-signed.NEWS
@@ -12,7 +12,7 @@ shim-signed (1.34) unstable; urgency=medium
package to generate a *mostly*-compliant PE/COFF EFI binary without
this toolchain support, and that seemed to be sufficient for
use. Everything seemed to work. *However*, during the development
- and testing phase of shim 15.3 and 15.4, we found found significant
+ and testing phase of shim 15.3 and 15.4, we found significant
issues with this approach. New security features needed in shim
(SBAT) showed up severe problems with the lack of proper toolchain
support. See https://github.com/rhboot/shim/issues/366 for more