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

[David Adamson]

I wasn't exactly methodical in my approach to resolve the issue but I
"think" what resolved my issue preventing me from generating keys was
following Stephan's suggestion of adding to .bashrc, which I had done
and was still getting the issue but tonight I added the lines to
.bashrc of root.

Or it could have been Peter's suggestion of rm trustdb.gpg.

Anyhow I have successfully generated pub and secret key.  I am getting
a gui pop up requesting I enter a passphrase when generating a key
which was not my initial goal but I'm glad to have something working
than nothing.

I have a feeling I'm not out of the woods quite yet but that's ok.  I
appreciate you guys helping me work through this gpg software.  I
still have lots of questions about what kind of questions I should
have but that will come.


David

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

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

[Stephan Beck]

Peter Lebbing:
> On 23/11/16 11:14, Stephan Beck wrote:
>> [...] and properly symlink
>> /usr/bin/pinentry to the pinentry-curses you actually would like to use
>> if you are using text-mode only, I don't know why it should not work.
> 
[...]So by installing the Debian pinentry-curses
> package, David should already have a /usr/bin/pinentry.
> 
Yes, it has helped, thanks. But I looked at one of the OP's previous
mail and was confirmed.

> I looked for a GUI platform but had no idea what it's called where to
> find it and why I need a GUI if I plan on using purely command line
> interface.

So, I am puzzled by the fact that he switched to GUI pinentry that
quickly, without providing more info on the error, so I proposed to get
the maximum amount of info possible using the debug-level flag.

Cheers

Stephan


0x4218732B.asc
Description: application/pgp-keys


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

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

[Peter Lebbing]

On 23/11/16 07:44, David Adamson wrote:
> Werner was GTK+-2.0 a potential option for an appropriate development
> package for the GUI platform?

(I'm not Werner :) Yes, GTK+-2 is one of the pinentries. It's the one I
use, on my XFCE Debian jessie.

> gpg: lookup_hashtable failed: Unknown system error
> gpg: trustdb: searching trust record failed: Unknown system error
> gpg: Error: The trustdb is corrupted.
> gpg: You may try to re-create the trustdb using the commands:
> gpg:   cd ~/.gnupg
> gpg:   gpg --export-ownertrust > otrust.tmp
> gpg:   rm trustdb.gpg
> gpg:   gpg --import-ownertrust < otrust.tmp
> gpg: If that does not work, please consult the manual

Argh. Just do the "rm trustdb.gpg", it contains the ownertrust values
you have assigned to other people's keys (well, okay, as well as your
own). I'm under the impression you're starting out cleanly, without
keys, so the file would have been empty anyway.

> So with one issue solved now on to the next.  I'm sorry but this can't
> be right. Anyone know why I am running into so many issues?

Murphy, probably :-). I think it's just bad luck.

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: configure warnings and errors upon ./configure for Pinentry v0.9.7

[Peter Lebbing]

On 23/11/16 11:14, Stephan Beck wrote:
> [...] and properly symlink
> /usr/bin/pinentry to the pinentry-curses you actually would like to use
> if you are using text-mode only, I don't know why it should not work.

