Re: Complete Ubuntu compile of GnuPG

2017-11-21 Thread Robert J. Hansen 
> The bash file works on a fresh install of Ubuntu 16.04, 17.10 and
> Raspbian Stretch (for Raspberry Pi).  Any suggestions for improvements?

Pass --enable-g13 --enable-wks-tools to your make invocation.

make -f build-aux/speedo.mk INSTALL_PREFIX=/usr/local \
  speedo_pkg_gnupg_configure='--enable-g13 --enable-wks-tools' \
  native

Also see https://wiki.gnupg.org/WKS .

Hope this helps!

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

Complete Ubuntu compile of GnuPG

2017-11-21 Thread murphy 
My goal is to compile the latest version of GnuPG for Ubuntu.  The
following bash file does pretty well:

cd ~/Downloads
version=gnupg-2.2.3
wget https://gnupg.org/ftp/gcrypt/gnupg/$version.tar.bz2
wget https://gnupg.org/ftp/gcrypt/gnupg/$version.tar.bz2.sig
tar xf $version.tar.bz2
cd $version
sudo apt-get update
sudo apt-get install -y libldap2-dev
sudo apt-get install -y gtk+-2
sudo apt-get install -y rng-tools
sudo apt-get install -y libbz2-dev
sudo apt-get install -y zlib1g-dev
sudo apt-get install -y libgmp-dev
sudo apt-get install -y nettle-dev
sudo apt-get install -y libgnutls28-dev
sudo apt-get install -y libsqlite3-dev
sudo apt-get install -y adns-tools
sudo apt-get install -y libreadline-dev
sudo apt-get install -y pinentry-gtk2
sudo apt-get install -y pcscd scdaemon
sudo make -f build-aux/speedo.mk native INSTALL_PREFIX=/usr/local
sudo ldconfig

But there are a couple of no answers I would like to eliminate:

GnuPG v2.2.3 has been configured as follows:

Revision:  97f4fea  (38900)
Platform:  GNU/Linux (x86_64-pc-linux-gnu)

OpenPGP:   yes
S/MIME:    yes
Agent: yes
Smartcard: yes (without internal CCID driver)
G13:   no
Dirmngr:   yes
Gpgtar:    yes
WKS tools: no

Protect tool:  (default)
LDAP wrapper:  (default)
Default agent: (default)
Default pinentry:  (default)
Default scdaemon:  (default)
Default dirmngr:   (default)

Dirmngr auto start:  yes
Readline support:    yes
LDAP support:    yes
TLS support: gnutls
TOFU support:    yes
Tor support: yes

Specifically G13 and WKS tools are not supported.  Am I missing some
dependencies?  Preferably they should be available via 'sudo apt-get
install' since this is checked for in new compiles and not reinstalled.

The bash file works on a fresh install of Ubuntu 16.04, 17.10 and
Raspbian Stretch (for Raspberry Pi).  Any suggestions for improvements?

Murphy



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

Which gnupg2-smime should I use for this build?

2017-11-21 Thread Dustin Rogers 
Hi gnupg users:


Which gnupg2-smime should I use here with this amazn linux?


Error: Package: gnupg2-smime-2.0.14-8.el6.x86_64 
(/gnupg2-smime-2.0.14-8.el6.x86_64)

   Requires: gnupg2 = 2.0.14-8.el6

   Installed: gnupg2-2.0.28-1.30.amzn1.x86_64 (installed)

   gnupg2 = 2.0.28-1.30.amzn1

You could try using --skip-broken to work around the problem

You could try running: rpm -Va --nofiles --nodigest


I found a 2.0.28 version for fedora core? Should I try that?


Thank you,

-Dustin

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

Re: Using the OpenPGP Card on Unix && Win7

2017-11-21 Thread Matthias Apitz 
El día martes, noviembre 21, 2017 a las 06:50:18p. m. +0900, NIIBE Yutaka 
escribió:

> Matthias Apitz  wrote:
> > The produced log is:
> >
> > $ cat ../AppData/Local/VirtualStore/Windows/SysWOW64/scdaemon.log
> [...]
> > 2017-11-21 08:24:04 scdaemon[3868.2] DBG: enter: apdu_open_reader: 
> > portstr=(null)
> > 2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'Broadcom Corp 
> > Contacted SmartCard 0'
> > 2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'Broadcom Corp 
> > Contactless SmartCard 0'
> > 2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'BROADCOM NFC 
> > Smartcard Reader 1'
> > 2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'Identiv uTrust 3512 
> > SAM slot Token 0'
> > 2017-11-21 08:24:04 scdaemon[3868.2] detected reader ''
> > 2017-11-21 08:24:04 scdaemon[3868.2] reader slot 0: not connected
> 
> You have five card readers (the last one looks strange, though).
> 
> GnuPG's scdaemon select the first one as default.  IIUC, you want to use
> 'Identiv uTrust 3512 SAM slot Token 0'.
> 
> In .gnupg/scdaemon.conf, you should have something like:
> ===
> reader-port "Identiv uTrust 3512 SAM slot Token"
> ===
> 
> ... to select the token.

