• Registered: 2024-02-28
  • Posts: 2

Topic: ssh tunnel using wolfSSL?

Hello,

I am running some tests on Yocto Linux (dunfell) on a Renesas S4 board.

I need to setup a SSH tunnel between the S4 and a PC running Ubuntu (22.4.). This works fine with OpenSSH, but the data through put is slow as expected with OpenSSH.

I tried building and running wolfSSL for dunfell and I had to backport OpenSSH (8.5p1) from hardknott, because that is the version compatible with the current version of of wolfSSL (5.6.6) available on Github. But, unfortunately backporting of OpenSSL did not work easily. The wolfSSL test and performance measurement were successful.

Is there a version of wolfSSL compatible with dunfell or OpenSSH version 8.2p1? What would be the correct git hash or label?

Thank you and best regards,

Michael

Share

  • Registered: 2021-08-12
  • Posts: 111

Re: ssh tunnel using wolfSSL?

Hi,
Have you tried using wolfSSH? It can be found at  https://github.com/wolfSSL/wolfssh or from our download page.
Warm regards, Anthony

Share

3 Reply by michael.dege (edited by michael.dege 2024-03-01 05:28:33)

  • Registered: 2024-02-28
  • Posts: 2

Re: ssh tunnel using wolfSSL?

Hi Anthony,

I added the Yocto recipe following the steps in https://github.com/wolfSSL/meta-wolfssl … README.md.

I had to replace the OpenSSL and OpenSSH recipes with newer ones from Yocto hardknott because the version in dunfell was too old and not compatible with meta-wolfssl/recipes-connectivity/openssh/openssh_8.5p1.bbappend and the patch (meta-wolfssl/recipes-connectivity/openssh/files/openssh-8.5p1.patch)

Compilation is successful and OpenSSH/OpenSSL is working und fortunately there is still an when I add WolfSSL to the compilation. Maybe you have an idea what I am still missing when I get this error message:

[   28.138060] audit: type=1701 audit(1600598664.428:2): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=351 comm="ssh-keygen" exe="/usr/bin/ssh-keygen" sig=6 res=1

root@spider:~# ssh -p22 -L7001:localhost:7001 mike@192.168.1.7
The authenticity of host '192.168.1.7 (192.168.1.7)' can't be established.
ED25519 key fingerprint is SHA256:wSiJCquCKl6ckqvNHMq7CwDkGew9rnASzbEhTZj2A3U.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '192.168.1.7' (ED25519) to the list of known hosts.
mike@192.168.1.7's password:
munmap_chunk(): invalid pointer
                               [  227.378675] audit: type=1701 audit(1600598863.669:3): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=393 comm="ssh" exe="/usr/bin/ssh.openssh" sig=6 res=1
Aborted


I realize, that it is probably not WolfSSL code, but it does relate to the openssh-8.5p1.patch provided by WolfSSL.

Best regards,

Michael

Share

  • Registered: 2021-08-12
  • Posts: 111

Re: ssh tunnel using wolfSSL?

Hi, Thanks for reaching otu Michael.  This appears to be a memory issue.  Can you please try repeating these procedures with Valgrind and then showing us the output?
Warm regards, Anthony

Share