Page MenuHome GnuPG

vext01 (Edd Barrett)
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Monday

  • Clear sailing ahead.

User Details

User Since
Mar 27 2017, 4:48 PM (220 w, 5 d)
Availability
Available

Recent Activity

Oct 18 2020

vext01 added a comment to T5104: Consider removing %n uses from printf-like functions.

Fair enough with regards to portability, and this is not a hill I will die on, but can you comment on the security concerns of using %n?

Oct 18 2020, 11:56 AM · Feature Request

Oct 17 2020

vext01 added a comment to T5104: Consider removing %n uses from printf-like functions.

Hi Werner,

Oct 17 2020, 8:34 PM · Feature Request

Nov 17 2017

vext01 created T3512: gpgme test failure when run with gpg version 1.
Nov 17 2017, 3:50 PM · gnupg (gpg14), gpgme, Bug Report
vext01 added a comment to T3472: gpgme-1.9.0 test suite hangs on OpenBSD.

Shall we close this?

Nov 17 2017, 3:48 PM · gpgagent, gnupg (gpg22), gpgme

Nov 7 2017

vext01 added a comment to T3472: gpgme-1.9.0 test suite hangs on OpenBSD.

So is 380bce13d94f the correct fix? If so, I will update the OpenBSD port including this as a local patch.

Nov 7 2017, 9:47 AM · gpgagent, gnupg (gpg22), gpgme

Nov 6 2017

vext01 added a comment to T3472: gpgme-1.9.0 test suite hangs on OpenBSD.

I confirm that applying the patch fixes the hang under a VM, and does not adversely affect running on a bare metal machine either.

Nov 6 2017, 1:11 PM · gpgagent, gnupg (gpg22), gpgme

Oct 28 2017

vext01 added a comment to T3472: gpgme-1.9.0 test suite hangs on OpenBSD.

Here are a couple of traces of the hanging t-protect test under the VM. I just let it run for a bit under gdb and pressed ctrl+c on a couple of occasions:

Oct 28 2017, 9:14 PM · gpgagent, gnupg (gpg22), gpgme
vext01 added a comment to T3472: gpgme-1.9.0 test suite hangs on OpenBSD.

I've been experimenting.

Oct 28 2017, 8:47 PM · gpgagent, gnupg (gpg22), gpgme

Oct 27 2017

vext01 created T3472: gpgme-1.9.0 test suite hangs on OpenBSD in the S1 Public space.
Oct 27 2017, 7:06 PM · gpgagent, gnupg (gpg22), gpgme

Mar 31 2017

vext01 set Version to 2.1.19 on T3030: Test failure: test using user's keyring instead of fresh keyring?.
Mar 31 2017, 8:10 AM · Info Needed, Bug Report, gnupg
vext01 added projects to T3030: Test failure: test using user's keyring instead of fresh keyring?: gnupg, Bug Report.
Mar 31 2017, 8:10 AM · Info Needed, Bug Report, gnupg

Mar 28 2017

vext01 added a comment to T3021: Add latest GnuPG release notes to the website. .

Thanks, sounds like you have plans to address all three of the problems then.

Cheers

Mar 28 2017, 3:00 PM · gpgweb, Bug Report
vext01 added a project to T3021: Add latest GnuPG release notes to the website. : Bug Report.
Mar 28 2017, 11:02 AM · gpgweb, Bug Report

Oct 2 2015

vext01 added a comment to T2107: dirmngr crash when searching keyservers on OpenBSD.

No problem!

Regarding ipv6. It's not that my OS doesn't support it, it's that the network I
am currently connected to (on my laptop) is not providing IPv6. There's nothing
to say that I won't move to another network that does.

Detecting IPv6 capability would be useful, but (I think) difficult. Especially
since I can move between networks in the lifetime of a single dirmngr. If I move
from a network *without* IPv6 to a network *with* IPv6, should dirmngr realise
and re-enable IPv6?

Anyway, we should open a new bug for this?

P.S.

The fix is applied to OpenBSD ports 2.1.8.

Cheers

Oct 2 2015, 12:02 PM · Duplicate, gnupg, Bug Report, dirmngr

Sep 29 2015

vext01 added a comment to T2107: dirmngr crash when searching keyservers on OpenBSD.

The unusable hosts is a separate issue. I don't have IPv6 connectivity. I can
work around this by using the ipv4 sks pool.

Sep 29 2015, 8:34 PM · Duplicate, gnupg, Bug Report, dirmngr
vext01 added a comment to T2107: dirmngr crash when searching keyservers on OpenBSD.