Thanks! Adding the above line to GNUPGHOME/scdaemon.conf makes it all work,
even the GPA and other GUI tools.

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


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

Re: Getting more verbose details of a key

2017-11-21 Thread Peter Lebbing 
On 20/11/17 08:56, Werner Koch wrote:
> (Suggestions for the name of a shortcut command are welcome)
How about just --show? It was suggested in an unfriendly manner at
LWN[1], but apart from the unfriendliness, I do think it makes sense.

It does imply that it works for more than just keys, though. I wonder if
that is a bad thing. Wouldn't a command that just shows the contents of
a file without processing it make sense? It could show all that
--import-options show-only shows for keys, or show recipients for
encrypted files, signers for signed files (no verification), etcetera. A
less techy version of --list-only --list-packets.

Peter.

[1] 

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



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

Re: Using the OpenPGP Card on Unix && Win7

2017-11-21 Thread NIIBE Yutaka 
Matthias Apitz  wrote:
> The produced log is:
>
> $ cat ../AppData/Local/VirtualStore/Windows/SysWOW64/scdaemon.log
[...]
> 2017-11-21 08:24:04 scdaemon[3868.2] DBG: enter: apdu_open_reader: 
> portstr=(null)
> 2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'Broadcom Corp Contacted 
> SmartCard 0'
> 2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'Broadcom Corp 
> Contactless SmartCard 0'
> 2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'BROADCOM NFC Smartcard 
> Reader 1'
> 2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'Identiv uTrust 3512 SAM 
> slot Token 0'
> 2017-11-21 08:24:04 scdaemon[3868.2] detected reader ''
> 2017-11-21 08:24:04 scdaemon[3868.2] reader slot 0: not connected

You have five card readers (the last one looks strange, though).

GnuPG's scdaemon select the first one as default.  IIUC, you want to use
'Identiv uTrust 3512 SAM slot Token 0'.

In .gnupg/scdaemon.conf, you should have something like:
===
reader-port "Identiv uTrust 3512 SAM slot Token"
===

... to select the token.
-- 

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

Re: Using the OpenPGP Card on Unix && Win7

2017-11-21 Thread Matthias Apitz 



Hello,

Thanks, Werner, for the helping hand. I did so to capture the log of the 
scdaemon.
But did not used the nice trick of TCP, because I did not wanted to have the VM
up and running and blocking the OpenPGP Card on USB. I run all the GnuPG 
commands
from the DOS cmd shell, only the tail of the scdaemon.log was done in Cygwin.

The scdaemon.conf used was:

$ cat /cygdrive/c/Users/apitzm/AppData/Roaming/gnupg/scdaemon.conf
log-file scdaemon.log
debug-level guru
debug-all
debug-log-tid
card-timeout 30

The produced log is:

