Dependencies :: system java is not recognized

[adriansev]

Hi! I have an Alma9 with openjdk 21.0.7.06

[root@isscloud ~]# rpm -qa | grep openjdk
java-21-openjdk-headless-21.0.7.0.6-1.el9.alma.1.x86_64
java-21-openjdk-21.0.7.0.6-1.el9.alma.1.x86_64
java-21-openjdk-devel-21.0.7.0.6-1.el9.alma.1.x86_64
java-21-openjdk-jmods-21.0.7.0.6-1.el9.alma.1.x86_64
java-17-openjdk-headless-17.0.15.0.6-2.el9.alma.1.x86_64

without doing occ libresign:install --java java dependency is not considered fulfilled the same seem to be with pdftk

[root@isscloud ~]# rpm -qa | grep pdftk
pdftk-java-3.3.3-1.el9.noarch

It would be nice to be able to use system level dependencies, and if it's a problem of version the message should say so... Thanks a lot!

[adriansev]

additionally, installing all packages and having:

[root@isscloud bin]# run_occ libresign:configure:check
 --------- ------------------- ---------------------------------------------------------------------------------------------------- ----- 
  Status    Resource            Message                                                                                              Tip  
 --------- ------------------- ---------------------------------------------------------------------------------------------------- ----- 
  success   java                Java version: openjdk version "21.0.6" 2025-01-21 LTS                                                     
  success   java                Java binary: /storage/appdata_ocbgc2w9cx8l/libresign/x86_64/linux/java/jdk-21.0.6+7-jre/bin/java          
  success   pdftk               PDFtk version: 3.3.3                                                                                      
  success   pdftk               PDFtk path: /storage/appdata_ocbgc2w9cx8l/libresign/x86_64/pdftk/pdftk.jar                                
  success   jsignpdf            JSignPdf version: 2.3.0                                                                                   
  success   jsignpdf            JSignPdf path: /storage/appdata_ocbgc2w9cx8l/libresign/x86_64/jsignpdf/jsignpdf-2.3.0/JSignPdf.jar        
  success   pdfsig              pdfsig version: 21.01.0                                                                                   
  success   pdfinfo             pdfinfo version: 21.01.0                                                                                  
  success   openssl-configure   Root certificate setup is working fine.                                                                   
 --------- ------------------- ---------------------------------------------------------------------------------------------------- ----- 

the configuration check from https://MYFQDN/settings/admin/libresign show:

[vitormattos]

Hi @adriansev could you check if is your problem related with the follow issue?

• https://github.com/LibreSign/libresign/issues/3227

Look at this issue that have reference to another issue. Follow the links. It's very important to identify if your scenario is the same.

[adriansev]

Hi! While indeed i had a avc looking like this:

----
time->Fri Apr 11 11:36:39 2025
type=PROCTITLE msg=audit(1744360599.961:183450): proctitle="/var/www/nextcloud/apps/mail/vendor/nextcloud/kitinerary-bin/src/../bin/kitinerary-extractor"
type=SYSCALL msg=audit(1744360599.961:183450): arch=c000003e syscall=9 success=no exit=-13 a0=0 a1=10000 a2=7 a3=2 items=0 ppid=1825340 pid=1883374 auid=4294967295 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=4294967295 comm="kitinerary-extr" exe="/var/www/nextcloud/apps/mail/vendor/nextcloud/kitinerary-bin/bin/kitinerary-extractor" subj=system_u:system_r:httpd_sys_script_t:s0 key=(null)
type=AVC msg=audit(1744360599.961:183450): avc:  denied  { execmem } for  pid=1883374 comm="kitinerary-extr" scontext=system_u:system_r:httpd_sys_script_t:s0 tcontext=system_u:system_r:httpd_sys_script_t:s0 tclass=process permissive=0

i'm not sure is related to libresign and still the problem was not fixed after applying the allow recipe

[vitormattos]

From what I can see, it doesn't seem that your log is directly related to LibreSign or to the reported issue, as the path points to the Mail app.

I currently don’t have access to an Alma9 environment. It’s possible that SELinux is involved, as we’ve encountered a similar case before. At that time, we were able to identify and fix the issue thanks to the help of a user who became a recurring sponsor of LibreSign, which allowed us to dedicate time to investigate that very specific scenario. However, since the environment wasn’t under our control, we couldn’t perform a more thorough verification or implement automated checks and tips to help other sysadmins.

If LibreSign has been helpful to you and you’d like to support the project, becoming a recurring sponsor would make a big difference. With your help, we could take a closer look at your specific environment, perhaps even through a quick video call, and work on improvements that would benefit not only you but also many others using Alma9.

Thanks again for contributing and helping LibreSign grow! 💚

[vitormattos]

Considering that the reported logs are of kitinerary-extractor and nof of LibreSign, I'm closing this issue as unrelated to LibreSign.