Invalid Hash of binaries files.
Hello,
First, many thanks for your job, it's a great tool to use !
On Nexcloud Hub 8, the installation goes wrong. The different binaries, are well downloading, but impossible de pass de check verification.
I installed Libresign from the Nextcloud's store. If used the occ command to download every binaries without any error. But the check status, is still to error.
If someone can help me to get the installation working !
Thank you, very much in advance :)
Best Regards
Thanks by your report, I will check what's happening. This is a new feature.
I identified the problem. This version need to have json files signing the dependencies but looking at tar.gz file, haven't the necessary files.
| Current scenario | Need to have these files |
|---|---|
I will check how to solve. The problem is when LibreSign is packed to publish at Nextcloud app store.
@GauthierCrp could you test the newest release?
Hello Vitor,
The bug seems to be resolved ! Many Thanks !
Have a good day. Best Reagrd
@vitormattos Fixed the invalid hashes on my instance as well.
That said, I can't seem to find how to add a signature to a pdf. The option "Open in LibreSign" opens the file info menu onto the LibreSign tab, but it is empty with no actions available.
@AceDicer This isn't about this issue. Could you open a specific issue to this?
@vitormattos hey, i have a trouble with this error, even after upgrading to 9.1.2.
If i remove these lines:
// if (count($this->verify('java'))) {
// return [
// (new ConfigureCheckHelper())
// ->setErrorMessage(
// 'Invalid hash of binaries files.'
// )
// ->setResource('java')
// ->setTip('Run occ libresign:install --all'),
// ];
// }
The things goes in right way!
I guess the java file check doesn't works.
Hi @rodsmar I think that I identified another problem at build and fixed here:
- https://github.com/LibreSign/libresign/pull/3250
I already merged this but I'm working now to generate a new build.
Could you check again at the newest release of LibreSign?
Closing this issue as solved.
If this issue persists, don't hesitate to open a new issue making reference to this.
[!NOTE]
If you like this app, don't hesitate to help us
Ways to help this project:
- Creating a very nice review of this project at:
- social networks like LinkedIn, Instagram, etc and putting the @LibreSign and @LibreCodeCoop
- AlternativeTo https://alternativeto.net/software/libresign/
- Nextcloud apps store: https://apps.nextcloud.com/apps/libresign
- Sponsoring the development by GitHub sponsor https://github.com/sponsors/LibreSign
- helping the translations on Transifex
- contacting us to have Enterprise support: https://libresign.coop
I am using the latest version 9.1.3 and still having issue with Invalid hash of binaries files.
@jameswlane I'm starting to create a new release with points that will touch at this.
Is your environment with debug mode on?
@vitormattos It is a production instance. I have yet to enable any additional logging except what is enabled by default.
I created a new release now, could you check with the newest release?
@vitormattos It seems to be stuck in a loop of download and validate
@vitormattos, would you happen to know what I can try to fix the loop?
Are you using Alpine Linux?
I created a new release with some fixes at setup flow, could you check with the newest release?
@vitormattos I am using Ubuntu 22.04 LTS. I will update it and see what I get.
@vitormattos Same thing. I ssh in and grabbed the logs its throwing the following error:
file_get_contents(): Read of 12288 bytes failed with errno=21 Is a directory at /var/www/html/lib/private/IntegrityCheck/Helpers/FileAccessHelper.php#44
After upgrading to 9.2.2 i can confirm: Java's hash validation works flawless!
But...
To check requirements i had to enable Nextcloud's debug mode:
config:system:set debug --value true --type boolean
@rodsmar the signature process is to ensure that the downloaded files are certified to works with LibreSign and wasn't changed.
At development mode is necessary to enable the debug mode because a developer can't sign the downloaded, only the LibreSign author that have the certificate can sign the downloaded files. At development mode is used a self generated certificate to sign and validate the downloaded files.
The signatures of downloaded files are stored at folder appinfo inside LibreSign folder. Are a lot of *.json files. These fiels are generated during the build process of LibreSign to validate the signatuer by the same way of Nextcloud validate the apps that are signed by developer certificate.
I think that have anything different at your environment. Could you check at Administratin Settings if all checks of Nextcloud are ok? Isn't the check of LibreSign, is about the checks of Nextcloud. I think that when you defined debug=true and validated your LibreSign setup, changed the json files inside appinfo folder.
Closing this as solved after newest release.
Please, test again to check if all is working fine.
this seems to be back on nextcloud 30.0.6
@Fuseteam check if your java version is up to date.
I will think to implement a way to update the dependencies or notify the admin about an outdated dependency.
@Fuseteam check if your java version is up to date.
I just ran occ libresign:install --all last week so i believe it should be up to date
I have nextcloud hub 10 (31.0.0) and same error as this. Is there a solution to this problem?
@Fuseteam check if your java version is up to date.
I just ran
occ libresign:install --alllast week so i believe it should be up to date
nextcloud running in Truenascale apps
Ran php occ libresign:install -all but jsignpdf still not valid hash. Any asistance for fix !!
there is now an fix for this issue: https://github.com/LibreSign/libresign/issues/4810#issuecomment-2989422713
It turns out that the downloaded binaries in /var/html/data/appdata_*/libresign/x86_64/jsignpdf are corrupted, removing those binaries manually and then re-running libresign:install --all fixes the error