Good one, the symlink. It makes me wonder: is the agent looking in the
right place for the pinentry? Perhaps if you compile your own GnuPG and
install it in /usr/local/*, it will look for /usr/local/bin/pinentry only?

The Debian jessie pinentry-curses package uses the alternatives system,
which means that /usr/bin/pinentry will be a symlink to
/etc/alternatives/pinentry, and if the only pinentry alternative is
pinentry-curses, that will in turn be a symlink to
/usr/bin/pinentry-curses. So by installing the Debian pinentry-curses
package, David should already have a /usr/bin/pinentry.

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: configure warnings and errors upon ./configure for Pinentry v0.9.7

[Stephan Beck]

Hi,

David Adamson:
> On Mon, Nov 21, 2016 at 8:15 PM, Stephan Beck  wrote:
>> Ah, I forgot one thing: you have to add the following to your ~/.bashrc
>> file:
>> GPG_TTY=$(tty)
>> export GPG_TTY
>>
>> Does it work now?
>>
>> HTH
>>
>> Stephan
> 
> Stephan I updated the .bashrc file in my home directory, still got the
> same error, so I restarted the system but unfortunately the error
> remains.
> 
> Thanks for the assistance.

You haven't answered the question if you only want to use text-mode.
If you only use text-mode, add those lines mentioned to ~/.bashrc (or
whatever may be your shell initialization file) and properly symlink
/usr/bin/pinentry to the pinentry-curses you actually would like to use
if you are using text-mode only, I don't know why it should not work.
I refer you to the info gnupg manual and its appropriate section
10.3 Commonly Seen Problems.
 * The Curses based Pinentry does not work

Maybe it's helpful for you and for all willing to help if you properly
document the output of gen-key with the debug flag set to expert or guru
level.

gpg2 --gen-key --debug-level [expert|guru]

Just a suggestion.

Cheers,

Stephan

P.S. I now see that you have installed gtk-pinentry, so maybe I was
wrong and you don't want to use text-mode.


0x4218732B.asc
Description: application/pgp-keys


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

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

[David Adamson]

On Mon, Nov 21, 2016 at 4:16 AM, Werner Koch  wrote:
>
>> configure: error: No pinentry enabled.
>
> You need to install the appropriate development package for the GUI
> platform.
>
>
> Salam-Shalom,
>
>Werner
>
> --
> Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.

Werner was GTK+-2.0 a potential option for an appropriate development
package for the GUI platform?

After installing GTK+-2.0 I was successfully able to complete the
install of pinentry, However during the --gen-key process while
generating entropy I got the following errors:

We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: lookup_hashtable failed: Unknown system error
gpg: trustdb: searching trust record failed: Unknown system error
gpg: Error: The trustdb is corrupted.
gpg: You may try to re-create the trustdb using the commands:
gpg:   cd ~/.gnupg
gpg:   gpg --export-ownertrust > otrust.tmp
gpg:   rm trustdb.gpg
gpg:   gpg --import-ownertrust < otrust.tmp
gpg: If that does not work, please consult the manual


So with one issue solved now on to the next.  I'm sorry but this can't
be right. Anyone know why I am running into so many issues?

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

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

[David Adamson]

On Mon, Nov 21, 2016 at 8:15 PM, Stephan Beck  wrote:
> Ah, I forgot one thing: you have to add the following to your ~/.bashrc
> file:
> GPG_TTY=$(tty)
> export GPG_TTY
>
> Does it work now?
>
> HTH
>
> Stephan

Stephan I updated the .bashrc file in my home directory, still got the
same error, so I restarted the system but unfortunately the error
remains.

Thanks for the assistance.

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

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

[Stephan Beck]

Hi,

David Adamson:
> On Mon, Nov 21, 2016 at 12:33 PM, Stephan Beck  wrote:
>> Hi,
>>
>> David Adamson:
>>
>> If you only want to use the command line (i.e. text mode) and do not
>> need a GUI, you'll probably need the pinentry-curses package. Install it
>> by typing: sudo apt-get install pinentry-curses
> 
> Thanks for the tip. I just tried your suggestion, installed
> pinentry-curses, which installed without error but I am getting the
> same error when trying generate keys, just as before.

Ah, I forgot one thing: you have to add the following to your ~/.bashrc
file:
GPG_TTY=$(tty)
export GPG_TTY

Does it work now?

HTH

Stephan


0x4218732B.asc
Description: application/pgp-keys


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

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

[David Adamson]

On Mon, Nov 21, 2016 at 12:33 PM, Stephan Beck  wrote:
> Hi,
>
> David Adamson:
>
> If you only want to use the command line (i.e. text mode) and do not
> need a GUI, you'll probably need the pinentry-curses package. Install it
> by typing: sudo apt-get install pinentry-curses

Thanks for the tip. I just tried your suggestion, installed
pinentry-curses, which installed without error but I am getting the
same error when trying generate keys, just as before.


> There's one thing I don't really understand:
> In your first mail you talked about your laptop with Debian Jessie, and
> that it has gnupg 1.4.18 pre-installed. I think the whole info should
> be: Debian Jessie (standard install) has gnupg 1.4.18 AND gnupg 2.0.26
> pre-installed. Or how would you be able to issue a command gpg2 at all?
> Or do you have a text-mode only pre-installed Debian Jessie with both
> gnupg versions?

You're right there's some information I accidentally left out. I have
a standard debian 8 jessie install which included gnupg v 1.4.18. I
then downloaded and installed from gnupg.org the source code for
version GnuPG modern 2.1.16 and needed libraries. With that said you
can pick up with the opening line of this thread. I hope I didn't
leave anything out this time.

I'm really starting to feel I missed a step along the way and messed
up the install.  I suppose I could do a fresh install  of the OS and
just use the 1.4.18 version otherwise I'm not aware of what to do
differently on my second attempt. I feel as though I followed the
instructions. It probably some basic linux config that I'm too new to
know about, LOL.

Thanks.

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

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

[Stephan Beck]

Hi,

David Adamson:
> On Mon, Nov 21, 2016 at 4:16 AM, Werner Koch  wrote:
> 
>>> configure: error: No pinentry enabled.
>>
>> You need to install the appropriate development package for the GUI
>> platform.
> 
> I looked for a GUI platform but had no idea what it's called where to
> find it and why I need a GUI if I plan on using purely command line
> interface.
> 
> Would It be:
> "GPA is a graphical frontend to GnuPG"
> 
> Thanks for your help!

If you only want to use the command line (i.e. text mode) and do not
need a GUI, you'll probably need the pinentry-curses package. Install it
by typing: sudo apt-get install pinentry-curses

There's one thing I don't really understand:
In your first mail you talked about your laptop with Debian Jessie, and
that it has gnupg 1.4.18 pre-installed. I think the whole info should
be: Debian Jessie (standard install) has gnupg 1.4.18 AND gnupg 2.0.26
pre-installed. Or how would you be able to issue a command gpg2 at all?
Or do you have a text-mode only pre-installed Debian Jessie with both
gnupg versions?

HTH

Stephan


0x4218732B.asc
Description: application/pgp-keys


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

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

[David Adamson]

On Mon, Nov 21, 2016 at 4:16 AM, Werner Koch  wrote:

>> configure: error: No pinentry enabled.
>
> You need to install the appropriate development package for the GUI
> platform.

I looked for a GUI platform but had no idea what it's called where to
find it and why I need a GUI if I plan on using purely command line
interface.

Would It be:
"GPA is a graphical frontend to GnuPG"

Thanks for your help!

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

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

[Werner Koch]

On Sat, 19 Nov 2016 21:51, davidadamson...@gmail.com said:

> *** 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.

This warning is a bit unfortunate but it is harmless.  Both platform
triplets indicate the same platform.

The names of these triplets are sometimes changed and when you are using
an older version of a library you may see such a warning.  The reason
why we print this warning is to be able to figure out build problems in
case of non properly installed systems where a native library and a
library used for cross-compiling are mixed up.

> checking for Qt5Core >= 5.0.0 Qt5Gui >= 5.0.0 Qt5Widgets >= 5.0.0...
> ./configure: line 9744: no: command not found

The "no" is a minor bug in the configure script - it is mostly harmless.

> configure: error: No pinentry enabled.

You need to install the appropriate development package for the GUI
platform.


Salam-Shalom,

   Werner

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


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

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

[David Adamson]

Thanks Krzysztof. I did apt-get install pinentry-qt4 although it was
an older (0.8.3-2) version than what is on gnupg . org. It installed
without any errors but when I run gpg2 --gen-key I'm still getting:

We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: agent_genkey failed: No pinentry
Key generation failed: No pinentry

There is no delay in the error - it occurs at the same time the text
above is displayed.

___
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