From patchwork Sun Apr 4 11:10:10 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Adolf Belka X-Patchwork-Id: 4096 Return-Path: Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384 client-signature ECDSA (P-384) client-digest SHA384) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by web04.haj.ipfire.org (Postfix) with ESMTPS id 4FCrg90VXgz3x1r for ; Sun, 4 Apr 2021 11:10:29 +0000 (UTC) Received: from mail02.haj.ipfire.org (mail02.haj.ipfire.org [172.28.1.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) client-signature ECDSA (P-384)) (Client CN "mail02.haj.ipfire.org", Issuer "R3" (verified OK)) by mail01.ipfire.org (Postfix) with ESMTPS id 4FCrg80hBSz1TN; Sun, 4 Apr 2021 11:10:28 +0000 (UTC) Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4FCrg75xJ9z2xxL; Sun, 4 Apr 2021 11:10:27 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384 client-signature ECDSA (P-384) client-digest SHA384) (Client CN "mail01.haj.ipfire.org", Issuer "R3" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4FCrg61FGGz2xfm for ; Sun, 4 Apr 2021 11:10:26 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4FCrg53ymMzD4; Sun, 4 Apr 2021 11:10:25 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1617534625; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=K6owrCaF8f9v2qea1a1xkCrX5wyCrS3Bxq0AWuCrJvI=; b=Vgp4WnU6u/C0Xeisnk5/f0utGWyI6BQgtgAhqUi1fz0ad33xQkzlNwKS2j5TWMa1wUD4Vx fo7a7vnsYy+2RtDQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1617534625; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=K6owrCaF8f9v2qea1a1xkCrX5wyCrS3Bxq0AWuCrJvI=; b=az28/hUCSHHiNYzqMMbptKOG3ZViSIORwTRe2LR9dOTlYl/p+htaW48ZaEjk7oNYCJh2kY EcLft6WoeKycm1XX1+Tcd8VooMdjgG5yXM6ttovDT5isciqsJc1/zg/VaXUiOR2kQucwPI k24xfz3N6bEYQWghtp5FPlk9h3J0Z4QsV+Q5PYdaOvnn8j3jArRuZLlbY6nagHksnS1RMb 8S/4HTkKG0VwO7V061R/zHIg9Q3ERfaETvv921MeWNSHzurHpQ0Vb/Wt6atGCkRdYh4C73 Z0f1M1gnD88OG3enjk+GA3fug0qnYml5zjPrxvDEQjpqdgScxee3y9Q2JFmDkw== From: Adolf Belka To: development@lists.ipfire.org Subject: [PATCH 0/5] gnupg: Update to 2.2.27 Date: Sun, 4 Apr 2021 13:10:10 +0200 Message-Id: <20210404111015.66155-1-adolf.belka@ipfire.org> MIME-Version: 1.0 X-BeenThere: development@lists.ipfire.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IPFire development talk List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: development-bounces@lists.ipfire.org Sender: "Development" This is the patch series for the update of gnupg from the legacy 1.4 branch to the LTS 2.2 branch. Required for build and use are libassuan New requirement for 2.2 branch - change from addon to Core program libksba New requirement for 2.2 branch - new install npth New requirement for 2.2 branch - new install pinentry not required for build. Is required for some uses of gnupg such as when providing passwords. This does not apply the the IPFire use cases. Trying to update gpgme with the old 1.4 branch gnupg resulted in various fails. Was looking for files that were not present. Updating gpgme with 2.2 branch of gnupg was successful. The iso created from the build of all the changes from this patch series was installed in my vm testbed. Keys successfully imported. Package lists successfully read and put into pakfire wui page. Several addons installed successfully. Packages had signatures successfully verified. My testing indicates that gnupg 2.2 branch is successfully working in IPFire in place of the 1.4 branch Adolf Belka (5): gnupg: Update to 2.2.27 libassuan: Convert from addon to core program libksba: required for gnupg 2.2 series npth: required for gnupg 2.2 series gpgme: Update to 1.15.1 config/rootfiles/common/gnupg | 107 ++++++++++-- .../rootfiles/{packages => common}/libassuan | 0 config/rootfiles/common/libksba | 9 + config/rootfiles/common/npth | 7 + config/rootfiles/packages/gpgme | 162 +++++++++++++++++- lfs/gnupg | 4 +- lfs/gpgme | 6 +- lfs/libassuan | 6 - lfs/libksba | 79 +++++++++ lfs/npth | 79 +++++++++ make.sh | 2 + 11 files changed, 434 insertions(+), 27 deletions(-) rename config/rootfiles/{packages => common}/libassuan (100%) create mode 100644 config/rootfiles/common/libksba create mode 100644 config/rootfiles/common/npth create mode 100644 lfs/libksba create mode 100644 lfs/npth