Re: gpg: keyserver refresh failed: No keyserver available

2020-07-06 Thread Dmitry Alexandrov 
Jerry  wrote:
> I have not been able to refresh the keys on my system. I have run the 
> following command with the error as shown.
>
> gpg2 --refresh-keys
> gpg: enabled debug flags: memstat
> gpg: refreshing 168 keys from hkp://pool.sks-keyservers.net
> gpg: keyserver refresh failed: No keyserver available

> I don't believe it is a firewall problem, since there is no entry in the 
> firewall log to even suggest that gpg2 tried to access anything.

That is, your have not tried to check the connection on the same machine but 
with some other tool first?  Why?  FWIW, HKP is HTTP on port 11371.

> I have a Windows 10 machine that is using Kleopatra, on the same network, and 
> it is working perfectly.

I do not remember for sure, but is not it, at least, preconfigured to use HKPS, 
i. e. HTTP/TLS on port 443, if not some proprietary keyserver instead of SKS 
pool?


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

[Announce] Libgcrypt 1.8.6 released

2020-07-06 Thread Werner Koch via Gnupg-users 
Hi!

The GnuPG Project is pleased to announce the availability of Libgcrypt
version 1.8.6.  This is a maintenance release.

Libgcrypt is a general purpose library of cryptographic building blocks.
It is used by GnuPG and many other programs.  Libgcrypt does not provide
any implementation of OpenPGP, S/MIME, or other protocols.  Thorough
understanding of applied cryptography is required to use Libgcrypt.


Noteworthy changes in version 1.8.6
===

 * Bug fixes:

   - Fix build problems on OpenIndiana et al. [#4818]

   - Fix GCM bug on arm64 which troubles for example OMEMO.  [#4986]

   - Fix wrong code execution in Poly1305 ARM/NEON implementation.
 [#4833]

   - Detect a div-by-zero in a debug helper tool.  [#4868]

   - Use a constant time mpi_inv in some cases and change the order
 mpi_invm is called.  [#4869]

   - Fix mpi_copy to correctly handle flags of opaque MPIs.

   - Fix mpi_cmp to consider +0 and -0 the same.

 * Other features:

   - Add OIDs from RFC-8410 as aliases for Ed25519 and Curve25519.

 Release-info: https://dev.gnupg.org/T4985



Download


Source code is hosted at the GnuPG FTP server and its mirrors as listed
at .  On the primary server
the source tarball and its digital signature are:

 https://gnupg.org/ftp/gcrypt/libgcrypt/libgcrypt-1.8.6.tar.bz2
 https://gnupg.org/ftp/gcrypt/libgcrypt/libgcrypt-1.8.6.tar.bz2.sig

or gzip compressed:

 https://gnupg.org/ftp/gcrypt/libgcrypt/libgcrypt-1.8.6.tar.gz
 https://gnupg.org/ftp/gcrypt/libgcrypt/libgcrypt-1.8.6.tar.gz.sig

In order to check that the version of Libgcrypt you downloaded is an
original and unmodified file please follow the instructions found at
.  In short, you may
use one of the following methods:

 - Check the supplied OpenPGP signature.  For example to check the
   signature of the file libgcrypt-1.8.6.tar.bz2 you would use this
   command:

 gpg --verify libgcrypt-1.8.6.tar.bz2.sig libgcrypt-1.8.6.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 libgcrypt-1.8.6.tar.bz2, you run the command like this:

 sha1sum libgcrypt-1.8.6.tar.bz2

   and check that the output matches the first line from the
   this list:

406b02873833427898d16bcc8483bc5c91c73d4a  libgcrypt-1.8.6.tar.bz2
1aa882e816f6ab9375307f19f26c5ea7a5d27b76  libgcrypt-1.8.6.tar.gz

   You should also verify that the checksums above are authentic by
   matching them with copies of this announcement.  Those copies can be
   found at other mailing lists, web sites, and search engines.


Copying
===

Libgcrypt is distributed under the terms of the GNU Lesser General
Public License (LGPLv2.1+).  The helper programs as well as the
documentation are distributed under the terms of the GNU General Public
License (GPLv2+).  The file LICENSES has notices about contributions
that require that these additional notices are distributed.


Support
===

For help on developing with Libgcrypt you should read the included
manual and if needed ask on the gcrypt-devel mailing list.

In case of problems specific to this release please first check
 for updated information.

Please also consult the archive of the gcrypt-devel mailing list before
reporting a bug: .
We suggest to send bug reports for a new release to this list in favor
of filing a bug at .  If you need commercial
support go to  or .

If you are a developer and you need a certain feature for your project,
please do not hesitate to bring it to the gcrypt-devel mailing list for
discussion.


Thanks
==

Maintenance and development of GnuPG is mostly financed by donations.
The GnuPG project currently employs two full-time developers and one
contractor.  They all work exclusively on GnuPG and closely related
software like Libgcrypt, GPGME and Gpg4win.

We have to thank all the people who helped the GnuPG project, be it
testing, coding, translating, suggesting, auditing, administering the
servers, spreading the word, and answering questions on the mailing
lists.

Many thanks to our numerous financial supporters, both corporate and
individuals.  Without you it would not be possible to

gpg: keyserver refresh failed: No keyserver available

2020-07-06 Thread Jerry 
If this is the wrong place to ask this question, I apologize.

FreeBSD 11.4-RELEASE

I have not been able to refresh the keys on my system. I have run the
following command with the error as shown.

gpg2 --refresh-keys
gpg: enabled debug flags: memstat
gpg: refreshing 168 keys from hkp://pool.sks-keyservers.net
gpg: keyserver refresh failed: No keyserver available
gpg: keydb: handles=1 locks=0 parse=168 get=168
gpg:build=0 update=0 insert=0 delete=0
gpg:reset=0 found=168 not=1 cache=0 not=0
gpg: kid_not_found_cache: count=0 peak=0 flushes=0
gpg: sig_cache: total=0 cached=0 good=0 bad=0
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
  outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: rndjent stat: collector=0x calls=0 bytes=0
gpg: secmem usage: 0/32768 bytes in 0 blocks

This is the version info for gpg2:
gpg2 --version
gpg (GnuPG) 2.2.20
libgcrypt 1.8.5
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: /home/gerard/.gnupg
Supported algorithms:
Pubkey: RSA (1), ELG (16), DSA (17), ECDH (18), ECDSA (19), EDDSA (22)
Cipher: IDEA (S1), 3DES (S2), CAST5 (S3), BLOWFISH (S4), AES (S7),
AES192 (S8), AES256 (S9), TWOFISH (S10), CAMELLIA128 (S11),
CAMELLIA192 (S12), CAMELLIA256 (S13)
Hash: SHA1 (H2), RIPEMD160 (H3), SHA256 (H8), SHA384 (H9), SHA512 (H10),
  SHA224 (H11)
Compression: Uncompressed (Z0), ZIP (Z1), ZLIB (Z2), BZIP2 (Z3)

I don't believe it is a firewall problem, since there is no entry in
the firewall log to even suggest that gpg2 tried to access anything.

I have a Windows 10 machine that is using Kleopatra, on the same
network, and it is working perfectly.

I was hoping that someone could give me some suggestions on how to
debug this problem.

Thanks!

-- 
Jerry


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

Re: Accidentally deleted ~/.gnupg/pubring.gpg

2020-07-06 Thread renws via Gnupg-users 
Hi Michał,

Thanks for your reply. However I've never uploaded the public key to any 
keyservers, is it possible to recover the public key from the private key (I 
still have ~/.gnupg/private-keys-v1.d)?

Regards,
Wenshan

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