$ cat ../AppData/Local/VirtualStore/Windows/SysWOW64/scdaemon.log
2017-11-21 08:24:04 scdaemon[3868.1] Es wird auf Socket 
`C:\Users\apitzm\AppData\Roaming\gnupg\S.scdaemon' gehört
2017-11-21 08:24:04 scdaemon[3868.2] Handhabungsroutine für fd -1 gestartet
2017-11-21 08:24:04 scdaemon[3868.2] DBG: chan_0x00b0 -> OK GNU Privacy 
Guard's Smartcard server ready
2017-11-21 08:24:04 scdaemon[3868.2] DBG: chan_0x00b0 <- GETINFO socket_name
2017-11-21 08:24:04 scdaemon[3868.2] DBG: chan_0x00b0 -> D 
C:\Users\apitzm\AppData\Roaming\gnupg\S.scdaemon
2017-11-21 08:24:04 scdaemon[3868.2] DBG: chan_0x00b0 -> OK
2017-11-21 08:24:04 scdaemon[3868.2] DBG: chan_0x00b0 <- OPTION 
event-signal=f0
2017-11-21 08:24:04 scdaemon[3868.2] DBG: chan_0x00b0 -> OK
2017-11-21 08:24:04 scdaemon[3868.2] DBG: chan_0x00b0 <- serialno
2017-11-21 08:24:04 scdaemon[3868.2] DBG: enter: apdu_open_reader: 
portstr=(null)
2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'Broadcom Corp Contacted 
SmartCard 0'
2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'Broadcom Corp Contactless 
SmartCard 0'
2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'BROADCOM NFC Smartcard 
Reader 1'
2017-11-21 08:24:04 scdaemon[3868.2] detected reader 'Identiv uTrust 3512 SAM 
slot Token 0'
2017-11-21 08:24:04 scdaemon[3868.2] detected reader ''
2017-11-21 08:24:04 scdaemon[3868.2] reader slot 0: not connected
2017-11-21 08:24:04 scdaemon[3868.2] DBG: leave: apdu_open_reader => slot=0 
[pc/sc]
2017-11-21 08:24:04 scdaemon[3868.2] DBG: enter: apdu_connect: slot=0
2017-11-21 08:24:04 scdaemon[3868.2] pcsc_connect failed: removed card 
(0x80100069)
2017-11-21 08:24:04 scdaemon[3868.2] reader slot 0: not connected
2017-11-21 08:24:04 scdaemon[3868.2] DBG: leave: apdu_connect => sw=0x10008
2017-11-21 08:24:04 scdaemon[3868.2] DBG: enter: apdu_close_reader: slot=0
2017-11-21 08:24:04 scdaemon[3868.2] DBG: enter: apdu_disconnect: slot=0
2017-11-21 08:24:04 scdaemon[3868.2] DBG: leave: apdu_disconnect => sw=0x0
2017-11-21 08:24:04 scdaemon[3868.2] DBG: leave: apdu_close_reader => 0x0 
(close_reader)
2017-11-21 08:24:04 scdaemon[3868.2] DBG: chan_0x00b0 -> ERR 100696144 No 
such device 
2017-11-21 08:24:23 scdaemon[3868.2] DBG: chan_0x00b0 <- RESTART
2017-11-21 08:24:23 scdaemon[3868.2] DBG: chan_0x00b0 -> OK
2017-11-21 08:26:07 scdaemon[3868.2] DBG: chan_0x00b0 <- serialno
2017-11-21 08:26:07 scdaemon[3868.2] DBG: enter: apdu_open_reader: 
portstr=(null)
2017-11-21 08:26:07 scdaemon[3868.2] detected reader 'Broadcom Corp Contacted 
SmartCard 0'
2017-11-21 08:26:07 scdaemon[3868.2] detected reader 'Broadcom Corp Contactless 
SmartCard 0'
2017-11-21 08:26:07 scdaemon[3868.2] detected reader 'BROADCOM NFC Smartcard 
Reader 1'
2017-11-21 08:26:07 scdaemon[3868.2] detected reader 'Identiv uTrust 3512 SAM 
slot Token 0'
2017-11-21 08:26:07 scdaemon[3868.2] detected reader ''
2017-11-21 08:26:07 scdaemon[3868.2] reader slot 0: not connected
2017-11-21 08:26:07 scdaemon[3868.2] DBG: leave: apdu_open_reader => slot=0 
[pc/sc]
2017-11-21 08:26:07 scdaemon[3868.2] DBG: enter: apdu_connect: slot=0
2017-11-21 08:26:07 scdaemon[3868.2] pcsc_connect failed: removed card 
(0x80100069)
2017-11-21 08:26:07 scdaemon[3868.2] reader slot 0: not connected
2017-11-21 08:26:07 scdaemon[3868.2] DBG: leave: apdu_connect => sw=0x10008
2017-11-21 08:26:07 scdaemon[3868.2] DBG: enter: apdu_close_reader: slot=0
2017-11-21 08:26:07 scdaemon[3868.2] DBG: enter: apdu_disconnect: slot=0
2017-11-21 08:26:07 scdaemon[3868.2] DBG: leave: apdu_disconnect => sw=0x0
2017-11-21 08:26:07 scdaemon[3868.2] DBG: leave: apdu_close_reader => 0x0 
(close_reader)
2017-11-21 08:26:07 scdaemon[3868.2] DBG: chan_0x00b0 -> ERR 100696144 No 
such device 
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 <- help
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 -> # NOP
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 -> # CANCEL
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 -> # OPTION
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 -> # BYE
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 -> # AUTH
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 -> # RESET
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 -> # END
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 -> # HELP
2017-11-21 08:26:46 scdaemon[3868.2] DBG: chan_0x00b0 -> # SERIALNO 
[--demand=] []
2

[Announce] GnuPG 2.2.3 released

2017-11-21 Thread Werner Koch 
Hello!

We are is pleased to announce the availability of a new GnuPG release:
version 2.2.3.  This is a maintenance release; see below for a list of
fixed bugs.


About GnuPG
===

The GNU Privacy Guard (GnuPG) is a complete and free implementation
of the OpenPGP standard which is commonly abbreviated as PGP.

GnuPG allows to encrypt and sign data and communication, features a
versatile key management system as well as access modules for public key
directories.  GnuPG itself is a command line tool with features for easy
integration with other applications.  A wealth of frontend applications
and libraries making use of GnuPG are available.  As an Universal Crypto
Engine GnuPG provides support for S/MIME and Secure Shell in addition to
OpenPGP.

GnuPG is Free Software (meaning that it respects your freedom).  It can
be freely used, modified and distributed under the terms of the GNU
General Public License.


Noteworthy changes in version 2.2.3
===

  * gpgsm: Fix initial keybox creation on Windows. [#3507]

  * dirmngr: Fix crash in case of a CRL loading error. [#3510]

  * Fix the name of the Windows registry key. [Git#4f5afaf1fd]

  * gpgtar: Fix wrong behaviour of --set-filename. [#3500]

  * gpg: Silence AKL retrieval messages. [#3504]

  * agent: Use clock or clock_gettime for calibration. [#3056]

  * agent: Improve robustness of the shutdown pending
state. [Git#7ffedfab89]


Getting the Software


Please follow the instructions found at  or
read on:

GnuPG 2.2.3 may be downloaded from one of the GnuPG mirror sites or
direct from its primary FTP server.  The list of mirrors can be found at
.  Note that GnuPG is not
available at ftp.gnu.org.

The GnuPG source code compressed using BZIP2 and its OpenPGP signature
are available here:

 https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.3.tar.bz2 (6393k)
 https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.3.tar.bz2.sig

An installer for Windows without any graphical frontend except for a
very minimal Pinentry tool is available here:

 https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.3_20171120.exe (3806k)
 https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.3_20171120.exe.sig

The source used to build the Windows installer can be found in the same
directory with a ".tar.xz" suffix.  A new Gpg4win 3.0 installer
featuring this version of GnuPG will be available soon.


Checking the Integrity
==

In order to check that the version of GnuPG which you are going to
install is an original and unmodified one, you can do it in one of
the following ways:

 * If you already have a version of GnuPG installed, you can simply
   verify the supplied signature.  For example to verify the signature
   of the file gnupg-2.2.3.tar.bz2 you would use this command:

 gpg --verify gnupg-2.2.3.tar.bz2.sig gnupg-2.2.3.tar.bz2

   This checks whether the signature file matches the source file.
   You should see a message indicating that the signature is good and
   made by one or more of the release signing keys.  Make sure that
   this is a valid key, either by matching the shown fingerprint
   against a trustworthy list of valid release signing keys or by
   checking that the key has been signed by trustworthy other keys.
   See the end of this mail for information on the signing keys.

 * If you are not able to use an existing version of GnuPG, you have
   to verify the SHA-1 checksum.  On Unix systems the command to do
   this is either "sha1sum" or "shasum".  Assuming you downloaded the
   file gnupg-2.2.3.tar.bz2, you run the command like this:

 sha1sum gnupg-2.2.3.tar.bz2

   and check that the output matches the next line:

68ed37d363166b5bd79971537484148eb8f2958c  gnupg-2.2.3.tar.bz2
9914e93d5ac50b4e542b4320e1e130dc1552e24b  gnupg-w32-2.2.3_20171120.exe
74d3d9565b4baa5627932b20af557645d7915e77  gnupg-w32-2.2.3_20171120.tar.xz


Internationalization


This version of GnuPG has support for 26 languages with Chinese, Czech,
French, German, Japanese, Norwegian, Russian, and Ukrainian being almost
completely translated.


Documentation and Support
=

If you used GnuPG in the past you should read the description of
changes and new features at doc/whats-new-in-2.1.txt or online at

  https://gnupg.org/faq/whats-new-in-2.1.html

The file gnupg.info has the complete reference manual of the system.
Separate man pages are included as well but they miss some of the
details availabale only in thee manual.  The manual is also available
online at

  https://gnupg.org/documentation/manuals/gnupg/

or can be downloaded as PDF at

  https://gnupg.org/documentation/manuals/gnupg.pdf .

The chapters on gpg-agent, gpg and gpgsm include information on how to
set up the whole thing.  You may also want to search the GnuPG mailing
list archives or ask on the gnupg-users mailing list for advise on how
to sol