Re: Questions using GPGME

Andreas Heinlein <aheinl...@gmx.com> writes: > Am 06.07.2017 um 14:01 schrieb Justus Winter: >>> 2.) Is there a way to safely distinguish "User clicked cancel when asked >>> for the passphrase" from other errors? I think an application should >>>

Re: Questions using GPGME

Hi :) Andreas Heinlein writes: > I am currently taking first steps using GPGME with the Python interface. > I am facing two questions: > > 1.) I'm looking for a way to get the recipients of encrypted data which > I can not/do not want to decrypt. I.e. a message for which I do

Re: Key corruption: duplicate signatures and usage flags

martin f krafft writes: > [ Unknown signature status ] > Hey Justus, thanks for writing in. Here are the answers you wanted: > >> gpg --version please? > > 2.1.18 > >> > So far, so good. Do note the [SC] usage flags. >> >> What are the capabilities of your primary key

Re: Key corruption: duplicate signatures and usage flags

martin f krafft writes: > And then check this out: > > % gpg --edit-key 0x55C9882D999BBCC4 > gpg (GnuPG) 2.1.18; Copyright (C) 2017 Free Software Foundation, Inc. > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the

Re: Key corruption: duplicate signatures and usage flags

martin f krafft writes: > Hey, > > My key on the keyservers is 0x55C9882D999BBCC4. If I download this > to a fresh keyring, I get some weird behaviours: gpg --version please? > % alias gpg='gpg --homedir=.' I tend to do: $ export GNUPGHOME=$(mktemp -d) > So far, so

Re: Planned GnuPG mirror shutdown: mirror.se.partyvan.eu

Juuso Lapinlampi writes: > I'm the operator of a GnuPG mirror at Partyvan. We've had a listed > GnuPG mirror for ~1.5 years now. [1] > [...] > I don't know yet if or when we could return to providing this mirror > server to the public and GnuPG. For the time being, you may want

Keyring corruption with GnuPG 2.1.20

Hello, unfortunately, GnuPG 2.1.20 has a bug that can lead to keyring corruptions when updating or deleting keys. GnuPG supports two ways to store public keys. The classic one is the 'keyring' format. The new one is called a 'keybox'. Only the 'keyring' format is affected. Long-term users

Re: GPA bug report

"Robert J. Hansen" writes: > (Apologies for the HTML mail; it seems to be the best way to submit a > screenshot, though.) Werner filters out all mail containing html, so this will not reach him. Why not simply attach the image to a plain/text mail? Or even better, report

Re: Parallel decrypts fail in 2.1.19

Michael Smith writes: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > >> Libgcrypt has the fix for the secure memory. Thus the above should not >> happen unless you have set an ulimit. Are you sure that the running >> gpg-agent is up-to-date? >> >>

Re: GnuPG 2.1.19 crashing when listing keys, if tofu-default-policy is "ask"

Hi, MFPA <2014-667rhzu3dc-lists-gro...@riseup.net> writes: > I have been having GnuPG crash with the following message when listing > keys:- > > gpg --list-keys > gpg: O j: Assertion "conflict_set" in get_trust failed > (/home/wk/b-w32/speedo/PLAY-release/gnupg-w32-2.1.19/g10/tofu.c:2787)

Re: GPG homedir path length limit

Daniel Kahn Gillmor <d...@fifthhorseman.net> writes: > On Thu 2017-02-16 04:12:36 -0500, Justus Winter wrote: >> That is still wrong. The length of the path of the socket is not >> limited in any way, the length of the path passed to connect is. > > this is a

Re: Problems with GPGME1.8 and Python 3.5 bindings

Hi, Jean-François Schaff writes: > Thank you Justus for your advice, I could fix that and use the lib > from Python. Good. > I had not realized that both gpg and gpg2 are installed by default on > Ubuntu 16.04 LTS. How is that related to your problem? > Do you know if

Re: GPG homedir path length limit

