The public key cannot be used to verify a signature after upgrade to 2.4.0

Checklist
[x ] I have read intro post: About the Installation Issues category
[x ] I have read the tutorials, help and searched for similar issues
[ x] I provide relevant information about my server (component names and versions, etc.)
[x ] I provide a copy of my logs and healthcheck
[ x] I describe the steps I have taken to trouble shoot the problem
[x ] I describe the steps on how to reproduce the issue

So im getting The public key cannot be used to verify a signature. in my healtcheck everything else is fine i got this error after upgrading to 2.4.0.

Everything is working fine i can login,view passwords etc.

Here is my healthcheck

[PASS] PHP version 7.0.32-0ubuntu0.16.04.1.
[PASS] PCRE compiled with unicode support.
[PASS] The temporary directory and its content are writable.
[PASS] The public image directory and its content are writable.
[PASS] The logs directory and its content are writable.
[PASS] GD or Imagick extension is installed.
[PASS] Intl extension is installed.
[PASS] Mbstring extension is installed.

Config files

[PASS] The application config file is present
[PASS] The passbolt config file is present

Core config

[PASS] Debug mode is off.
[PASS] Cache is working.
[PASS] Unique value set for security.salt
[PASS] Full base url is set to https://vault.hostingforyou.nl
[PASS] App.fullBaseUrl validation OK.
[PASS] /healthcheck/status is reachable.
SSL Certificate

[PASS] SSL peer certificate validates
[PASS] Hostname is matching in SSL certificate.
[PASS] Not using a self-signed certificate

Database

[PASS] The application is able to connect to the database
[PASS] 30 tables found
[PASS] Some default content is present
[PASS] The database schema up to date.

GPG Configuration

[PASS] PHP GPG Module is installed and loaded.
[PASS] The environment variable GNUPGHOME is set to /home/www-data/.gnupg.
[PASS] The directory /home/www-data/.gnupg containing the keyring is writable by the webserver user.
[PASS] The server gpg key is not the default one
[PASS] The public key file is defined in config/passbolt.php and readable.
[PASS] The private key file is defined in config/passbolt.php and readable.
[PASS] The server key fingerprint matches the one defined in config/passbolt.php
[PASS] The server public key defined in the config/passbolt.php is in the keyring.
[PASS] There is a valid email id defined for the server key.
[PASS] The public key can be used to encrypt a message.
[PASS] The private key can be used to sign a message.
[PASS] The public and private keys can be used to encrypt and sign a message.
[PASS] The private key can be used to decrypt a message.
[PASS] The private key can be used to decrypt and verify a message.
[FAIL] The public key cannot be used to verify a signature.

Application configuration

[PASS] Using latest passbolt version (2.4.0).
[PASS] Passbolt is configured to force SSL use.
[PASS] App.fullBaseUrl is set to HTTPS.
[PASS] Selenium API endpoints are disabled.
[PASS] Search engine robots are told not to index content.
[PASS] Registration is closed, only administrators can add users.
[PASS] Serving the compiled version of the javascript app
[PASS] All email notifications will be sent.

1 error(s) found. Hang in there!

h4yadm@h4y-vault:/var/www/passbolt_api/config$

Hi @lanaiscool,

I have doubt the issue is the result of the update, since this functionality was not affected by the update.
Maybe it is the result of an underlying system update such as php-gnupg.

How did you install php-gnupg? Did you use the ubuntu package or pear or something else?

I’ll try to schedule some time in the coming weeks to dig into building more feedback for when this check fails. At the moment it should not be a blocker, since we don’t check for detached signature, it’s more a flag to tell us something is weird is going on.

i did an apt-get upgrade before i started the passbolt upgrade so it probably updated php as well

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.