schlomo

Forum Replies Created

Viewing 1 post (of 1 total)
  • Author
    Posts
  • in reply to: Using native SSH client with ProxyCommand #38955
    schlomo
    Participant

    Thanks! That actually works. Can you please link to the documentation where this is explained? I couldn’t find that via a Google search.

    Follow up question: How can I change the path that is used by the NX Client? Currently the PATH is only the bare system directories:

    $ ps eww -o command 1675 | tr ' ' '\n'
    COMMAND
    /Applications/NoMachine.app/Contents/MacOS/nxplayer
    COMMAND_MODE=unix2003
    PATH=/usr/bin:/bin:/usr/sbin:/sbin
    TMPDIR=/var/folders/0g/3s3mgqqn6k78g_qx_sryqr8c0000gn/T/
    __CFBundleIdentifier=com.nomachine.nxdock
    LOGNAME=xxx
    HOME=/Users/xxx
    XPC_FLAGS=0x0
    USER=xxx
    DISPLAY=/private/tmp/com.apple.launchd.fjVgzdDVok/org.xquartz:0
    SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.86zqQQ0wCW/Listeners
    XPC_SERVICE_NAME=application.com.nomachine.nxdock.32575488.37668810
    SHELL=/bin/zsh
    __CF_USER_TEXT_ENCODING=0x1F5:0x0:0x0

    And my ProxyCommand binary is of course in /opt/homebrew/bin/cloudflared.

    The problem is that the SSH process spawned by the NX client can’t find that binary as the PATH is missing the Homebrew or even the /usr/local/bin directory.

    Of course I could solve that with a custom SSH wrapper, I was wondering if I could solve that via NX Client configuration.

    Another question: How should I configure the NX Client profile to not ask for username or password? Essentially to not ask for anything and just use the system SSH binary to deal with the connection? And also to not try to configure authentication methods?

Viewing 1 post (of 1 total)