From mm at dorfdsl.de  Thu Jul  3 21:21:14 2025
From: mm at dorfdsl.de (Marco Moock)
Date: Thu, 3 Jul 2025 21:21:14 +0200
Subject: gpgsm bash completion
Message-ID: <20250703212114.49ee0baa@ryz.dorfdsl.de>

Hello!

I am running Debian with 2.4.8-1.

I noticed that gpg support bash command completion, but gpgsm doesn't.
Was that ever available for gpgsm?

-- 
Gru?
Marco

Send unsolicited bulk mail to 1751570321muell at stinkedores.dorfdsl.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20250703/de89a420/attachment.sig>

From collin.funk1 at gmail.com  Sun Jul  6 02:10:10 2025
From: collin.funk1 at gmail.com (Collin Funk)
Date: Sat, 05 Jul 2025 17:10:10 -0700
Subject: gpgsm bash completion
In-Reply-To: <20250703212114.49ee0baa@ryz.dorfdsl.de>
References: <20250703212114.49ee0baa@ryz.dorfdsl.de>
Message-ID: <87ldp2mb6l.fsf@gmail.com>

Hi Marco,

Marco Moock via Gnupg-users <gnupg-users at gnupg.org> writes:

> I am running Debian with 2.4.8-1.
>
> I noticed that gpg support bash command completion, but gpgsm doesn't.
> Was that ever available for gpgsm?

The bash completions for 'gpg' are maintained by the bash-completion
project, not GnuPG [1][2][3].

I suppose whoever wrote them originally did not use the 'gpgsm' command,
since it does not have completions implemented.

I'm sure they would be happy to accept the contribution if you or
someone else implemented it. The completions for the other commands
should be a good reference.

Collin

[1] https://github.com/scop/bash-completion/blob/51b009f6a653c66454816e9bc869c40f61329764/completions/gpg
[2] https://github.com/scop/bash-completion/blob/51b009f6a653c66454816e9bc869c40f61329764/completions/gpg2
[3] https://github.com/scop/bash-completion/blob/51b009f6a653c66454816e9bc869c40f61329764/completions/gpgv


