Empty client certificate chain

[JokerGermany]

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior: When the client connects to me, I get this error: The Client only gets "Connection aborted"

Expected behavior Connection Established

Screenshots

Desktop (please complete the following information):

• OS: Ubuntu Mate 22.04
• Version 13.0.0 (Happened with the version before, too. Updated Dayon then one both sides)

Aditional Context Deleted the .dayon folder on the client to make sure thats not the problem.

[RetGal]

Hi, which Java version do you use? Please click on the info Icon (i), it should display something like this:

[RetGal]

Hi, I couln't reproduce the described behaviour using Ubuntu Mate 22.04 running from an USB stick with Dayon! installed from ppa:regal/dayon. It worked for both sides (assistant and assisted), connection to/from another notebook running the latest Debian could be established without any issues:

[JokerGermany]

Will ask the client to provide the informations. (probably stock fully updated Ubuntu Mate 22.04.3 - I use this script for installing: https://github.com/Linux-Installation/Ubuntu-Installations-Script )

Thats what the Server is running:

         dayon.application.name [dayon_assistant]
                     dayon.home [/home/jokergermany/.dayon]
                      dayon.log [file]
                  file.encoding [UTF-8]
                 file.separator [/]
                java.class.path [/usr/bin/dayon/dayon.jar]
             java.class.version [62.0]
                      java.home [/usr/lib/jvm/java-18-openjdk-amd64]
                 java.io.tmpdir [/tmp]
              java.library.path [/usr/java/packages/lib:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib]
              java.runtime.name [OpenJDK Runtime Environment]
           java.runtime.version [18-ea+36-Ubuntu-1]
        java.specification.name [Java Platform API Specification]
      java.specification.vendor [Oracle Corporation]
     java.specification.version [18]
                    java.vendor [Private Build]
                java.vendor.url [Unknown]
            java.vendor.url.bug [Unknown]
                   java.version [18-ea]
              java.version.date [2022-03-22]
     java.vm.compressedOopsMode [32-bit]
                   java.vm.info [mixed mode, sharing]
                   java.vm.name [OpenJDK 64-Bit Server VM]
     java.vm.specification.name [Java Virtual Machine Specification]
   java.vm.specification.vendor [Oracle Corporation]
  java.vm.specification.version [18]
                 java.vm.vendor [Private Build]
                java.vm.version [18-ea+36-Ubuntu-1]
                      jdk.debug [release]
                 line.separator [\10]
                native.encoding [UTF-8]
                        os.arch [amd64]
                        os.name [Linux]
                     os.version [5.15.0-48-generic]
                 path.separator [:]
            sun.arch.data.model [64]
sun.awt.enableExtraMouseButtons [true]
          sun.boot.library.path [/usr/lib/jvm/java-18-openjdk-amd64/lib]
                 sun.cpu.endian [little]
        sun.io.unicode.encoding [UnicodeLittle]
               sun.java.command [/usr/bin/dayon/dayon.jar assistant]
              sun.java.launcher [SUN_STANDARD]
             sun.java2d.uiScale [1]
               sun.jnu.encoding [UTF-8]
        sun.management.compiler [HotSpot 64-Bit Tiered Compilers]
                   user.country [DE]
                       user.dir [/home/jokergermany]
                      user.home [/home/jokergermany]
                  user.language [de]
                      user.name [jokergermany]
                  user.timezone [Europe/Berlin]

[RetGal]

Hi, I suspect that it is the "odd" Java version that is causing the problems:

java.vm.vendor [Private Build]
ava.vm.version [18-ea+36-Ubuntu-1]

Java 18 was a "short term version" who was only supported during 6 months (March to September 2022). Vendor "Private Build" also looks a bit suspicious to me. I have successfully tested the connectivity of release 13.0.0 with OpenJDK 8, 11, 17, 21 and 18 and could not reproduce this bug.

Side note: In reviewing your install script, I was wondering if you are aware of the (automatic) connection function with an assisted.yaml. Described here, at the bottom.

[JokerGermany]

Yeah would make sense, that the server is the problem, the most things are changed there^^ Will test with a LMDE today/tommorow. At the moment I don't have contact to the original client.

@assisted.yaml Looks nice, will test it. €dit: Yes the automatic connection function will help... ("press the play button?" "What is a play button?" "press the triangle" "the left or the right one?" [the right one is the exit button...])

[RetGal]

Addendum This error (also) occurs, if you try to connect an Assisted with v13.0.0 to an Assistant with an older version. (The other way round works if you enable the compatibility mode on the Assistant.)

Solution: Update the Assistant to the newest version.