Ошибка internal error no matching private keys available

Code: Select all

ServerRoot "/opt/rh/httpd24/root/etc/httpd"
Listen 80
#Listen 443
Include conf.modules.d/*.conf
User apache
Group apache
ServerAdmin root@localhost
DocumentRoot "/opt/rh/httpd24/root/var/www/html"
<Directory "/opt/rh/httpd24/root/var/www">
Options +SymLinksIfOwnerMatch
    AllowOverride all
    # Allow open access:
    Require all granted
</Directory>

# Further relax access to the default document root:
<Directory "/opt/rh/httpd24/root/var/www/html">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.4/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks
Options +SymLinksIfOwnerMatch
    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    #
    AllowOverride all

    #
    # Controls who can get stuff from this server.
    #
    Require all granted
    <IfModule dir_module>
    DirectoryIndex index.php index.html index.htm home.html home.htm
    <Files ".ht*">
    Require all denied
</Files>
</IfModule>
</Directory>
ErrorLog "logs/error_log"
LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t "%r" %>s %b "%{Referer}i" "%{User-Agent}i"" combined
    LogFormat "%h %l %u %t "%r" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t "%r" %>s %b "%{Referer}i" "%{User-Agent}i" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    #CustomLog "logs/access_log" common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    CustomLog "logs/access_log" combined
</IfModule>
<IfModule alias_module>
ScriptAlias /cgi-bin/ "/opt/rh/httpd24/root/var/www/cgi-bin/"

</IfModule>
<Directory "/opt/rh/httpd24/root/var/www/cgi-bin">
    AllowOverride None
    Options None
    Require all granted
</Directory>
<IfModule mime_module>
TypesConfig /etc/mime.types
 AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz
 AddType text/html .shtml
    AddOutputFilter INCLUDES .shtml
</IfModule>
AddDefaultCharset UTF-8

<IfModule mime_magic_module>
    #
    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type.  The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    #
    MIMEMagicFile conf/magic
</IfModule>
EnableSendfile on

# Supplemental configuration
#
# Load config files in the "/etc/httpd/conf.d" directory, if any.
IncludeOptional conf.d/*.conf

Code: Select all

<Directory /usr/share/www>
        AllowOverride All
        Options FollowSymLinks
        Require all granted
        Order deny,allow
        Allow from all
<IfVersion < 2.4>
    Allow from all
</IfVersion>
<IfVersion >= 2.4>
    Require all granted
</IfVersion>
        # rewrite for backward compability of public links
        RedirectMatch "^/pydio_public/(.*)" "/pydio/public/$1"
</Directory>

<VirtualHost files.bencor.info:80>
        DocumentRoot "/usr/share/www"
        ServerName test.bencor.info
</VirtualHost>
<VirtualHost files.bencor.info:443>
        ServerName files.bencor.info
        ServerAdmin massimo.mucci@bencorinc.com
####### HOME PAGE: PYDIO #######
#       SSLEngine on
        SSLCertificateFile /etc/pki/tls/files_bencor_info.crt
        SSLCertificateKeyFile /etc/pki/tls/files_bencor_info.key
        SSLCertificateChainFile /etc/pki/tls/files_bencor_info.ca-bundle
        DocumentRoot /usr/share/www
        ErrorLog logs/rd_error_log
        TransferLog logs/rd_access_log
</VirtualHost>

Code: Select all

# When we also provide SSL we have to listen to the 
# the HTTPS port in addition.
#
#Listen 443 https

##
##  SSL Global Context
##
##  All SSL configuration in this context applies both to
##  the main server and all SSL-enabled virtual hosts.
##

#   Pass Phrase Dialog:
#   Configure the pass phrase gathering process.
#   The filtering dialog program (`builtin' is a internal
#   terminal dialog) has to provide the pass phrase on stdout.
SSLPassPhraseDialog builtin

#   Inter-Process Session Cache:
#   Configure the SSL Session Cache: First the mechanism 
#   to use and second the expiring timeout (in seconds).
SSLSessionCache         shmcb:/opt/rh/httpd24/root/var/run/httpd/sslcache(512000)
SSLSessionCacheTimeout  300

#   Pseudo Random Number Generator (PRNG):
#   Configure one or more sources to seed the PRNG of the 
#   SSL library. The seed data should be of good random quality.
#   WARNING! On some platforms /dev/random blocks if not enough entropy
#   is available. This means you then cannot use the /dev/random device
#   because it would lead to very long connection times (as long as
#   it requires to make more entropy available). But usually those
#   platforms additionally provide a /dev/urandom device which doesn't
#   block. So, if available, use this one instead. Read the mod_ssl User
#   Manual for more details.
SSLRandomSeed startup file:/dev/urandom  256
SSLRandomSeed connect builtin
#SSLRandomSeed startup file:/dev/random  512
#SSLRandomSeed connect file:/dev/random  512
#SSLRandomSeed connect file:/dev/urandom 512

#
# Use "SSLCryptoDevice" to enable any supported hardware
# accelerators. Use "openssl engine -v" to list supported
# engine names.  NOTE: If you enable an accelerator and the
# server does not start, consult the error logs and ensure
# your accelerator is functioning properly. 
#
SSLCryptoDevice builtin
#SSLCryptoDevice ubsec

##
## SSL Virtual Host Context
##

<VirtualHost _default_:443>

# General setup for the virtual host, inherited from global configuration
#DocumentRoot "/var/www/html"
#ServerName www.example.com:443

# Use separate log files for the SSL virtual host; note that LogLevel
# is not inherited from httpd.conf.
ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log
LogLevel warn

#   SSL Engine Switch:
#   Enable/Disable SSL for this virtual host.
#SSLEngine on

#   SSL Protocol support:
# List the enable protocol levels with which clients will be able to
# connect.  Disable SSLv2 access by default:
SSLProtocol all -SSLv2

#   SSL Cipher Suite:
#   List the ciphers that the client is permitted to negotiate.
#   See the mod_ssl documentation for a complete list.
SSLCipherSuite HIGH:MEDIUM:!aNULL:!MD5

#   Speed-optimized SSL Cipher configuration:
#   If speed is your main concern (on busy HTTPS servers e.g.),
#   you might want to force clients to specific, performance
#   optimized ciphers. In this case, prepend those ciphers
#   to the SSLCipherSuite list, and enable SSLHonorCipherOrder.
#   Caveat: by giving precedence to RC4-SHA and AES128-SHA
#   (as in the example below), most connections will no longer
#   have perfect forward secrecy - if the server's key is
#   compromised, captures of past or future traffic must be
#   considered compromised, too.
#SSLCipherSuite RC4-SHA:AES128-SHA:HIGH:MEDIUM:!aNULL:!MD5
#SSLHonorCipherOrder on 

#   Server Certificate:
# Point SSLCertificateFile at a PEM encoded certificate.  If
# the certificate is encrypted, then you will be prompted for a
# pass phrase.  Note that a kill -HUP will prompt again.  A new
# certificate can be generated using the genkey(1) command.
#SSLCertificateFile /etc/ssl/certs/files_bencor_info.crt

#   Server Private Key:
#   If the key is not combined with the certificate, use this
#   directive to point at the key file.  Keep in mind that if
#   you've both a RSA and a DSA private key you can configure
#   both in parallel (to also allow the use of DSA ciphers, etc.)
#SSLCertificateKeyFile /etc/ssl/certs/bencor.key

#   Server Certificate Chain:
#   Point SSLCertificateChainFile at a file containing the
#   concatenation of PEM encoded CA certificates which form the
#   certificate chain for the server certificate. Alternatively
#   the referenced file can be the same as SSLCertificateFile
#   when the CA certificates are directly appended to the server
#   certificate for convinience.
#SSLCertificateChainFile /etc/ssl/certs/files_bencor_info.ca-bundle ***

#   Certificate Authority (CA):
#   Set the CA certificate verification path where to find CA
#   certificates for client authentication or alternatively one
#   huge file containing all of them (file must be PEM encoded)
#SSLCACertificateFile /etc/ssl/certs/files_bencor_info.crt

#   Client Authentication (Type):
#   Client certificate verification type and depth.  Types are
#   none, optional, require and optional_no_ca.  Depth is a
#   number which specifies how deeply to verify the certificate
#   issuer chain before deciding the certificate is not valid.
#SSLVerifyClient require
#SSLVerifyDepth  10

#   Access Control:
#   With SSLRequire you can do per-directory access control based
#   on arbitrary complex boolean expressions containing server
#   variable checks and other lookup directives.  The syntax is a
#   mixture between C and Perl.  See the mod_ssl documentation
#   for more details.
#<Location />
#SSLRequire (    %{SSL_CIPHER} !~ m/^(EXP|NULL)/ 
#            and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." 
#            and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} 
#            and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 
#            and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20       ) 
#           or %{REMOTE_ADDR} =~ m/^192.76.162.[0-9]+$/
#</Location>

#   SSL Engine Options:
#   Set various options for the SSL engine.
#   o FakeBasicAuth:
#     Translate the client X.509 into a Basic Authorisation.  This means that
#     the standard Auth/DBMAuth methods can be used for access control.  The
#     user name is the `one line' version of the client's X.509 certificate.
#     Note that no password is obtained from the user. Every entry in the user
#     file needs this password: `xxj31ZMTZzkVA'.
#   o ExportCertData:
#     This exports two additional environment variables: SSL_CLIENT_CERT and
#     SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
#     server (always existing) and the client (only existing when client
#     authentication is used). This can be used to import the certificates
#     into CGI scripts.
#   o StdEnvVars:
#     This exports the standard SSL/TLS related `SSL_*' environment variables.
#     Per default this exportation is switched off for performance reasons,
#     because the extraction step is an expensive operation and is usually
#     useless for serving static content. So one usually enables the
#     exportation for CGI and SSI requests only.
#   o StrictRequire:
#     This denies access when "SSLRequireSSL" or "SSLRequire" applied even
#     under a "Satisfy any" situation, i.e. when it applies access is denied
#     and no other module can change it.
#   o OptRenegotiate:
#     This enables optimized SSL connection renegotiation handling when SSL
#     directives are used in per-directory context. 
#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
<Files ~ ".(cgi|shtml|phtml|php3?)$">
    SSLOptions +StdEnvVars
</Files>
<Directory "/var/www/cgi-bin">
    SSLOptions +StdEnvVars
</Directory>

#   SSL Protocol Adjustments:
#   The safe and default but still SSL/TLS standard compliant shutdown
#   approach is that mod_ssl sends the close notify alert but doesn't wait for
#   the close notify alert from client. When you need a different shutdown
#   approach you can use one of the following variables:
#   o ssl-unclean-shutdown:
#     This forces an unclean shutdown when the connection is closed, i.e. no
#     SSL close notify alert is send or allowed to received.  This violates
#     the SSL/TLS standard but is needed for some brain-dead browsers. Use
#     this when you receive I/O errors because of the standard approach where
#     mod_ssl sends the close notify alert.
#   o ssl-accurate-shutdown:
#     This forces an accurate shutdown when the connection is closed, i.e. a
#     SSL close notify alert is send and mod_ssl waits for the close notify
#     alert of the client. This is 100% SSL/TLS standard compliant, but in
#     practice often causes hanging connections with brain-dead browsers. Use
#     this only for browsers where you know that their SSL implementation
#     works correctly. 
#   Notice: Most problems of broken clients are also related to the HTTP
#   keep-alive facility, so you usually additionally want to disable
#   keep-alive for those clients, too. Use variable "nokeepalive" for this.
#   Similarly, one has to force some clients to use HTTP/1.0 to workaround
#   their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
#   "force-response-1.0" for this.
BrowserMatch "MSIE [2-5]" 
         nokeepalive ssl-unclean-shutdown 
         downgrade-1.0 force-response-1.0

#   Per-Server Logging:
#   The home of a custom SSL log file. Use this when you want a
#   compact non-error SSL logfile on a virtual host basis.
CustomLog logs/ssl_request_log 
          "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x "%r" %b"

</VirtualHost>                    

Code: Select all

[root@files tls]# ls -ls private/
total 8
4 -rwx------  1 apache apache 1704 Oct 18 10:27 files_bencor_info.key
4 -rw-------. 1 apache apache 1675 Mar  1  2017 localhost.key
[root@files tls]# ls -ls certs/
total 28
0 lrwxrwxrwx  1 apache apache   49 Mar  1  2017 ca-bundle.crt -> /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
0 lrwxrwxrwx  1 apache apache   55 Mar  1  2017 ca-bundle.trust.crt -> /etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt
8 -rwx------  1 apache apache 4111 Feb 11  2014 files_bencor_info.ca-bundle
4 -rwx------  1 apache apache 2057 Oct 18 00:00 files_bencor_info.crt
0 drwx------  2 apache apache   85 Oct 18 10:25 keys.old
4 -rwx------. 1 apache apache 1468 Mar  1  2017 localhost.crt
4 -rwx------  1 apache apache  610 Aug  4 01:41 make-dummy-cert
4 -rwx------  1 apache apache 2516 Aug  4 01:41 Makefile
4 -rwx------  1 apache apache  829 Aug  4 01:41 renew-dummy-cert

Code: Select all

[root@files httpd]# systemctl status httpd24-httpd -l
● httpd24-httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd24-httpd.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2017-10-19 09:52:17 CDT; 11s ago
  Process: 34588 ExecStop=/opt/rh/httpd24/root/usr/sbin/httpd-scl-wrapper $OPTIONS -k graceful-stop (code=exited, status=0/SUCCESS)
  Process: 34586 ExecStart=/opt/rh/httpd24/root/usr/sbin/httpd-scl-wrapper $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
 Main PID: 34586 (code=exited, status=1/FAILURE)

Oct 19 09:52:16 files.bencor.info systemd[1]: Starting The Apache HTTP Server...
Oct 19 09:52:16 files.bencor.info systemd[1]: httpd24-httpd.service: main process exited, code=exited, status=1/FAILURE
Oct 19 09:52:17 files.bencor.info httpd-scl-wrapper[34588]: httpd (no pid file) not running
Oct 19 09:52:17 files.bencor.info systemd[1]: Failed to start The Apache HTTP Server.
Oct 19 09:52:17 files.bencor.info systemd[1]: Unit httpd24-httpd.service entered failed state.
Oct 19 09:52:17 files.bencor.info systemd[1]: httpd24-httpd.service failed.

Code: Select all

[root@files httpd]# systemctl status httpd24-httpd -l
● httpd24-httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd24-httpd.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2017-10-19 09:47:02 CDT; 6s ago
  Process: 34433 ExecStop=/opt/rh/httpd24/root/usr/sbin/httpd-scl-wrapper $OPTIONS -k graceful-stop (code=exited, status=1/FAILURE)
  Process: 34431 ExecStart=/opt/rh/httpd24/root/usr/sbin/httpd-scl-wrapper $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
 Main PID: 34431 (code=exited, status=1/FAILURE)

Oct 19 09:47:02 files.bencor.info systemd[1]: Starting The Apache HTTP Server...
Oct 19 09:47:02 files.bencor.info httpd-scl-wrapper[34431]: AH00526: Syntax error on line 116 of /opt/rh/httpd24/root/etc/httpd/conf.d/ssl.conf:
Oct 19 09:47:02 files.bencor.info httpd-scl-wrapper[34431]: SSLCertificateChainFile takes one argument, SSL Server CA Certificate Chain file ('/path/to/file' - PEM encoded)
Oct 19 09:47:02 files.bencor.info systemd[1]: httpd24-httpd.service: main process exited, code=exited, status=1/FAILURE
Oct 19 09:47:02 files.bencor.info httpd-scl-wrapper[34433]: AH00526: Syntax error on line 116 of /opt/rh/httpd24/root/etc/httpd/conf.d/ssl.conf:
Oct 19 09:47:02 files.bencor.info httpd-scl-wrapper[34433]: SSLCertificateChainFile takes one argument, SSL Server CA Certificate Chain file ('/path/to/file' - PEM encoded)
Oct 19 09:47:02 files.bencor.info systemd[1]: httpd24-httpd.service: control process exited, code=exited status=1
Oct 19 09:47:02 files.bencor.info systemd[1]: Failed to start The Apache HTTP Server.
Oct 19 09:47:02 files.bencor.info systemd[1]: Unit httpd24-httpd.service entered failed state.
Oct 19 09:47:02 files.bencor.info systemd[1]: httpd24-httpd.service failed.

Code: Select all

[root@files certs]#  openssl x509 -inform der -in files_bencor_info.crt -out files_bencor_info.pem
unable to load certificate
140134402181024:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag:tasn_dec.c:1199:
140134402181024:error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error:tasn_dec.c:374:Type=X509

Code: Select all

Oct 19 10:45:07 files.bencor.info httpd-scl-wrapper[35321]: AH00526: Syntax error on line 100 of /opt/rh/httpd24/root/etc/httpd/conf.d/ssl.conf:
Oct 19 10:45:07 files.bencor.info httpd-scl-wrapper[35321]: SSLCertificateFile: file '/etc/pki/tls/files_bencor_info.crt' does not exist or is empty
Oct 19 10:45:07 files.bencor.info systemd[1]: httpd24-httpd.service: main process exited, code=exited, status=1/FAILURE
Oct 19 10:45:07 files.bencor.info httpd-scl-wrapper[35323]: AH00526: Syntax error on line 100 of /opt/rh/httpd24/root/etc/httpd/conf.d/ssl.conf:
Oct 19 10:45:07 files.bencor.info httpd-scl-wrapper[35323]: SSLCertificateFile: file '/etc/pki/tls/files_bencor_info.crt' does not exist or is empty
Oct 19 10:45:07 files.bencor.info systemd[1]: httpd24-httpd.service: control process exited, code=exited status=1

Code: Select all

[root@files httpd]# cat /etc/pki/tls/certs/files_bencor_info.crt 
-----BEGIN CERTIFICATE-----
Blah Blah

-----END CERTIFICATE-----

❯ keybase pgp export -q 04460cd228df9e0d42f07643992eb6fafd4e6361 --secret
▶ ERROR No matching keys found

❯ pass path/to/auth
gpg: decryption failed: No secret key

sec   rsa4096 2019-03-06 [SC]
      04460CD228DF9E0D42F07643992EB6FAFD4E6361
uid           [ unknown] Sullivan Senechal <soullivaneuh@gmail.com>
uid           [ unknown] Sullivan Senechal <sullivan.senechal@gmail.com>
ssb   rsa2048 2019-03-06 [E] [expires: 2027-03-04]
ssb   rsa2048 2019-03-06 [SA] [expires: 2027-03-04]

Please keybase log send . CC @zapu

@maxtaco Here it is: 6b770312cc9ce6a2500b521c.

So I finally removed my second key and then did:

keybase pgp export | gpg --import
keybase pgp export --secret | gpg --import

It works and «solve» my problem.

If you don’t find any issue from my log, feel free to close this one. 👍

Sorry, no clue what went wrong here. The log does not reach that far back to show the failures you’ve experienced. I also tried this on a fresh account with different combinations of keys and could import/export successfully.

Got the same issue. my log id: 05cd7600b630fad82befcb1c

I have got the same issue on my ‘older’ first installation. Can’t find a trace of a ‘second key’.

Executing ‘keybase pgp export -s’ and comparing the ‘keybase.service.log’ files on both installation, I find a difference:

old computer/installation (▶ ERROR No matching keys found)

skb_keyring.go:123] 60fa + Loading SKB keyring: . . ./Keybase/secretkeys.pawawa.mpack
skb_keyring.go:181] 60fc | Indexed 2 secret keys

new computer/installation

skb_keyring.go:123] 8bdc + Loading SKB keyring: . . ./Keybase/secretkeys.pawawa.mpack
skb_keyring.go:181] 8bde | Indexed 3 secret keys

Hey @kanutope thank you for reaching out to us.

Was the key in question imported into Keybase using the keybase.io website or keybase pgp import --push-secret? Can you send the logs (using keybase log send) immediately after using the command on both «old computer» and «new computer» and pasting log IDs here? Thank you.

Hey @zapu thanks for your swift reply

• pgp key was (re)created on the ‘NEW’ installation.
• I have repeated the pgp export -s, on both NEW (successful) and OLD (failing) installation.
• log sent (NEW): 77d27f6eafaece1ae5c60f1c .
• log sent (OLD): da3e7e25bef99eca2a7f601c .

Cheers!

I am pretty sure this is the expected behavior. The pgp private key isn’t server synced.

So there are two keychains available for every Keybase user: one that is local, and one that stores keys on Keybase server, encrypted with user passphrase. If you only synced / imported to local keychain on machine ‘NEW’ (when generating it), it will not be automatically available on other machines.

Try keybase pgp push-private and keybase pgp pull-private

Hi @maxtaco
I did keybase pgp push-private on NEW and keybase pgp pull-private on OLD.
private/.keys/pgp created successfully after ‘push’.
With ‘pull’, ran into ‘▶ ERROR GPG error: exit status 2’.
Made keybase log send => a1a28b061ec8820fa4c58a1c .
I am investigating the server.log file — there might be something wrong with my GnuPG installation.

Looking into keybase.server.log file, I saw /usr/local/bin/gpg --no-tty --import was failing.
I went to …/private/.keys/pgp, and tried ‘manual’ import gpg --import < <key>.asc, and that one succeeded, after requesting for my passphrase.

If our small company were 10x the size we could accommodate every breaking change of every minor version of gpg on every platform under every package manager. But alas.

hi @maxtaco — I don’t know whether it has to do with the gpg version. I checked again, and the ‘manual’ import succeeded thanks to the GPG_TTY variable being set (independently of the --no-tty option.
Thanks for your support. Cheers!
Just a last observation: I’ve gotten my secret PGP key transferred to the OLD machine, though the keybase pgp export -s still returns the «No matching keys found» error.

• solved *

Revoking the OLD machine and scratching the entire Keybase user data did not resolve the issue.

Though, got it working after reading through keybase/keybase-issues#2793 and performing
gpg --export-secret-key 1A9342D586065111 | keybase pgp import --push-secret.
Message returned:
▶ INFO Key 01018488fbae49e539f76f2f198d252bac7223ca8cdd2b8bef51cd1d364962c039930a already exists. Only importing the private key.

Let me be the first to say, there is something absolutely wrong here.

Log ID: a6f0f31d67eccd8373ae641c

I tried importing my key several times and it works non-deterministically.

~  97  21:19:38  ✔  keybase pgp export -q 36DF664C07A67A08 --secret | gpg --allow-secret-key-import
gpg: WARNING: no command supplied.  Trying to guess what you mean ...
▶ ERROR No matching keys found
gpg: processing message failed: Unknown system error
~  98  21:21:39  ↵ 2|2  keybase pgp export -q 36DF664C07A67A08 --secret | gpg --allow-secret-key
gpg: WARNING: no command supplied.  Trying to guess what you mean ...
▶ ERROR No matching keys found
gpg: processing message failed: Unknown system error
~  99  21:21:46  ↵ 2|2  keybase pgp export -q 36DF664C07A67A08 --secret | gpg --allow-secret-key --import
gpg: key 36DF664C07A67A08: "Matt Ouille <matthew.ouille@gmail.com>" not changed
gpg: key 36DF664C07A67A08/36DF664C07A67A08: error sending to agent: Inappropriate ioctl for device
gpg: error building skey array: Inappropriate ioctl for device
gpg: Total number processed: 1
gpg:              unchanged: 1
gpg:       secret keys read: 1
~  100  21:22:16  ↵ 0|2  export GPG_TTY=$(tty)
~  101  21:22:39  ✔  vim ~/.zshenv
~  102  21:22:54  ✔  keybase pgp export -q 36DF664C07A67A08 --secret | gpg --allow-secret-key --import
▶ ERROR No matching keys found
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
~  103  21:23:00  ↵ 2|2  keybase pgp export -q 36DF664C07A67A08 --secret | gpg --allow-secret-key --import
▶ ERROR No matching keys found
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
~  103  21:23:03  ↵ 2|2  keybase pgp export -q 36DF664C07A67A08 --secret | gpg --allow-secret-key --import
▶ ERROR No matching keys found
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
~  103  21:23:04  ↵ 2|2  keybase pgp export -q 36DF664C07A67A08 --secret | gpg --allow-secret-key --import
~  103  21:23:12  ↵ 2|2  keybase pgp export -q 36DF664C07A67A08 --secret | gpg --allow-secret-key --import
▶ ERROR No matching keys found
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
~  103  21:23:14  ↵ 2|2  keybase pgp export -q 36DF664C07A67A08 --secret | gpg --allow-secret-key --import
▶ ERROR No matching keys found
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
~  103  21:23:16  ↵ 2|2  keybase pgp export -q 36DF664C07A67A08 --secret | gpg --allow-secret-key --import
▶ ERROR No matching keys found
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
~  103  21:23:17  ↵ 2|2  keybase pgp export -q 36DF664C07A67A08 --secret | gpg --allow-secret-key --import
▶ ERROR No matching keys found
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
~  103  21:23:18  ↵ 2|2  keybase pgp export -q 36DF664C07A67A08 --secret | gpg --allow-secret-key --import
gpg: key 36DF664C07A67A08: "Matt Ouille <matthew.ouille@gmail.com>" not changed
gpg: key 36DF664C07A67A08: secret key imported
gpg: Total number processed: 1
gpg:              unchanged: 1
gpg:       secret keys read: 1
gpg:   secret keys imported: 1
~  103  21:23:46  ✔  keybase log send

That seems similar to a bug in pgp decrypt that we have fixed previously. I’ll take a look, thank you.

could also be a local pinentry/gpg misconfigure

i hate to ask for this @mattouille, but will do so anyway. please have some sympathy for us, gpg is basically impossible to support, given it breaks with every minor version and that every combination of platform, package manager and dotfiles provides additional bugs and misconfigurations, and demands further workarounds.

(…also as @zapu says, there is a bug that we’ve recently fixed….)

@maxtaco I definitely have empathy for your situation and I apologize if I came off like I didn’t.

Some context
I use Keybase to manage my PGP key which signs all of my commits for work and another which signs my personal commits. Keybase has basically become an integral part of my development process both professionally and personally.

Yesterday my hard drive failed and I ended up having to rebuild my OS, which means going through the process of exporting my keys from Keybase. Normally this process is very smooth and predictable and I spent the better part of an hour messing with it before I figured out it was failing non-deterministically.

I’m not frustrated with Keybase, you all, or anything of the sort — just the scenario I was in. That’s the frustrated tone you’re reading.

I still love Keybase and I’m thankful every day for you all maintaining it.

I left off the most important part of all: I use Keybase PGP because I don’t like dealing with GPG.

Understood, thanks @mattouille for the clarification! Hopefully the next build solves the issue in general. But for now, is the workaround of trying n times good enough for you to recover your important data?

BTW, I currently use keybase pgp push-private to sync my PGP private keys via KBFS. This would be useful in the case of a disk crash.

Interesting. I guess I had always looked at my desktop GPG provided pgp keys as «temporary» (or as long as this OS install lasts) and I was treating my Keybase generated ones as empirical.

Also, yes, once it’s installed I don’t need to mess with it and it eventually succeeded.

Hi friends, currently experiencing this issue on a fresh install!

Log id: a47bffd64aae0fed89393e1c

Love keybase!

I’ve also experienced this on

$ keybase version
Client:  5.9.2-20220131221715+a25f15e42b
Service: 5.9.2-20220131221715+a25f15e42b

Log ID: 3e359fc39634b724430e6d1c

Workaround for my use case, i.e. moving private GPG keys from machine A to B.

1. On machine A, run keybase pgp push-private --all -f.
2. On machine B list all keys using keybase fs ls -l /keybase/private/$you/.keys/pgp.
3. For each key file, run keybase fs read /keybase/private/$you/.keys/pgp/$key | gpg --allow-secret-key-import --import.
4. Optionally remove private keys from Keybase.