Daniel Kahn Gillmor writes: > [ Unknown signature status ] > Hi all-- > > sorry for the late followup on this thread: > > On Mon 2017-01-16 14:16:28 -0500, Werner Koch wrote: >> On Sun, 15 Jan 2017 00:39, gn...@jelmail.com said: >>> Just experimenting in a sandbox

Re: Questions about --throw-keyids

Daniel Kahn Gillmor <d...@fifthhorseman.net> writes: > On Tue 2017-02-14 05:28:07 -0500, Justus Winter wrote: >> I don't. I strongly believe that adding command line switches should be >> the absolute last resort. > > I'm open to other suggestions about how to achieve

Re: Questions about --throw-keyids

Daniel Kahn Gillmor writes: > [ Unknown signature status ] > On Mon 2017-02-13 11:54:04 -0500, Lukas Pitschl | GPGTools wrote: >>> Am 13.02.2017 um 17:34 schrieb Daniel Kahn Gillmor : >>> >>> On Mon 2017-02-13 06:41:51 -0500, Bjarni Runar

Re: Problems with GPGME1.8 and Python 3.5 bindings

Hi :) Jean-François Schaff writes: > I'm new to gpg, and trying to use the Python bindings included in > PGPME. I'm using Ubuntu 16.04 LTS. > > I have done the following things: ... > - compiled and installed gpgme-1.8.0 > > Everything seems to build and install as expected,

Re: tofu: Missing entry in the bindings table for new key

Hi! Luis Ressel <ara...@aixah.de> writes: > [ Unknown signature status ] > On Tue, 24 Jan 2017 11:53:55 +0100 > Justus Winter <jus...@g10code.com> wrote: > >> Can you please describe in detail what you were doing so that we can >> recreate the problem? Yo

Re: pyme3 for Windows

ankostis <ankos...@gmail.com> writes: > On 24 January 2017 at 11:46, Justus Winter <jus...@g10code.com> wrote: >> We cross-compile all our software for Windows using MinGW. We don't >> build the Python bindings though. If anyone manages to do that, please >> sha

Re: tofu: Missing entry in the bindings table for new key

Hi, Luis Ressel writes: > Hello, > > I created a new key today. When I tried to verify a signature made by > this key, I got the error message > > gpg: Signature made Sat Jan 21 01:07:59 2017 CET > gpg:using RSA key DEADBEEF > gpg: Good signature from "foo

Re: pyme3 for Windows

ankostis writes: > On 23 January 2017 at 16:28, Jerry wrote: > >> On Mon, 23 Jan 2017 01:06:38 +0100, ankostis stated: >> >> >Has anybody managed to compile pyme3 on Windows? >> > >> >Thanks for all the Hard Work, >> > Kostis >> > >> >> I don't know if

Re: SSH public key comment field and gpg-agent

Hi :) John Lane writes: > If the key is in the agent because of the gpg keyring then it is known > as "(none)". If I do "ssh-add -L" I will see "(none)" at the end of the > output: > > ssh-rsa B3NzaC1yc2EDAQAHT...IfFoxh2j13b3 (none) > > The reason that I stumbled

Re: Private key export for SSH

John Lane writes: >> >> John, can you please tell us which version of GnuPG you are using, and >> just to be sure, also check that >> >> gpg-connect-agent 'getinfo version' /bye >> >> prints the expected version number? >> >> > > $ gpg --version > gpg (GnuPG) 2.1.14 >

Re: Private key export for SSH

Hi John :) Daniel Kahn Gillmor writes: > On Wed 2016-10-12 11:52:19 -0400, John Lane wrote: >> This is just an observation. I thought that perhaps, if I had an >> extracted private key, that I could use "ssh-add" to add it and remove >> the need to manually edit

Re: API documentation for Python GpgMe bindings?

Hello :) Bjoern Kahl writes: > I'd tried to play around with the (new) Python bindings announced just > a few days ago, but I am a bit lost. I am using Python-2.7 on MacOS > "El Captain", with Python-2.7, gpg2, gpgme (1.6.0_2) and the bindings > py27-pygpgme and pyme

