Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nextcloud AIO 29.0.3 and LibreSign 9.1.3 can't get past 'Invalid hash of binaries files.' error #3324

Closed
t3cneo opened this issue Jul 10, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@t3cneo
Copy link

t3cneo commented Jul 10, 2024

Describe the bug
NC AIO 29.0.3 here with LibreSign 9.1.3, can't get past the 'Invalid hash of binaries files.' error

To Reproduce
Steps to reproduce the behavior:
Install LibreSign 9.1.3 from webUI, click 'Download Binaries' and get the error.
Install from cli (from inside the container) lead to the same error.

Expected behavior
Binaries installed and LibreSign ready to work..

Screenshots
Copie d'écran_20240710_211823

Environment information (please complete the following information):

  • OS: Docker AIO
  • Browser Firefox
  • LibreSign Version 9.1.3
  • Nextcloud Server Version 29.0.3
  • Logs

Copie d'écran_20240710_212226

Additional context
I read all topics related to AIO, especially #1409 and #3026, here are a few things you might ask :

NEXTCLOUD_ADDITIONAL_APKS is set to imagemagick ghostscript and the output of gs --version is 10.03.1

Java seams to install as expected :

8b0f582248ca:/var/www/html$ /mnt/ncdata/appdata_ID/libresign/x86_64/java/jdk-21.0.2+13-jre/bin/java --version
openjdk 21.0.2 2024-01-16 LTS
OpenJDK Runtime Environment Temurin-21.0.2+13 (build 21.0.2+13-LTS)
OpenJDK 64-Bit Server VM Temurin-21.0.2+13 (build 21.0.2+13-LTS, mixed mode, sharing)

EDIT:

Don't think it could be related but alpine has been bumped since #3026

8b0f582248ca:/var/www/html$ php -r "var_dump(shell_exec('cat /etc/*-release'));"
string(195) "3.20.1
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.20.1
PRETTY_NAME="Alpine Linux v3.20"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://gitlab.alpinelinux.org/alpine/aports/-/issues"
"
@t3cneo t3cneo added the bug Something isn't working label Jul 10, 2024
@github-project-automation github-project-automation bot moved this to 0. Needs triage in Roadmap Jul 10, 2024
@t3cneo
Copy link
Author

t3cneo commented Jul 10, 2024

It's getting better but weird :

I had the idea to try earlier version of LibreSign.

Could not get any of 9.1.x version working but 9.0.2 installed and got me passed the webUI LibreSign Wizard.
I could not get the webapp to work though (visiting https://cloud.mydomain.tld/apps/libresign/* would break Nextcloud's menu) so I updated it via webUI and it is now working.

I can still see the 'Invalid hash of binaries files.' error when visiting https://cloud.mydomain.tld/settings/admin/libresign (exactly the same as in the first screenshot) but the webapp at https://cloud.mydomain.tld/apps/libresign/* is working now. (only tested signing requests via email)

@vitormattos
Copy link
Member

These dependencies are no longer necessary in LibreSign, they have been replaced by pdftk.

NEXTCLOUD_ADDITIONAL_APKS is set to imagemagick ghostscript and the output of gs --version is 10.03.1

@vitormattos
Copy link
Member

vitormattos commented Jul 11, 2024

Could you provide more information about the files that stay at log? Sounds that PHP haven't access to these files.

Other possible points to check is about this issue:

Another point to check is a ls -l at folder appinfo of LibreSign. The build process put the signature files of binaries inside this folder.

Screenshot_20240711_022259

@vitormattos
Copy link
Member

@t3cneo I identified a problem at build process and created a new release with fixes.

Could ou test again with the newest release?

@t3cneo
Copy link
Author

t3cneo commented Jul 15, 2024

All good now with 9.2.2, thanks a lot @vitormattos

@t3cneo t3cneo closed this as completed Jul 15, 2024
@github-project-automation github-project-automation bot moved this from 0. Needs triage to 4. to release in Roadmap Jul 15, 2024
@vitormattos
Copy link
Member

@t3cneo we need help to funding this project.
If you like this project and want to help, you could make a recurrent sponsor
The funding is very important to keep alive this project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: 4. to release
Development

No branches or pull requests

2 participants