Page MenuHome GnuPG
Feed Advanced Search

Sep 27 2016

justus added a comment to T2693: Compile error on iMac OS X El Capitan - dns-stuff.c.

I got my hands on a macOS box, and this particular problem is fixed in 2e64ccb0.

I still cannot compile gnupg there, but I'm working on it.

Sep 27 2016, 6:05 PM · Bug Report, gnupg, gnupg (gpg22)
justus added a comment to T2216: Generating keys on Yubikey and requesting off-card backup always fails.

I'm going to close this issue due to inactivity. Feel free to reopen it.

Sep 27 2016, 11:26 AM · Bug Report, gnupg
justus closed T2216: Generating keys on Yubikey and requesting off-card backup always fails as Resolved.
Sep 27 2016, 11:26 AM · Bug Report, gnupg

Sep 23 2016

justus added a comment to T2700: Clean up the command line interface (avoid abbreviated --long-options, consistency).

Also, most options join words with hyphens, but some don't.

Sep 23 2016, 2:44 PM · gnupg, Feature Request, gnupg (gpg22)
justus renamed T2700: Clean up the command line interface (avoid abbreviated --long-options, consistency) from Avoid abbreviated --long-options, e.g. --recv-keys to Clean up the command line interface (avoid abbreviated --long-options, consistency).
Sep 23 2016, 2:44 PM · gnupg, Feature Request, gnupg (gpg22)
justus assigned T1464: key signing in GPGME to werner.
Sep 23 2016, 12:28 PM · gpgme, Feature Request
justus added a comment to T1464: key signing in GPGME.

Fixed in 1.7 with gpgme_op_keysign.

Sep 23 2016, 12:28 PM · gpgme, Feature Request
justus closed T1464: key signing in GPGME as Resolved.
Sep 23 2016, 12:28 PM · gpgme, Feature Request
justus added projects to T2701: Do not let users create keys without an expiration date: gnupg (gpg22), Feature Request, gnupg.
Sep 23 2016, 11:51 AM · Feature Request, gnupg (gpg22)
justus added projects to T2700: Clean up the command line interface (avoid abbreviated --long-options, consistency): gnupg (gpg22), Feature Request, gnupg.
Sep 23 2016, 11:18 AM · gnupg, Feature Request, gnupg (gpg22)

Sep 22 2016

justus added a comment to T2693: Compile error on iMac OS X El Capitan - dns-stuff.c.

Thanks. I believe the relevant part is:

checking whether the resolver is usable... no
checking whether I can make the resolver usable with BIND_8_COMPAT... no

The latter is indeed a MacOS X specific thing.

Would you be so kind to execute the following commands on your machine, and
report the results back?