OK, I think the crash is a use-after free, caused by a realloc followed by a use
of the old dangling pointer.

The following patch fixes this. Can someone on the GPG team review and commit
this for me? I can deal with fixing this in the OpenBSD ports tree. Thanks.

  • dirmngr/ks-engine-hkp.c.orig Tue Sep 29 15:05:02 2015

+++ dirmngr/ks-engine-hkp.c Tue Sep 29 15:05:26 2015
@@ -512,7 +512,7 @@ map_host (ctrl_t ctrl, const char *name, int force_res

  xfree (reftbl);
  return err;
}
  • qsort (reftbl, refidx, sizeof *reftbl, sort_hostpool);

+ qsort (hi->pool, refidx, sizeof *reftbl, sort_hostpool);

  }
else
  xfree (reftbl);
Sep 29 2015, 8:33 PM · Duplicate, gnupg, Bug Report, dirmngr

Sep 22 2015

vext01 added a comment to T2107: dirmngr crash when searching keyservers on OpenBSD.

FWIW, after setting MALLOC_FLAGS="s", I get:

dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'openpgp.us'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'jupiter.zaledia.com'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'schluesselbruecke.de'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 'keys-
02.licoho.de'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 'host-
550b4a17.sileman.net.pl'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'keyserver.mattrude.com'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'dreamcoat.che.uct.ac.za'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'194.94.127.122'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 'RESISP-
209-135-211-141.smf.ragingwire.net'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 'pkqs.net'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 'openpgp-
keyserver.de'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'[2001:4d88:1ffc:477::7]'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'[2001:67c:2050:1000::3:4]'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'[2a01:a500:385:1::9:1]'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'mira.cbaines.net'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'[2001:bc8:3d90:103::]'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'[2001:470:b2a7:1:225:90ff:fe93:e9fc]'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'[2001:1488:ac15:fffe::4]'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'[2a00:b9c0:e::4]'
dirmngr[16846.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'[2604:a880:800:10::688:e001]'
dirmngr[16846.0]: can't connect to '2001:470:b2a7:1:225:90ff:fe93:e9fc': No 
route to host
dirmngr[16846.0]: error connecting to 
'http://[2001:470:b2a7:1:225:90ff:fe93:e9fc]:11371': No route to host
dirmngr[16846.0]: command 'KS_SEARCH' failed: No route to host
ERR 167804970 No route to host <Dirmngr>

I ran again and got:

KEYSERVER --clear hkp://pool.sks-keyservers.net
KS_SEARCH blah@sometesst.ext
OK
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 'RESISP-
209-135-211-141.smf.ragingwire.net'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'dreamcoat.che.uct.ac.za'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 'pkqs.net'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 'host-
550b4a17.sileman.net.pl'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 'keys-
02.licoho.de'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'jupiter.zaledia.com'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'194.94.127.122'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'schluesselbruecke.de'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'openpgp.us'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'keyserver.mattrude.com'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'[2604:a880:800:10::688:e001]'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'[2a00:b9c0:e::4]'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'[2001:470:b2a7:1:225:90ff:fe93:e9fc]'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 'openpgp-
keyserver.de'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'[2001:4d88:1ffc:477::7]'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'mira.cbaines.net'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'[2001:1488:ac15:fffe::4]'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'[2001:67c:2050:1000::3:4]'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'[2a01:a500:385:1::9:1]'
dirmngr[16131.0]: getnameinfo returned for 'pool.sks-keyservers.net': 
'[2001:bc8:3d90:103::]'
dirmngr[16131.0]: error accessing 'http://194.94.127.122:11371/pks/lookup?
op=index&options=mr&search=blah%40sometesst%2Eext': http status 404
dirmngr[16131.0]: command 'KS_SEARCH' failed: No data
ERR 167772218 No data <Dirmngr>

Seems like it doesn't crash with malloc flags on (which is weird). I'm not sure
how dirmngr is supposed to work, but from what i gather the SKS pool has loads
of broken hosts. I've not gotten a working one yet. Surely this can't be right?

Sep 22 2015, 9:32 PM · Duplicate, gnupg, Bug Report, dirmngr
vext01 added projects to T2107: dirmngr crash when searching keyservers on OpenBSD: dirmngr, Bug Report.
Sep 22 2015, 9:19 PM · Duplicate, gnupg, Bug Report, dirmngr
vext01 set Version to 2.1.8 on T2107: dirmngr crash when searching keyservers on OpenBSD.
Sep 22 2015, 9:19 PM · Duplicate, gnupg, Bug Report, dirmngr