Bug#827311: [Pkg-privacy-maintainers] Bug#827311: Bug#827311: parcimonie can't find the keyserver for gpg2

2016-06-23 Thread intrigeri
Daniel Kahn Gillmor wrote (22 Jun 2016 19:46:16 GMT) :
> On Wed 2016-06-22 12:44:01 -0400, Sven Bartscher wrote:
>> Do I really need to configure the keyserver in the dirmngr.conf? If so,
>> that would be a bit inconvenient, as gpg2 itself is fine with having
>> the keyserver configured in gpg.conf.

> in 2.1.9, gpg started deprecating that option.  From gnupg's NEWS file:

>   * dirmngr: Add option --keyserver.  Deprecate that option for gpg.

> But the error you originally cited was a parcimonie error, not a gpg
> error, right?  i don't know enough about parcimonie to know why it might
> think there are different rules for the different versions.

> I recommend that you put your preferred keyserver into dirmngr.conf,
> even if it duplicates the entry in gpg.conf.  does that solve the
> parcimonie issue?

Oops, I missed that email and released parcimonie 0.10.2 that allows
keyserver being defined in gpg.conf *only*, even when using GnuPG 2.x.

After reading what Daniel wrote, it looks like I should revert this
change, shouldn't I?

Cheers,
-- 
intrigeri



Bug#827311: [Pkg-privacy-maintainers] Bug#827311: parcimonie can't find the keyserver for gpg2

2016-06-23 Thread intrigeri
Control: tag -1 + upstream

Hi,

Sven Bartscher wrote (22 Jun 2016 16:44:01 GMT) :
> Do I really need to configure the keyserver in the dirmngr.conf? If so,
> that would be a bit inconvenient, as gpg2 itself is fine with having
> the keyserver configured in gpg.conf.

You're right, the sanity check for "do we have a keyserver configured"
is buggy in this case when using --gnupg2, and it shound check
gpg.conf too. I'll fix that shortly.

Thanks for reporting!

Cheers,
-- 
intrigeri



Bug#827311: [Pkg-privacy-maintainers] Bug#827311: parcimonie can't find the keyserver for gpg2

2016-06-22 Thread Daniel Kahn Gillmor
On Wed 2016-06-22 12:44:01 -0400, Sven Bartscher wrote:
> On Wed, 15 Jun 2016 18:15:16 -0400
> Daniel Kahn Gillmor  wrote:
>
>> what version of gnupg2 do you have installed? 
>
> 2.1.11-7
 [...]
> Do I really need to configure the keyserver in the dirmngr.conf? If so,
> that would be a bit inconvenient, as gpg2 itself is fine with having
> the keyserver configured in gpg.conf.

in 2.1.9, gpg started deprecating that option.  From gnupg's NEWS file:

  * dirmngr: Add option --keyserver.  Deprecate that option for gpg.

But the error you originally cited was a parcimonie error, not a gpg
error, right?  i don't know enough about parcimonie to know why it might
think there are different rules for the different versions.

I recommend that you put your preferred keyserver into dirmngr.conf,
even if it duplicates the entry in gpg.conf.  does that solve the
parcimonie issue?

 --dkg



Bug#827311: parcimonie can't find the keyserver for gpg2

2016-06-22 Thread Sven Bartscher
On Wed, 15 Jun 2016 18:15:16 -0400
Daniel Kahn Gillmor  wrote:

> what version of gnupg2 do you have installed? 

2.1.11-7

> what does:
> 
>  grep ^keyserver ~/.gnupg/dirmngr.conf
> 
> show you?

~/.gnupg/dirmngr.conf doesn't exist for my user. The keyserver is
configured in ~/.gnupg/gpg.conf. Doing the grep over that file gives
this:

$ grep ^keyserver ~/.gnupg/gpg.conf
keyserver hkps://hkps.pool.sks-keyservers.net
keyserver-options no-honor-keyserver-url
keyserver-options include-revoked
keyserver-options
ca-cert-file=/etc/gnupg/trusted-certs/sks-keyservers.netCA.pem

(I know the last option is deprecated for gnupg2, but it's there for
gpg1 compatibility)

Do I really need to configure the keyserver in the dirmngr.conf? If so,
that would be a bit inconvenient, as gpg2 itself is fine with having
the keyserver configured in gpg.conf.

Regards
Sven


pgp1B9avKTI5j.pgp
Description: Digitale Signatur von OpenPGP


Bug#827311: [Pkg-privacy-maintainers] Bug#827311: parcimonie can't find the keyserver for gpg2

2016-06-15 Thread Daniel Kahn Gillmor
On Tue 2016-06-14 16:59:19 -0400, Sven Bartscher wrote:
> When I run parcimonie --gnupg2 it always exits with the following
> message:
>
> No keyserver is configured. at \
> /usr/share/perl5/App/Parcimonie/Daemon.pm line 151.
>
> I actually do have a keyserver configured and gpg2 utilizes it just
> fine. Running parcimonie without --gnupg2 works just fine, so I don't
> think this is a problem with my configuration.
>
> I looked at the code pointed to by the error message and found that
> the following command should return the keyserver:
>
> gpg-connect-agent --dirmngr keyserver /bye
>
> However, it always just prints "OK" and exits without giving the
> address of the keyserver.

what version of gnupg2 do you have installed?  what does:

 grep ^keyserver ~/.gnupg/dirmngr.conf

show you?

another approach is to use:

 gpgconf --list-options dirmngr | grep ^keyserver: | cut -f10 -d:

(the results might need to be un-escaped before use)

 --dkg



Bug#827311: parcimonie can't find the keyserver for gpg2

2016-06-14 Thread Sven Bartscher
Package: parcimonie
Version: 0.10.1-1
Severity: normal

When I run parcimonie --gnupg2 it always exits with the following
message:

No keyserver is configured. at \
/usr/share/perl5/App/Parcimonie/Daemon.pm line 151.

I actually do have a keyserver configured and gpg2 utilizes it just
fine. Running parcimonie without --gnupg2 works just fine, so I don't
think this is a problem with my configuration.

I looked at the code pointed to by the error message and found that
the following command should return the keyserver:

gpg-connect-agent --dirmngr keyserver /bye

However, it always just prints "OK" and exits without giving the
address of the keyserver.

Regards
Sven

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: i386 (i686)

Kernel: Linux 4.5.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages parcimonie depends on:
ii  libclone-perl0.38-1+b1
ii  libconfig-general-perl   2.61-1
ii  libfile-homedir-perl 1.00-1
ii  libfile-which-perl   1.21-1
ii  libgnupg-interface-perl  0.52-2
ii  libipc-system-simple-perl1.25-3
ii  liblist-moreutils-perl   0.413-1+b1
ii  libmoo-perl  2.001001-1
ii  libmoox-late-perl0.015-2
ii  libmoox-options-perl 4.022-1
ii  libnamespace-clean-perl  0.27-1
ii  libpath-tiny-perl0.094-1
ii  libtime-duration-parse-perl  0.13-1
ii  libtry-tiny-perl 0.24-1
ii  libtype-tiny-perl1.05-1
ii  libtypes-path-tiny-perl  0.005-1
ii  perl 5.22.2-1
ii  torsocks 2.1.0-2

Versions of packages parcimonie recommends:
ii  gnupg-curl  1.4.20-6
ii  libglib-perl3:1.320-2
ii  libgtk3-perl0.026-1
ii  liblocale-gettext-perl  1.07-2
ii  libnet-dbus-glib-perl   0.33.0-1+b5
ii  libnet-dbus-perl1.1.0-3+b1
ii  libpango-perl   1.227-1
ii  libtime-duration-perl   1.20-1
ii  tor 0.2.7.6-1

parcimonie suggests no packages.

-- no debconf information