Your browser does not allow storing cookies. We recommend enabling them.

SSH

Debugging Using USS shell

When debugging the server, a second server daemon can be started to a different TCP port or alternatively the existing server can be stopped and the same port can be used for debugging.

Debugging can be started with the following command (run as the SSHD2 user):

> /opt/tectia/sbin/sshd2 -d 4 -p 1234

In the command, -d defines the debug level and -p the TCP port. With this command the debug output is displayed to the screen.

Debug can also be forwarded to a file:

> /opt/tectia/sbin/sshd2 -d 4 -p 1234 
> /tmp/sshd2_debug.out 2>&1

Debugging for the SFTP server subsystem can be controlled with the SSH_SFTP_DEBUG and SSH_SFTP_DEBUG_FILE environment variables. SSH_SFTP_DEBUG defines the debug level for the file transfer server. SSH_SFTP_DEBUG_FILE defines the output file for the debug messages. See Debugging File Transfer below.


 

 
Highlights from the SSH.COM blog:

  • Cryptomining with the SSH protocol: what big enterprises need to know about it

    Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency.
    Read more
  • SLAM the door shut on traditional privileged access management

    Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity?
    Read more
  • We broke the IT security perimeter

    Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so.
    Read more