RE: gpg: signing failed: Inappropriate ioctl for device Error Message on Linux

Hello, please don't drop the mailing list when replying. Jim Ernst writes: >> I am currently testing keys I created using gpg version 2 2.1.15 (libgcrypt >> 1.7.3) and I am trying to encrypt a file using a shell script in a LINUX >> environment. I am getting the

Re: gpg: signing failed: Inappropriate ioctl for device Error Message on Linux

Jim Ernst writes: > Hello - > > I am currently testing keys I created using gpg version 2 2.1.15 (libgcrypt > 1.7.3) and I am trying to encrypt a file using a shell script in a LINUX > environment. I am getting the following error when the command is executed: >

Re: Call gpg with gpgme

Hi, Le Roy Francis writes: > My snippet works just fine if not for the pinentry. Please reconsider. Your code may work today, but if you are not using gpgme, it will likely break in the future. > Is there a way of > avoiding the pinentry pop-up and enter the pin in

Re: several GPG smartcards connected at the same time

NdK writes: > If GnuPG supported PKCS#11 it would open a whole new world, like the > ability to use generic cards. We have such a module: http://scute.org/ Justus signature.asc Description: PGP signature ___ Gnupg-users

Re: Building gpgme on windows with GCC 5.1.0

Hi :) Le Roy Francis writes: > Hi, I have difficulties building gpgme on windows. I have tried to cross > compile on ubuntu, but I was unable to found a cross compile toolchain > with gcc version 5.1.0.. Do you need exactly that version? Debian has a gcc 5.4 cross

Re: Reduce GPGME memory usage

Hello :) Marcel Behlau writes: > The old version worked fine, now i have to port the stuff to a new > system with fewer RAM and bigger update files. This generates some > problems , if the maximum RAM is used, caused by to big update files. In > my workflow, i'm

Re: improvements for "Git Access" page

Hello :) Filipp Gunbin writes: > - page url is https://www.gnupg.org/download/cvs_access.html , while > it's certainly not "cvs" now. Or was "vcs" meant? Agreed, looks odd. > - A little typo: "You must run ./autogen.sh before running the > ./configure in the way

Re: GPGME signing failed: Bad passphrase

yurip...@sohu.com writes: > Hi, SirI have test "tests/gpg/t-sign.c" and done some necessary > modification as following:0. file "t-support.h", function > "passphrase_cb" char *pass = "057128"; // altered > with the passphrase of my key1. file "t-sign.c", function "main"#if 1 > // be 0 originally,

Re: GPGME signing failed: Bad passphrase

Hello, please don't drop the mailinglist from your replies. It may be that your questions may be relevant to others as well. And by only replying to me you prevent others from answering it, in turn forcing me to reply. yurip...@sohu.com writes: > Hi, SirThanks for your timely reply!I'm really

Re: GPGME signing failed: Bad passphrase

Hello :) First of all, your mails are really hard to read because your mua is inserting into the plain/text part, and there are no newlines. This is how it looks to me: yurip...@sohu.com writes: > Hi, all, We're using GPGME now.I encountered one problem > When running

Re: gpgscm

Hello :) ng0 writes: > While doing the update of gnupg from 2.1.13 to 2.1.14 I found out > that you now include a modified version of tinyscheme for running > your tests/opengpg/ tests. > > Are the changes you apply to tinyscheme generic enough to > contribute to

Re: gpg-preset-passphrase not working with 2.1

Hello :) David Matthews writes: > I can't get gpg-preset-passphrase to work with GnuPG 2.1.7. The > command appears to work successfully but the passphase is not found by > GET_PASSPHRASE. I've included details of my simple test below plus the > output from running it

GnuPG in 2016

Hello, this is the plain text version of a new blog entry I wrote up. If you have questions or want to comment, please group-reply to this mail. Cheers, Justus GnuPG in 2016 = This is an overview of what happened in the first half of 2016 in the GnuPG project and community.