grep COMPAT /usr/include/arpa/*
grep PACKETSZ /usr/include/arpa/*

Sep 22 2016, 12:59 PM · Bug Report, gnupg, gnupg (gpg22)

Sep 20 2016

justus added projects to T2695: gpg --always-trust --quick-gen-key fails to create a trust database: gnupg (gpg22), gnupg, Bug Report.
Sep 20 2016, 2:58 PM · Bug Report, gnupg, gnupg (gpg22)
justus set Version to 2.1.15, master on T2695: gpg --always-trust --quick-gen-key fails to create a trust database.
Sep 20 2016, 2:58 PM · Bug Report, gnupg, gnupg (gpg22)
justus closed T2445: gpgscm needs to link against libintl on Mac OS as Resolved.
Sep 20 2016, 9:40 AM · Bug Report, gnupg
justus added a comment to T2445: gpgscm needs to link against libintl on Mac OS.

This has been fixed in July with c49c43d7.

Sep 20 2016, 9:40 AM · Bug Report, gnupg
justus claimed T2693: Compile error on iMac OS X El Capitan - dns-stuff.c.
Sep 20 2016, 9:24 AM · Bug Report, gnupg, gnupg (gpg22)
justus added a comment to T2693: Compile error on iMac OS X El Capitan - dns-stuff.c.

Thanks for the report. Please attach the full output of configure.

Sep 20 2016, 9:24 AM · Bug Report, gnupg, gnupg (gpg22)
justus added a project to T2693: Compile error on iMac OS X El Capitan - dns-stuff.c: gnupg (gpg22).
Sep 20 2016, 9:24 AM · Bug Report, gnupg, gnupg (gpg22)

Sep 19 2016

justus assigned T2690: crash when editing key with no signatures to werner.
Sep 19 2016, 2:00 PM · Bug Report, gnupg
justus closed T2691: how to resolve the issue gnome keyring manager hijacked the gnupg agent in redhat linux as Invalid.
Sep 19 2016, 2:00 PM · gnupg, Support
justus claimed T2691: how to resolve the issue gnome keyring manager hijacked the gnupg agent in redhat linux.
Sep 19 2016, 2:00 PM · gnupg, Support
justus lowered the priority of T2691: how to resolve the issue gnome keyring manager hijacked the gnupg agent in redhat linux from Unbreak Now! to Normal.
Sep 19 2016, 2:00 PM · gnupg, Support
justus removed a project from T2691: how to resolve the issue gnome keyring manager hijacked the gnupg agent in redhat linux: Bug Report.
Sep 19 2016, 2:00 PM · gnupg, Support
justus added a comment to T2691: how to resolve the issue gnome keyring manager hijacked the gnupg agent in redhat linux.

This is an issue of GNOME as packaged by Red Hat. Please file a bug in Red
Hat's bug tracker instead.

Sep 19 2016, 2:00 PM · gnupg, Support

Sep 15 2016

justus added a comment to T2682: Keys cannot be refreshed via "gpg2 --refresh-keys".

Sorry, I cannot reproduce this problem using 2.1.11:

% export GNUPGHOME=$(mktemp -d)
% echo "keyserver hkps://hkps.pool.sks-keyservers.net
hkp-cacert
/home/teythoon/repos/g10/gnupg-2.1.11/dirmng/sks-keyservers.netCA.pem" >
$GNUPGHOME/dirmngr.conf
% g10/gpg2 --recv-keys 99B03CE455DB476E737057B44FD0FA5528DB9E3F
gpg: /tmp/tmp.QINMXRcRqH/trustdb.gpg: trustdb created
gpg: key 28DB9E3F: public key "Justus Winter <justus@gnupg.org>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg: imported: 1
% g10/gpg2 --refresh-keys
gpg: refreshing 1 key from hkps://hkps.pool.sks-keyservers.net
gpg: key 28DB9E3F: "Justus Winter <justus@gnupg.org>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1

(Adding the .onion service makes no difference for me either.)

Sep 15 2016, 4:34 PM · Bug Report, gnupg
justus closed T2685: GnuPG failed to start as Invalid.
Sep 15 2016, 4:13 PM · gnupg
justus removed a project from T2685: GnuPG failed to start: Bug Report.
Sep 15 2016, 4:13 PM · gnupg
justus claimed T2685: GnuPG failed to start.
Sep 15 2016, 4:13 PM · gnupg
justus lowered the priority of T2685: GnuPG failed to start from High to Normal.
Sep 15 2016, 4:13 PM · gnupg
justus added a project to T2685: GnuPG failed to start: gnupg.
Sep 15 2016, 4:13 PM · gnupg
justus triaged T2686: Re as Normal priority.
Sep 15 2016, 4:12 PM · Trash
justus closed T2686: Re as Invalid.
Sep 15 2016, 4:12 PM · Trash
justus added a project to T2686: Re: Trash.
Sep 15 2016, 4:12 PM · Trash
justus claimed T2686: Re.
Sep 15 2016, 4:12 PM · Trash

Sep 14 2016

justus lowered the priority of T2684: GPG encrypts using a key of a partial recipient match instead of exact match from High to Normal.
Sep 14 2016, 3:25 PM · gnupg (gpg14), Bug Report
justus changed Version from 2.0.22 to 1.4, 2.0.22, master on T2684: GPG encrypts using a key of a partial recipient match instead of exact match.
Sep 14 2016, 3:25 PM · gnupg (gpg14), Bug Report
justus renamed T2684: GPG encrypts using a key of a partial recipient match instead of exact match from GPG signs using a key of a partial recipient match instead of exact match to GPG encrypts using a key of a partial recipient match instead of exact match.
Sep 14 2016, 3:25 PM · gnupg (gpg14), Bug Report
justus added a project to T2684: GPG encrypts using a key of a partial recipient match instead of exact match: gnupg (gpg22).
Sep 14 2016, 3:25 PM · gnupg (gpg14), Bug Report
justus added a comment to T2684: GPG encrypts using a key of a partial recipient match instead of exact match.

Indeed, this is unfortunate, but not as bad as you make it sound (unless the
user uses always trust).

Note that this is not about signing (which uses the private key), but about
encryption. I've changed the bug title accordingly.

This happens also with master, and it seems the order of keys in the public
keyring is important:

teythoon@europa ~/repos/g10/gnupg/obj (git)-[master] % export GNUPGHOME=$(mktemp -d)
teythoon@europa ~/repos/g10/gnupg/obj (git)-[master] % gpg2 --import test.user.asc
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
gpg: keybox '/tmp/tmp.TR2cSoWHMb/pubring.kbx' created
gpg: /tmp/tmp.TR2cSoWHMb/trustdb.gpg: trustdb created
gpg: key 8D62594F1FE90C7B: public key "test.user@example.org" imported
gpg: Total number processed: 1
gpg: imported: 1
teythoon@europa ~/repos/g10/gnupg/obj (git)-[master] % gpg2 --import user.asc
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
gpg: key 00988FEC00B5CA77: public key "user@example.org" imported
gpg: Total number processed: 1
gpg: imported: 1
teythoon@europa ~/repos/g10/gnupg/obj (git)-[master] % echo huhu|gpg2 -e -r
"user@example.org" -a|gpg2

gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
gpg: 1A7265CF27F9E78E: There is no assurance this key belongs to the named user
sub rsa2048/1A7265CF27F9E78E 2016-09-14 test.user@example.org
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
Primary key fingerprint: CA77 8656 2AAC BBB2 6A50 3A50 8D62 594F 1FE9 0C7B

      Subkey fingerprint: 52CB E9DC 1812 9F78 3054  6569 1A72 65CF 27F9 E78E

It is NOT certain that the key belongs to the person named
in the user ID. If you *really* know what you are doing,
you may answer the next question with yes.

Use this key anyway? (y/N)

gpg: signal gpgInterrupt: signal caught ... exiting
Interrupt caught ... exiting
130 teythoon@europa ~/repos/g10/gnupg/obj (git)-[master] % export
GNUPGHOME=$(mktemp -d)
teythoon@europa ~/repos/g10/gnupg/obj (git)-[master] % gpg2 --import user.asc
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
gpg: keybox '/tmp/tmp.Hfjbb2jvji/pubring.kbx' created
gpg: /tmp/tmp.Hfjbb2jvji/trustdb.gpg: trustdb created
gpg: key 00988FEC00B5CA77: public key "user@example.org" imported
gpg: Total number processed: 1
gpg: imported: 1
teythoon@europa ~/repos/g10/gnupg/obj (git)-[master] % gpg2 --import test.user.asc
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
gpg: key 8D62594F1FE90C7B: public key "test.user@example.org" imported
gpg: Total number processed: 1
gpg: imported: 1
teythoon@europa ~/repos/g10/gnupg/obj (git)-[master] % echo huhu|gpg2 -e -r
"user@example.org" -a|gpg2
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
gpg: DAB278A8736B0D2C: There is no assurance this key belongs to the named user
sub rsa2048/DAB278A8736B0D2C 2016-09-14 user@example.org
Primary key fingerprint: 6680 B181 D853 CEB5 6671 ECC7 0098 8FEC 00B5 CA77

      Subkey fingerprint: 3909 7C31 399C A746 87B3  5D74 DAB2 78A8 736B 0D2C

It is NOT certain that the key belongs to the person named
in the user ID. If you *really* know what you are doing,
you may answer the next question with yes.

Use this key anyway? (y/N)

gpg: signal gpgInterrupt: signal caught ... exiting
Interrupt caught ... exiting

Sep 14 2016, 3:25 PM · gnupg (gpg14), Bug Report

Aug 11 2016

justus closed T2408: implicit declaration of function ‘gpg_err_set_errno’ in common/w32-afunix.c:65 as Resolved.
Aug 11 2016, 1:49 PM · Bug Report, gnupg
justus added a comment to T2408: implicit declaration of function ‘gpg_err_set_errno’ in common/w32-afunix.c:65.

Fixed in 72fa314b.

Aug 11 2016, 1:49 PM · Bug Report, gnupg
justus claimed T2408: implicit declaration of function ‘gpg_err_set_errno’ in common/w32-afunix.c:65.
Aug 11 2016, 9:56 AM · Bug Report, gnupg

Aug 10 2016

justus added a comment to T2417: gnupg doesn't like empty trustdb file.

Actually, I'd argue that tdbio_set_dbname did not handle this case correctly. In
any case, if you must create some temporary gnupghomes, deleting the whole
directory might be both easier and more robust.

Fixed in a27410a2.

Aug 10 2016, 4:54 PM · gnupg, Bug Report
justus closed T2417: gnupg doesn't like empty trustdb file as Resolved.
Aug 10 2016, 4:54 PM · gnupg, Bug Report

Aug 8 2016

justus claimed T2320: pinentry: Fix -Wimplicit-function-declaration warning in pinentry-curses.c [patch].
Aug 8 2016, 11:09 AM · Bug Report, pinentry
justus added a comment to T2320: pinentry: Fix -Wimplicit-function-declaration warning in pinentry-curses.c [patch].

Can you please test if the following patch that has been committed recently
fixes your problem?

https://git.gnupg.org/cgi-bin/gitweb.cgi?
p=pinentry.git;a=commitdiff;h=2227f67af53f38d3d7f97760f2553d2c9ed05969

(It is not NCURSES_INCLUDE, but NCURSES_CFLAGS should be set by
PKG_CHECK_MODULES.)

Thanks!

Aug 8 2016, 11:09 AM · Bug Report, pinentry

Aug 5 2016

justus added projects to T2259: --key-gen failing on Solaris 10: gnupg (gpg14), gnupg.
Aug 5 2016, 9:01 AM · gnupg, gnupg (gpg14), Bug Report
justus added a project to T2354: Deleted secure key not quite deleted?: gnupg.
Aug 5 2016, 9:00 AM · gnupg, Bug Report
justus added a project to T2417: gnupg doesn't like empty trustdb file: gnupg.
Aug 5 2016, 8:59 AM · gnupg, Bug Report
justus added a project to T2394: Broken link to noepatents.org: libgcrypt.
Aug 5 2016, 8:58 AM · Won't Fix, libgcrypt, Bug Report

Aug 4 2016

justus added a comment to T2425: 2.1.14 intermittent `make check` failure on gpgtar.scm.

Can you please tell us what version of ssh you are using (ssh -V)?

Aug 4 2016, 11:58 AM · MacOS, gnupg, Bug Report, gnupg (gpg22)

Aug 2 2016

justus added a comment to T767: gpg2 ignores gpgme_set_passphrase_cb.

https://pagure.io/pygpgme/c/6648b075fb3d434c599d7e1793bd1f0bbe85dfe3?branch=master says:

T767 indicates that

gpgme_set_passphrase_cb is a deprecated corner of the API and that
developers using gpgme should really rely on the gpg-agent to handle
this stuff.

That is not correct. gpgme_set_passphrase_cb is not deprecated, and gpg21 does honor the flag.
In fact, allow-loopback-pinentry is the default since GnuPG 2.1.12.

Aug 2 2016, 6:28 PM · gnupg
justus claimed T767: gpg2 ignores gpgme_set_passphrase_cb.
Aug 2 2016, 6:28 PM · gnupg
justus added a comment to T2407: The assuan interface in gpgme is not documented.

Fixed in 135185b7.

Aug 2 2016, 4:58 PM · Documentation, gpgme, Bug Report
justus closed T2407: The assuan interface in gpgme is not documented as Resolved.
Aug 2 2016, 4:58 PM · Documentation, gpgme, Bug Report
justus claimed T2407: The assuan interface in gpgme is not documented.
Aug 2 2016, 4:58 PM · Documentation, gpgme, Bug Report
justus added a comment to T2426: gpgme - Inappropriate ioctl for device.

Ok, there are no significant patches on top of pygpgme. Note that pygpgme is not really
maintained, and that we neither develop nor support pygpgme. But seeing that dnf is important to
Fedora, let's figure this out.

It would be nice if you could try to reproduce the problem without pygpgme though, just to make a
more minimal test case. I see the exception is thrown during some import. This is how I strace
gnupg to see what ioctls it is issuing:

% strace -eioctl g10/gpg --import ../tests/openpgp/samplekeys/ecc-sample-1-pub.asc
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
gpg: key 0BA52DF0BAA59D9C: public key "ec_dsa_dh_256 <openpgp@brainhub.org>" imported

  • SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=26716, si_uid=1000, si_status=0,

si_utime=0, si_stime=0} ---
ioctl(0, SNDCTL_TMR_TIMEBASE or SNDRV_TIMER_IOCTL_NEXT_DEVICE or TCGETS, {B38400 opost isig icanon
echo ...}) = 0
ioctl(0, SNDCTL_TMR_TIMEBASE or SNDRV_TIMER_IOCTL_NEXT_DEVICE or TCGETS, {B38400 opost isig icanon
echo ...}) = 0
gpg: Total number processed: 1
gpg: imported: 1
+++ exited with 0 +++

Note that if you try to strace your gpgme-based application, you need to pass '-f' to strace to
follow forks.

I have grepped through gpgme and gnupg, and it looks like gnupg is only doing ioctls to terminals,
so maybe your container setup is doing something funny to terminals. But let's see what the strace
shows.

Aug 2 2016, 2:06 PM · Python, Fedora, Bug Report, gpgme
justus claimed T2430: pinentry gtk2 should grab pointer as well as keyboard.
Aug 2 2016, 12:49 PM · Bug Report, pinentry
justus closed T2430: pinentry gtk2 should grab pointer as well as keyboard as Resolved.
Aug 2 2016, 12:49 PM · Bug Report, pinentry
justus added a comment to T2430: pinentry gtk2 should grab pointer as well as keyboard.

Fixed in 2f1f1f06.

Grabbing the pointer might have unexpected repercussions though, e.g. one isn't
able to move windows around anymore. Let's see how it turns out.

Aug 2 2016, 12:49 PM · Bug Report, pinentry
justus added projects to T2434: pinentry-gtk-2's --no-global-grab does not work as advertised: pinentry, Bug Report.
Aug 2 2016, 12:44 PM · Bug Report, pinentry
justus set Version to master on T2434: pinentry-gtk-2's --no-global-grab does not work as advertised.
Aug 2 2016, 12:44 PM · Bug Report, pinentry
justus added a comment to T2320: pinentry: Fix -Wimplicit-function-declaration warning in pinentry-curses.c [patch].

What operating system are you using?

We had the exact same patch committed (21e83f42) and later reverted (f0db3192).
Discussion: https://lists.gnupg.org/pipermail/gnupg-devel/2015-June/030051.html

Aug 2 2016, 12:27 PM · Bug Report, pinentry

Aug 1 2016

justus closed T2375: regression: "could not grab keyboard" as Resolved.
Aug 1 2016, 6:04 PM · Bug Report, pinentry
justus added a comment to T2375: regression: "could not grab keyboard".

This is really weird. Merely not adding the password reveal button to the hbox
'fixes' this problem. Therefore, I don't believe that the patch introduces the
bug, it merely makes it manifest itself.

I looked around in the related gtk bits, but I believe the problem might be in
the X server, or the asynchronous interaction with it. I don't believe it is
worth digging further into X.

Workaround committed in ad390f29.

Aug 1 2016, 6:04 PM · Bug Report, pinentry
justus claimed T2375: regression: "could not grab keyboard".
Aug 1 2016, 6:04 PM · Bug Report, pinentry
justus added a comment to T2432: gpgsm --with-colons --list-keys writes an excessive colon, causing --with-secret to write to the wrong column.

Indeed, thanks for the analysis!

Fixed in 40365b28.

Aug 1 2016, 12:36 PM · Bug Report, gnupg
justus closed T2432: gpgsm --with-colons --list-keys writes an excessive colon, causing --with-secret to write to the wrong column as Resolved.
Aug 1 2016, 12:36 PM · Bug Report, gnupg
justus claimed T2432: gpgsm --with-colons --list-keys writes an excessive colon, causing --with-secret to write to the wrong column.
Aug 1 2016, 12:36 PM · Bug Report, gnupg
justus claimed T2431: tests/openpgp/run-test.scm not shipped in tarball.
Aug 1 2016, 11:20 AM · Bug Report, gnupg
justus closed T2431: tests/openpgp/run-test.scm not shipped in tarball as Resolved.
Aug 1 2016, 11:20 AM · Bug Report, gnupg
justus added a comment to T2431: tests/openpgp/run-test.scm not shipped in tarball.

Fixed in c971ff08.

Aug 1 2016, 11:20 AM · Bug Report, gnupg

Jul 28 2016

justus set Version to master on T2429: Allow Assuan flags to be set.
Jul 28 2016, 2:12 PM · gpgme, Feature Request
justus added projects to T2429: Allow Assuan flags to be set: Feature Request, gpgme.
Jul 28 2016, 2:12 PM · gpgme, Feature Request
justus set Version to master on T2428: Implement returning data from inquire callbacks.
Jul 28 2016, 2:07 PM · gpgme, Feature Request
justus added projects to T2428: Implement returning data from inquire callbacks: Feature Request, gpgme.
Jul 28 2016, 2:07 PM · gpgme, Feature Request

Jul 27 2016

justus closed T2345: Test mds.test fails if /bin/sh -> dash as Resolved.
Jul 27 2016, 5:01 PM · Bug Report
justus added a comment to T2345: Test mds.test fails if /bin/sh -> dash.

Fixed in 2.1.14 with the switch to Scheme-based tests.

Jul 27 2016, 5:01 PM · Bug Report
justus added a comment to T2401: import-clean and export-clean do not have the documented effect.

import-clean does call the same code, but it behaves differently for the key you
mention. I created a test key that does get cleaned up upon import.

Jul 27 2016, 4:22 PM · Bug Report, gnupg
justus changed Version from 2.1.13 to 2.1.13,master on T2401: import-clean and export-clean do not have the documented effect.
Jul 27 2016, 4:22 PM · Bug Report, gnupg
justus added a comment to T2401: import-clean and export-clean do not have the documented effect.

Jul 27 2016, 4:22 PM · Bug Report, gnupg
justus closed T2418: Wrong check for Android in configure.ac as Resolved.
Jul 27 2016, 12:40 PM · Bug Report, gnupg
justus added a comment to T2418: Wrong check for Android in configure.ac.

Merged in 583a464c, thanks!

Note that we prefer contributions sent to the mailinglist using git send-email.

Jul 27 2016, 12:40 PM · Bug Report, gnupg
justus claimed T2418: Wrong check for Android in configure.ac.
Jul 27 2016, 12:40 PM · Bug Report, gnupg
justus added a comment to T2426: gpgme - Inappropriate ioctl for device.

Thanks for the report.

I see that you are using pygpgme, is that correct? If so, which version, and are
there significant patches applied in the Fedora package? And can you please tell
me what version of libgpgme you are using?

Let's try to figure out which ioctl fails. Could you try to strace this process?

Jul 27 2016, 12:24 PM · Python, Fedora, Bug Report, gpgme
justus claimed T2426: gpgme - Inappropriate ioctl for device.
Jul 27 2016, 12:24 PM · Python, Fedora, Bug Report, gpgme

Jul 26 2016

justus added a project to T2419: gpg --list-packets hangs on file containing single zero byte: gnupg.
Jul 26 2016, 6:39 PM · gnupg, Bug Report
justus closed T2419: gpg --list-packets hangs on file containing single zero byte as Resolved.
Jul 26 2016, 6:39 PM · gnupg, Bug Report
justus added a comment to T2419: gpg --list-packets hangs on file containing single zero byte.

Fixed in b2572b0c.

Jul 26 2016, 6:39 PM · gnupg, Bug Report
justus added a comment to T2425: 2.1.14 intermittent `make check` failure on gpgtar.scm.

Thanks for letting us know. Unfortunately, we do not test on MacOS yet, but we are working
on that.

I have neither experience with debugging on MacOS, nor do I have access to such a machine.
I'm afraid you are on your own for now.

The ssh test is new, so we need to figure out why it does not work. Please do

  make -C tests/openpgp check TESTS="setup.scm ssh.scm" verbose=2

This lets us see what ssh-add prints to stderr. It might be related to the version of
OpenSSH shipped with the OS.

Jul 26 2016, 4:43 PM · MacOS, gnupg, gnupg (gpg22), Bug Report
justus claimed T2425: 2.1.14 intermittent `make check` failure on gpgtar.scm.
Jul 26 2016, 4:43 PM · MacOS, gnupg, gnupg (gpg22), Bug Report
justus added projects to T2425: 2.1.14 intermittent `make check` failure on gpgtar.scm: gnupg (gpg22), gnupg.
Jul 26 2016, 4:43 PM · MacOS, gnupg, gnupg (gpg22), Bug Report
justus set Version to master on T2425: 2.1.14 intermittent `make check` failure on gpgtar.scm.
Jul 26 2016, 4:43 PM · MacOS, gnupg, gnupg (gpg22), Bug Report
justus added a comment to T2421: General error after update 2.1.12 -> 2.1.13 on gpgme_op_edit().

The API of pyme3 is almost identical to that of pyme, the former being a port to Python3,
while the latter is for Python2. We also added a more idiomatic interface on top of that, but
porting pyme applications should be easy. It is different to the API of pygpgme though.

I don't know exactly when 1.7 will be released, but it is overdue, so I'd say next month.

Jul 26 2016, 11:10 AM · gnupg
justus removed a project from T2421: General error after update 2.1.12 -> 2.1.13 on gpgme_op_edit(): Bug Report.
Jul 26 2016, 10:21 AM · gnupg
justus closed T2421: General error after update 2.1.12 -> 2.1.13 on gpgme_op_edit() as Invalid.
Jul 26 2016, 10:21 AM · gnupg
justus lowered the priority of T2421: General error after update 2.1.12 -> 2.1.13 on gpgme_op_edit() from High to Normal.
Jul 26 2016, 10:21 AM · gnupg
justus claimed T2421: General error after update 2.1.12 -> 2.1.13 on gpgme_op_edit().
Jul 26 2016, 10:21 AM · gnupg
justus added a comment to T2421: General error after update 2.1.12 -> 2.1.13 on gpgme_op_edit().

That is not a bad commit, that is Werner evolving our software. pygpgme is unmaintained since

  1. My guess is that it cannot cope with the new status code being emitted by GnuPG.

I ran the testsuite myself, and I can reproduce the issue, among many other failures: 24 if I'm
using the GnuPG components from Debian/unstable, 9 if I am using more recent components.

One of them is test_encrypt_to_signonly, which tries to encrypt a mail to a key only usable for
signing, and expects a general error, which all recent versions of GPGME return in this case, but
this was a bug, fixed in GPGME master, which returns the correct error.

Updating pygpgme is out of scope for us. If you merely need any binding, consider using the pyme3
bindings that we merged into GPGME proper, and will release with 1.7. You can also find it on
pypi, it requires GPGME 1.6.x to build.

The way I see it is that the pygpgme bindings and its test suite are way too unmaintained and the
test suite too noisy to demonstrate a bug in GnuPG or GPGME. Feel free to reopen this bug if you
have compelling evidence that we broke something, preferably a small test case not using pygpgme.

Jul 26 2016, 10:21 AM · gnupg

Jul 25 2016

justus added a comment to T2118: Command --quick-gen-key ignores --default-cert-expire, --edit-key ignores --default-sig-expire.

The document you cite also states that UID/UAT lines only use field 10.

Also, neither UID nor UAT packets encode an expiration date [0], the way an UID/UAT can expire
is that the self-signature expires [1].

0: https://tools.ietf.org/html/rfc4880#section-5.11
1: https://tools.ietf.org/html/rfc4880#section-5.2.3.3

I do no longer agree with your first problem. Key expiration is different from signature
expiration, the way to quickly generate a key that expires in one year is:

    $ g10/gpg --quick-gen-key quick_test - - 1y

I guess one could argue that if one specifies --default-cert-expire=X when adding an uid, that
the self-signature for the new uid should expire. But to be honest, I doubt that this matches
user expectations.

What would be the use case really? I know that I'll lose access to that mail address in X years
and hence want my uid to expire then.

Jul 25 2016, 2:15 PM · Won't Fix, gnupg (gpg21), Bug Report, gnupg