Your browser does not allow storing cookies. We recommend enabling them.
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
> /opt/tectia/etc/init.d/sshd2 start foreground -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/etc/init.d/sshd2 start foreground -d 4 -p 1234 >/tmp/sshd2_debug.out 2>&1
Debugging for the SFTP server subsystem can be controlled with the
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.
[ Contents] [ Index] [ Contact Information | Support | Feedback | SSH Home Page | SSH Products ]
Copyright © 2011 SSH Communications Security Corp.
This software is protected by international copyright laws. All rights reserved. Copyright Notice Reduce Secure Shell risk. Get to know the NIST 7966. The NISTIR 7966 guideline from the Computer Security Division of NIST is a direct call to action for organizations regardless of industry and is a mandate for the US Federal government. Download now ISACA Practitioner Guide for SSH With contributions from practitioners, specialists and SSH.COM experts, the ISACA “SSH: Practitioner Considerations” guide is vital best practice from the compliance and audit community. Download now What we recommend to read next: Regulatory compliance for cybersecurity? Privileged access management related information NEAREST SSH.COM OFFICE SSH Communications Security, Inc. 460 Totten Pond Road #460 Waltham, MA 02140 USA 781-247-2100 Contact us