From wk at gnupg.org  Sat Jul  5 13:11:14 2025
From: wk at gnupg.org (Werner Koch)
Date: Sat, 05 Jul 2025 13:11:14 +0200
Subject: gpgsm bash completion
In-Reply-To: <20250703212114.49ee0baa@ryz.dorfdsl.de> (Marco Moock via
 Gnupg-users's message of "Thu, 3 Jul 2025 21:21:14 +0200")
References: <20250703212114.49ee0baa@ryz.dorfdsl.de>
Message-ID: <8734ba51v1.fsf@jacob.g10code.de>

On Thu,  3 Jul 2025 21:21, Marco Moock said:

> I noticed that gpg support bash command completion, but gpgsm doesn't.
> Was that ever available for gpgsm?

No idea. Should be easy to implement by parsing "gpgsm --dump-options".


Salam-Shalom,

   Werner

-- 
The pioneers of a warless world are the youth that
refuse military service.             - A. Einstein
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openpgp-digital-signature.asc
Type: application/pgp-signature
Size: 247 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20250705/c56c5bd5/attachment.sig>

From collin.funk1 at gmail.com  Sun Jul  6 22:03:12 2025
From: collin.funk1 at gmail.com (Collin Funk)
Date: Sun, 06 Jul 2025 13:03:12 -0700
Subject: gpgsm bash completion
In-Reply-To: <8734ba51v1.fsf@jacob.g10code.de>
References: <20250703212114.49ee0baa@ryz.dorfdsl.de>
 <8734ba51v1.fsf@jacob.g10code.de>
Message-ID: <87ldp184u7.fsf@gmail.com>

Werner Koch via Gnupg-users <gnupg-users at gnupg.org> writes:

> On Thu,  3 Jul 2025 21:21, Marco Moock said:
>
>> I noticed that gpg support bash command completion, but gpgsm doesn't.
>> Was that ever available for gpgsm?
>
> No idea. Should be easy to implement by parsing "gpgsm --dump-options".

Yep, that is what the completions do for 'gpg', 'gpgv', etc.

Atleast, it does that after handling context-specific completions. For
example, 'gpg --edit-key' and pressing tab for completions will execute
'gpg --list-keys' to suggest keys that you might want to edit.

Collin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20250706/51bb47bb/attachment.sig>

From sebastian.wagner at intevation.de  Fri Jul 11 08:50:54 2025
From: sebastian.wagner at intevation.de (Sebastian Wagner)
Date: Fri, 11 Jul 2025 08:50:54 +0200
Subject: Replacement for the gone gpgme Python library?
Message-ID: <f8fbedcb-1d4c-4e06-a0f7-996c814f2ae7@intevation.de>

Dear gnupg community

what is the correct replacement for the gone gpgme library?
https://pypi.org/project/gpgme/
which has vanished somewhere between June 10th and June 18th

The library published as gpg (https://pypi.org/project/gpgme/) is not a 
replacement as that itself depends on the deleted gpgme (or is broken 
itself):

|     import gpg
| 
/opt/hostedtoolcache/Python/3.10.14/x64/lib/python3.10/site-packages/gpg/__init__.py:101: 
in <module>
|     from . import core
| 
/opt/hostedtoolcache/Python/3.10.14/x64/lib/python3.10/site-packages/gpg/core.py:34: 
in <module>
|     from . import gpgme
| E   ImportError: cannot import name 'gpgme' from partially initialized 
module 'gpg' (most likely due to a circular import) 
(/opt/hostedtoolcache/Python/3.10.14/x64/lib/python3.10/site-packages/gpg/__init__.py)

The error message is a bit different on 3.13:

|     import gpg
| 
/opt/hostedtoolcache/Python/3.13.1/x64/lib/python3.13/site-packages/gpg/__init__.py:101: 
in <module>
|     from . import core
| 
/opt/hostedtoolcache/Python/3.13.1/x64/lib/python3.13/site-packages/gpg/core.py:34: 
in <module>
|     from . import gpgme
| 
/opt/hostedtoolcache/Python/3.13.1/x64/lib/python3.13/site-packages/gpg/gpgme.py:13: 
in <module>
|     from . import _gpgme
| E   ImportError: dynamic module does not define module export function 
(PyInit__gpgme)

best regards

-- 
Sebastian Wagner  |  +49-541-335083-164  |  https://intevation.de
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20250711/98a876ba/attachment-0001.sig>

From ametzler at bebt.de  Fri Jul 11 11:08:00 2025
From: ametzler at bebt.de (Andreas Metzler)
Date: Fri, 11 Jul 2025 11:08:00 +0200
Subject: Replacement for the gone gpgme Python library?
In-Reply-To: <f8fbedcb-1d4c-4e06-a0f7-996c814f2ae7@intevation.de>
References: <f8fbedcb-1d4c-4e06-a0f7-996c814f2ae7@intevation.de>
Message-ID: <aHDUcM-QRrmq4CYK@argenau.bebt.de>

On 2025-07-11 Sebastian Wagner via Gnupg-users <gnupg-users at gnupg.org> wrote:
> Dear gnupg community

> what is the correct replacement for the gone gpgme library?
> https://pypi.org/project/gpgme/
> which has vanished somewhere between June 10th and June 18th

> The library published as gpg (https://pypi.org/project/gpgme/) is not a
> replacement as that itself depends on the deleted gpgme (or is broken
> itself):
[...]

Hello,

I see two identical URLs above, and it is a dead link.

Gpgme is a C library https://gnupg.org/software/gpgme/index.html and
very much alive. The python binings for this library have been split out
from gpgme tarball and are available at
https://dev.gnupg.org/source/gpgmepy/ (GIT) and
https://gnupg.org/ftp/gcrypt/gpgmepy/ (tarball).

cu Andreas


From swagner at intevation.de  Fri Jul 11 11:17:47 2025
From: swagner at intevation.de (Sebastian Wagner)
Date: Fri, 11 Jul 2025 11:17:47 +0200
Subject: Replacement for the gone gpgme Python library?
In-Reply-To: <aHDUcM-QRrmq4CYK@argenau.bebt.de>
References: <f8fbedcb-1d4c-4e06-a0f7-996c814f2ae7@intevation.de>
 <aHDUcM-QRrmq4CYK@argenau.bebt.de>
Message-ID: <10e45b6e-d097-4c9d-b3df-02d2afb49fd8@intevation.de>

Hello

On 11/07/2025 11:08, Andreas Metzler wrote:
> I see two identical URLs above, and it is a dead link.

Sorry, the second link should have been https://pypi.org/project/gpg/

That the gpgme link is dead, is the problem. Previously it had version 2 
of the library.

> Gpgme is a C library https://gnupg.org/software/gpgme/index.html and
> very much alive. The python binings for this library have been split out
> from gpgme tarball and are available at
> https://dev.gnupg.org/source/gpgmepy/ (GIT) and
> https://gnupg.org/ftp/gcrypt/gpgmepy/ (tarball).

Thank you, that helps.

So the packages are no longer updated on pypi? The gpg library published 
there is seven years old and broken.

Best regards

-- 
Sebastian Wagner  |  +49-541-335083-164  |  https://intevation.de
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter


From swagner at intevation.de  Fri Jul 11 10:18:10 2025
From: swagner at intevation.de (Sebastian Wagner)
Date: Fri, 11 Jul 2025 10:18:10 +0200
Subject: Replacement for the gone gpgme Python library?
Message-ID: <96f0be0f-b6f2-431a-94be-cdd514c4b13e@intevation.de>

Dear gnupg community

what is the correct replacement for the gone gpgme library?
https://pypi.org/project/gpgme/
which has vanished somewhere between June 10th and June 18th

The library published as gpg (https://pypi.org/project/gpgme/) is not a 
replacement as that itself depends on the deleted gpgme (or is broken 
itself):

|     import gpg
| 
/opt/hostedtoolcache/Python/3.10.14/x64/lib/python3.10/site-packages/gpg/__init__.py:101: 
in <module>
|     from . import core
| 
/opt/hostedtoolcache/Python/3.10.14/x64/lib/python3.10/site-packages/gpg/core.py:34: 
in <module>
|     from . import gpgme
| E   ImportError: cannot import name 'gpgme' from partially initialized 
module 'gpg' (most likely due to a circular import) 
(/opt/hostedtoolcache/Python/3.10.14/x64/lib/python3.10/site-packages/gpg/__init__.py)

The error message is a bit different on 3.13:

|     import gpg
| 
/opt/hostedtoolcache/Python/3.13.1/x64/lib/python3.13/site-packages/gpg/__init__.py:101: 
in <module>
|     from . import core
| 
/opt/hostedtoolcache/Python/3.13.1/x64/lib/python3.13/site-packages/gpg/core.py:34: 
in <module>
|     from . import gpgme
| 
/opt/hostedtoolcache/Python/3.13.1/x64/lib/python3.13/site-packages/gpg/gpgme.py:13: 
in <module>
|     from . import _gpgme
| E   ImportError: dynamic module does not define module export function 
(PyInit__gpgme)

best regards

-- 
Sebastian Wagner  |  +49-541-335083-164  |  https://intevation.de
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter


From Eva.Bolten at gnupg.com  Fri Jul 11 13:57:48 2025
From: Eva.Bolten at gnupg.com (Eva Bolten)
Date: Fri, 11 Jul 2025 13:57:48 +0200
Subject: Replacement for the gone gpgme Python library?
In-Reply-To: <10e45b6e-d097-4c9d-b3df-02d2afb49fd8@intevation.de>
References: <f8fbedcb-1d4c-4e06-a0f7-996c814f2ae7@intevation.de>
 <aHDUcM-QRrmq4CYK@argenau.bebt.de>
 <10e45b6e-d097-4c9d-b3df-02d2afb49fd8@intevation.de>
Message-ID: <54762869.ez6Hsxa1ig@jackson>

Hi Sebastian,

> So the packages are no longer updated on pypi? The gpg library published
> there is seven years old and broken.

Have a look at the gnupg-devel list, there have been several threads regarding 
python bindings of gpg and pypy recently, e.g.:

https://lists.gnupg.org/pipermail/gnupg-devel/2025-June/035961.html
https://lists.gnupg.org/pipermail/gnupg-devel/2025-June/035922.html

Your colleagues Bernhard and Paul are involved. You might tell them to improve 
the documentation and discoverablity of the recent changes ;-) 

Kind regards

Eva

-- 
g10 Code GmbH         GnuPG.com           AmtsGer. Wuppertal HRB 14459
Bergstr. 3a                               Gesch?ftsf?hrung Werner Koch
D-40699 Erkrath       https://gnupg.com      USt-Id DE215605608
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20250711/24c21fd0/attachment.sig>

From sebastian.wagner at intevation.de  Fri Jul 11 11:17:27 2025
From: sebastian.wagner at intevation.de (Sebastian Wagner)
Date: Fri, 11 Jul 2025 11:17:27 +0200
Subject: Replacement for the gone gpgme Python library?
In-Reply-To: <aHDUcM-QRrmq4CYK@argenau.bebt.de>
References: <f8fbedcb-1d4c-4e06-a0f7-996c814f2ae7@intevation.de>
 <aHDUcM-QRrmq4CYK@argenau.bebt.de>
Message-ID: <d086915c-e75e-4459-84f1-3e2afa744ce8@intevation.de>

Hello

On 11/07/2025 11:08, Andreas Metzler wrote:
> I see two identical URLs above, and it is a dead link.

Sorry, the second link should have been https://pypi.org/project/gpg/

That the gpgme link is dead, is the problem. Previously it had version 2 
of the library.

> Gpgme is a C library https://gnupg.org/software/gpgme/index.html and
> very much alive. The python binings for this library have been split out
> from gpgme tarball and are available at
> https://dev.gnupg.org/source/gpgmepy/ (GIT) and
> https://gnupg.org/ftp/gcrypt/gpgmepy/ (tarball).

Thank you, that helps.

So the packages are no longer updated on pypi? The gpg library published 
there is seven years old and broken.

Best regards

-- 
Sebastian Wagner  |  +49-541-335083-164  |  https://intevation.de
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20250711/8b9bc0d5/attachment.sig>

From wk at gnupg.org  Mon Jul 14 14:12:19 2025
From: wk at gnupg.org (Werner Koch)
Date: Mon, 14 Jul 2025 14:12:19 +0200
Subject: [Announce] GnuPG 2.5.9 released
Message-ID: <875xfvynrw.fsf@jacob.g10code.de>

Hello!

We are pleased to announce the availability of a new GnuPG release.
Version 2.5.9 which will soon lead us to the new stable 2.6 series.
This release mostly fixes regression in the previous releases.

The main features in the 2.6 series are improvements for 64 bit Windows
and the introduction of Kyber (ML-KEM, FIPS-203) as PQC encryption
algorithm.  Other than PQC support the 2.6 series will not differ a lot
from 2.4 because the majority of changes are internal to make use of
newer features from the supporting libraries.  Please be aware that the
2.4 series will reach end of life in June next of year.


What is GnuPG
=============

The GNU Privacy Guard (GnuPG, GPG) is a complete and free implementation
of the OpenPGP and S/MIME standards.

GnuPG allows to encrypt and sign data and communication, features a
versatile key management system as well as access modules for public key
directories.  GnuPG itself is a command line tool with features for easy
integration with other applications.  The separate library GPGME provides
a uniform API to use the GnuPG engine by software written in common
programming languages.  A wealth of frontend applications and libraries
making use of GnuPG are available.  As an universal crypto engine GnuPG
provides support for S/MIME and Secure Shell in addition to OpenPGP.

GnuPG is Free Software (meaning that it respects your freedom).  It can
be freely used, modified and distributed under the terms of the GNU
General Public License.


Noteworthy changes in version 2.5.9 (2025-07-10)
================================================
         [compared to version 2.5.8]

  * gpg: Add the revocation reason to the sigclass of a "rev" line.
    Regression in 2.5.7.  [T7073]

  * gpg: Do not show the non-standard secp256k1 curve in the menu to
    select the curve.  It can however be specified using its name.
    [rG49a9171f63]

  * gpg: Fix regression in using the secp256k1 curve.  [T7698]

  * dirmngr: New option --user-agent and send a default User-Agent of
    "GnuPG/2.6" for all HTTP requests.  [T7715]

  Release-info: https://dev.gnupg.org/T7695


Getting the Software
====================

Please follow the instructions found at <https://gnupg.org/download/> or
read on:

GnuPG may be downloaded from one of the GnuPG mirror sites or direct
from its primary file server.  The list of mirrors can be found at
<https://gnupg.org/download/mirrors.html>.  Note that GnuPG is not
available at ftp.gnu.org.

The GnuPG source code compressed using BZIP2 and its OpenPGP signature
are available here:

 https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.5.9.tar.bz2 (8015k)
 https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.5.9.tar.bz2.sig

An installer for Windows without any graphical frontend except for a
very minimal Pinentry tool is available here:

 https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.5.9_20250710.exe (5521k)
 https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.5.9_20250710.exe.sig

The source used to build this installer for 64-bit Windows is available as

 https://gnupg.org/ftp/gcrypt/gnupg/gnupg-w32-2.5.9_20250710.tar.xz (15M)
 https://gnupg.org/ftp/gcrypt/gnupg/gnupg-w32-2.5.9_20250710.tar.xz.sig

This source tarball may also be used to download all required libraries
at once to build a Unix version on any modern system.  See the included
README.


Debian Packages
===============

For the first time we now provide Debian style packages for a couple of
Debian variants.  See https://repos.gnupg.org/deb/gnupg/bookworm-devel/
or use the menu to switch to other distros/releases.  If you encounter
packaging problems please report them to the gnupg-devel mailing list.


Windows Installer
=================

A new *Beta* version of Gpg4win, our full featured Windows installer
including this version of GnuPG as well as the Kleopatra GUI and a PDF
has also been released.  See https://gpg4win.org/version5.html


Checking the Integrity
======================

In order to check that the version of GnuPG which you are going to
install is an original and unmodified one, you can do it in one of
the following ways:

 * If you already have a version of GnuPG installed, you can simply
   verify the supplied signature.  For example to verify the signature
   of the file gnupg-2.5.9.tar.bz2 you would use this command:

     gpg --verify gnupg-2.5.9.tar.bz2.sig gnupg-2.5.9.tar.bz2

   This checks whether the signature file matches the source file.
   You should see a message indicating that the signature is good and
   made by one or more of the release signing keys.  Make sure that
   this is a valid key, either by matching the shown fingerprint
   against a trustworthy list of valid release signing keys or by
   checking that the key has been signed by trustworthy other keys.
   See the end of this mail for information on the signing keys.

 * If you are not able to use an existing version of GnuPG, you have
   to verify the SHA-1 checksum.  On Unix systems the command to do
   this is either "sha1sum" or "shasum".  Assuming you downloaded the
   file gnupg-2.5.9.tar.bz2, you run the command like this:

     sha1sum gnupg-2.5.9.tar.bz2

   and check that the output matches the next line:

701bd8fe8789a86cd2b7c27254a2ab837ee4fcfa  gnupg-2.5.9.tar.bz2
1209dd1dc3cb9e33e3c7857e7f10a7b0fc8d478e  gnupg-w32-2.5.9_20250710.tar.xz
0c7814a9ed67c48d0498f42f5a0eeaaf18e29f49  gnupg-w32-2.5.9_20250710.exe


Internationalization
====================

This version of GnuPG has support for 26 languages with Chinese
(traditional and simplified), Czech, French, German, Italian, Japanese,
Norwegian, Polish, Portuguese, Russian, Turkish, and Ukrainian being
almost completely translated.


Documentation and Support
=========================

The file gnupg.info has the complete reference manual of the system.
Separate man pages are included as well but they miss some of the
details available only in the manual.  The manual is also available
online at

  https://gnupg.org/documentation/manuals/gnupg/

or can be downloaded as PDF at

  https://gnupg.org/documentation/manuals/gnupg.pdf

You may also want to search the GnuPG mailing list archives or ask on
the gnupg-users mailing list for advise on how to solve problems.  Most
of the new features are around for several years and thus enough public
experience is available.  https://wiki.gnupg.org has user contributed
information around GnuPG and relate software.

In case of build problems specific to this release please first check
https://dev.gnupg.org/T7695 for updated information.

Please consult the archive of the gnupg-users mailing list before
reporting a bug: https://gnupg.org/documentation/mailing-lists.html.
We suggest to send bug reports for a new release to this list in favor
of filing a bug at https://bugs.gnupg.org.  If you need commercial
support go to https://gnupg.com or https://gnupg.org/service.html.

If you are a developer and you need a certain feature for your project,
please do not hesitate to bring it to the gnupg-devel mailing list for
discussion.


Thanks
======

Since 2001 maintenance and development of GnuPG is done by g10 Code GmbH
and has mostly been financed by donations.  A team of full-time employed
developers and contractors are working exclusively on GnuPG and related
software like Libgcrypt, GPGME, Kleopatra, Okular, and Gpg4win.

Fortunately, and this is still not common with free software, we have
established a way of financing the development while keeping all our
software free and freely available for everyone.  Our model is similar
to the way RedHat manages RHEL and Fedora: Except for the actual binary
of the MSI installer for Windows and client specific configuration
files, all the software is available under the GNU GPL and other Open
Source licenses.  Thus customers may even build and distribute their own
version of the software as long as they do not use our trademarks
GnuPG Desktop? or GnuPG VS-Desktop?.

We like to thank all the nice people who are helping the GnuPG project,
be it testing, coding, translating, suggesting, auditing, administering
the servers, spreading the word, answering questions on the mailing
lists, or helped with donations.

*Thank you all*

   Your GnuPG hackers


p.s.
This is an announcement only mailing list.  Please send replies only to
the gnupg-users at gnupg.org mailing list.

* List of Release Signing Keys:
  To guarantee that a downloaded GnuPG version has not been tampered by
  malicious entities we provide signature files for all tarballs and
  binary versions.  The keys are also signed by the long term keys of
  their respective owners.  Current releases are signed by one or more
  of these four keys:

    ed25519 2020-08-24 [SC] [expires: 2030-06-30]
    6DAA 6E64 A76D 2840 571B  4902 5288 97B8 2640 3ADA
    Werner Koch (dist signing 2020)
  
    ed25519 2021-05-19 [SC] [expires: 2027-04-04]
    AC8E 115B F73E 2D8D 47FA  9908 E98E 9B2D 19C6 C8BD
    Niibe Yutaka (GnuPG Release Key)
  
    rsa3072 2025-05-09 [SC] [expires: 2033-03-03]
    3B76 1AE4 E63B F351 9CE7  D63B ECB6 64CB E133 2EEF
    Alexander Kulbartsch (GnuPG Release Key)
  
    brainpoolP256r1 2021-10-15 [SC] [expires: 2029-12-31]
    02F3 8DFF 731F F97C B039  A1DA 549E 695E 905B A208
    GnuPG.com (Release Signing Key 2021)

  The keys are available at https://gnupg.org/signature_key.html and in
  any recently released GnuPG tarball in the file g10/distsigkey.gpg .
  Note that this mail has been signed by a different key.

* Debian Package Signing Key:
  The new Debian style packages are signed using this key:

  ed25519 2025-07-08 [SC] [expires: 2035-07-14]
  3209 7B71 9B37 45D6 E61D DA1B 85C4 5AE3 E1A2 B355
  GnuPG.org Package Signing Key <package-maintainers at gnupg.org>

  See the package website (https://repos.gnupg.org/deb/gnupg) for a list
  of supported distributions and a download link for the key.

-- 
Arguing that you don't care about the right to privacy because you have
nothing to hide is no different from saying you don't care about free
speech because you have nothing to say.                - Edward Snowden
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openpgp-digital-signature.asc
Type: application/pgp-signature
Size: 247 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20250714/05b5a95e/attachment-0001.sig>
-------------- next part --------------
_______________________________________________
Gnupg-announce mailing list
Gnupg-announce at gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-announce

From swagner at intevation.de  Wed Jul 16 12:34:34 2025
From: swagner at intevation.de (Sebastian Wagner)
Date: Wed, 16 Jul 2025 12:34:34 +0200
Subject: Replacement for the gone gpgme Python library?
In-Reply-To: <54762869.ez6Hsxa1ig@jackson>
References: <f8fbedcb-1d4c-4e06-a0f7-996c814f2ae7@intevation.de>
 <aHDUcM-QRrmq4CYK@argenau.bebt.de>
 <10e45b6e-d097-4c9d-b3df-02d2afb49fd8@intevation.de>
 <54762869.ez6Hsxa1ig@jackson>
Message-ID: <cc97f67c-0eff-41d3-be04-d4b9e4f37dde@intevation.de>

Hi Eva

On 11/07/2025 13:57, Eva Bolten via Gnupg-users wrote:
> Have a look at the gnupg-devel list, there have been several threads regarding
> python bindings of gpg and pypy recently, e.g.:
> 
> https://lists.gnupg.org/pipermail/gnupg-devel/2025-June/035961.html
> https://lists.gnupg.org/pipermail/gnupg-devel/2025-June/035922.html
> 
> Your colleagues Bernhard and Paul are involved. You might tell them to improve
> the documentation and discoverablity of the recent changes ;-)

Their work only consisted of development, not the uploading of packages 
to PyPI.

With the deleted gpgme library on pypi, the only source of the working 
gpg library on pypi was gone. So my question is where do pip-users get 
the current version from, and the answer was: not on pypi, but from the 
gnupg website.

However, I want to add that this policy might open the door for popular 
non-official uploads of the library on pypi.

Best regards

-- 
Sebastian Wagner  |  +49-541-335083-164  |  https://intevation.de
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter