Re: gpg2 --version gpg: Fatal: libgcrypt is too old (need 1.7.0, have 1.6.3)

[Werner Koch]

On Sat, 19 Nov 2016 00:24, davidadamson...@gmail.com said:

> gpg: Fatal: libgcrypt is too old (need 1.7.0, have 1.6.3).

You built gpg2 against Libgcrypt 1.7 but the system can't find that
library at runtime and uses the system provided version (1.6.3).  Quick
workaround (assuming gpg was built with defaults):

  $ LD_LIBRARY_PATH=/usr/local/lib
  $ export LD_LIBRARY_PATH


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


pgpj_xBMxlzdZ.pgp
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: gpg2 --version gpg: Fatal: libgcrypt is too old (need 1.7.0, have 1.6.3)

[David Adamson]

That worked thank you but only for that session and I read that it's
generally not good practice to make that path permanent.

Are you proposing I do this every time I wish to use gpg2?
Is this behavior expected in a successful installation or what did I
do wrong and can I fix it?

Thanks again.

P.S. I am prepared to do fresh install of OS if that would be smart.

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: gpg2 --version gpg: Fatal: libgcrypt is too old (need 1.7.0, have 1.6.3)

[Peter Lebbing]

On 19/11/16 15:13, David Adamson wrote:
> Are you proposing I do this every time I wish to use gpg2?
> Is this behavior expected in a successful installation or what did I
> do wrong and can I fix it?

Did you issue a

# ldconfig

as root after you installed the libraries? Because you say you run
Debian jessie, and that has the file:

::
/etc/ld.so.conf.d/libc.conf
::
# libc default configuration
/usr/local/lib

So unless you manually changed the settings for ld.so, this directory
should already be in the system search path. However, invoking ldconfig
as root is a necessary step to scan these directories for new additions,
AFAIK. Possibly this is only necessary if you put the first library in
one of the dirs, I don't have the details ready. But in a normal Debian
jessie system, libraries in this directory should "Just Work"(TM).

Or is this a problem with the 1.6.3 receiving priority over 1.7.3? I
don't know off the top of my head how to fix that, so let's try ldconfig
first...

HTH,

Peter.

-- 
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at 

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: gpg2 --version gpg: Fatal: libgcrypt is too old (need 1.7.0, have 1.6.3)

[David Adamson]

Running ldconfig as root resolved the issue I was having! Now when I
type gpg2 --version in a new shell it reports the following:

gpg (GnuPG) 2.1.15
libgcrypt 1.7.3

Thanks for the help.

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

configure warnings and errors upon ./configure for Pinentry v0.9.7

[David Adamson]

Hello,

I'm running a debian Jessie v8 kernel release 3.16.0-4-amd64 on my
personal laptop. It came pre-installed with GnuPG 1.4.18.

I went to generate keys for myself by typing:
gpg2 --gen-key

But then during the process got this error:
gpg: agent_genkey failed: No pinentry
Key generation failed: No pinentry

So I assumed I needed to install Pinentry and downloaded it from gnupg.org.
I tried running ./configure as root and towards the end I got the
following warnings and errors. I'm not sure how many issues I'm
dealing with here or how to fix them.

checking for gpg-error-config... /usr/local/bin/gpg-error-config
checking for GPG Error - version >= 1.16... yes (1.25)
configure: WARNING:
***
*** The config script /usr/local/bin/gpg-error-config was
*** built for x86_64-pc-linux-gnu and thus may not match the
*** used host x86_64-unknown-linux-gnu.
*** You may want to use the configure option --with-gpg-error-prefix
*** to specify a matching config script or use $SYSROOT.
***
checking for libassuan-config... /usr/local/bin/libassuan-config
checking for LIBASSUAN - version >= 2.1.0... yes (2.4.3)
checking LIBASSUAN API version... okay
configure: WARNING:
***
*** The config script /usr/local/bin/libassuan-config was
*** built for x86_64-pc-linux-gnu and thus may not match the
*** used host x86_64-unknown-linux-gnu.
*** You may want to use the configure option --with-libassuan-prefix
*** to specify a matching config script or use $SYSROOT.
***
checking for byte typedef... no
checking for ulong typedef... yes
checking for setcap... /sbin/setcap
checking for cap_set_proc in -lcap... no
checking for pkg-config... no
checking for ncursesw... checking for ncurses... checking for initscr
in -lncursesw... no
checking for initscr in -lncurses... no
checking for tgetent in -lcurses... no
checking for tgetent in -ltermcap... no
checking for tgetent in -ltermlib... no
checking for initscr in -lcurses... no
checking if Unix domain socket is supported... yes
checking for pkg-config... no
checking for pkg-config... (cached) no
checking for Qt5Core >= 5.0.0 Qt5Gui >= 5.0.0 Qt5Widgets >= 5.0.0...
./configure: line 9744: no: command not found
./configure: line 9752: no: command not found
no
./configure: line 9770: no: command not found
checking for QtCore >= 4.4.0 QtGui >= 4.4.0... ./configure: line
10123: no: command not found
./configure: line 10131: no: command not found
no
configure: error: No pinentry enabled.

I appreciate any help, thanks.

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

gpg2 --version gpg: Fatal: libgcrypt is too old (need 1.7.0, have 1.6.3)

[murphy]

Hi David - I have run into this exact issue on various 32 bit machines
or OS that run as 32 bit, like raspberry pi.  I am certainly no expert
but this seems to consistently solve the problem.

sudo nano /etc/ld.so.conf

Then place the following as the first line:

include /etc/ld.so.conf.d/libc.conf

save and then:

sudo ldconfig

Best of luck!

Murphy




signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: smartcard reader

[Nix]

On 22 Oct 2016, Bjoern Kahl spake thusly:
>  I /think/ it worked exactly once.  But then I played a bit with the
>  PIV applet on the YubiKey (using yubico's piv-tool), and since then
>  I can not get to the OpenPGP applet on the YubiKey.  Only the PIV
>  works (I see my x509 certificates in there in Keychain and can used
>  in Safari to authenticate to for example StartSSL.com)

If you're using pcscd, there's no way this will work without at least
OpenSC 0.16.0, which was released quite recently (due to spec violations
in the Yubikey Neo and 4's PIV applet which have exactly the effects you
see). The master branch is more likely yet to work.

Getting both PIV and GPG to work simultaneously is an even bigger kettle
of pain :/

-- 
NULL && (void)

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users