# SFTPServer Component The SFTPServer component is used to create a Secure File Transfer Protocol (SFTP) server. ## Syntax ```text nsoftware.IPWorksSFTP.SFTPServer ``` ## Remarks The SFTPServer component provides a simple way to create a Secure File Transfer Protocol (SFTP) server. Any SFTP client will be able to connect and transfer files to and from the server. ### Getting Started To begin, first provide a valid certificate with a private key in the [SSHCert](#sshcert-property-sftpserver-component) property. Optionally set the [RootDirectory](#rootdirectory-property-sftpserver-component) property to a valid local path. If this property is set, the component will serve files from this location, and when clients connect, they will see this as their initial directory. If this property is not set, then the component will fire events allowing customized responses for each operation. To start the server, set [Listening](#listening-property-sftpserver-component) to True. ### Client Authentication Client authentication is handled through the [SSHUserAuthRequest](#sshuserauthrequest-event-sftpserver-component) event. Inside this event, the *Accept* parameter determines whether authentication is accepted; this parameter should be set to *True* if a successful authentication is detected and *False* otherwise. When a client connects, the *AuthMethod* parameter indicates the method of authentication the client wishes to use. Connecting clients will initially attempt authentication with an *AuthMethod* of "none". This is done with the expectation that the request will fail and the server will provide a list of support authentication methods. The client then selects an available method and reauthenticates. If *AuthMethod* is "none", *Accept* should be set to *False*. For **password** authentication, the *User* parameter will hold the client's username and the *AuthParam* parameter will hold the password provided by the client. An external list of known usernames and passwords should be maintained to check these values against. For **publickey** authentication, the *User* parameter will hold the client's username and the *AuthParam* parameter will hold the key provided by the client. This key should be compared to an external list of known keys and usernames. For **keyboard-interactive** authentication, the [SSHUserAuthRequest](#sshuserauthrequest-event-sftpserver-component) event will fire multiple times; once for each prompt and response sent by the client. The index of the response is specified as a suffix in the *AuthMethod* parameter (e.g., keyboard-interactive-1, keyboard-interactive-2), and *AuthParam* will contain the client's response to the prompt. Finally, [SSHUserAuthRequest](#sshuserauthrequest-event-sftpserver-component) will fire one last time with *AuthMethod* set to "keyboard-interactive" and *AuthParam* set to an empty string. The *Accept* parameter must be set to *True* each time the event fires for the authentication process to succeed. ### Directory Listing When a client requests a directory listing, the [DirList](#dirlist-event-sftpserver-component) event fires with the *Path* parameter set to the directory to enumerate. If the directory listing is allowed, the appropriate set of files should be passed to the [SetFileList](#setfilelist-method-sftpserver-component) method. The *StatusCode* parameter should be set according to the status of the operation, and the valid status codes can be found in the documentation for the [DirList](#dirlist-event-sftpserver-component) event. ### Handling Events Event handlers are the primary method of customizing the component's functionality. When a client attempts to connect, open a file, authenticate to the server, and so on, the corresponding SFTPServer event will fire to allow for custom handling of the client's request. The following events are fired **both before and after** the requested operation is executed: - [DirCreate](#dircreate-event-sftpserver-component) - [DirList](#dirlist-event-sftpserver-component) - [DirRemove](#dirremove-event-sftpserver-component) - [FileOpen](#fileopen-event-sftpserver-component) - [FileRemove](#fileremove-event-sftpserver-component) - [FileRename](#filerename-event-sftpserver-component) - [FileWrite](#filewrite-event-sftpserver-component) - [SetAttributes](#setattributes-event-sftpserver-component) Each of these events has a *BeforeExec* event parameter that is *True* when the event is fired before execution of the operation, and *False* after execution of the operation. Handling the event before execution provides an opportunity to use custom logic to determine whether the operation should be denied, diverted, or otherwise modified. Handling the event after execution provides an opportunity to report success or any errors related to the operation to the client. The following events are fired only **after** the requested operation is executed: - [FileClose](#fileclose-event-sftpserver-component) - [FileRead](#fileread-event-sftpserver-component) - [GetAttributes](#getattributes-event-sftpserver-component) - [ResolvePath](#resolvepath-event-sftpserver-component) Any logic to deny opening a file for read or write should be done in the [FileOpen](#fileopen-event-sftpserver-component) event handler. **Threading in Server Applications** In .NET, all socket-based components perform all Socket.IO through asynchronous methods. Each call consumes a thread from the system's thread pool, and thus the number of concurrent calls is limited to the number of worker threads returned by ***System.Threading.ThreadPool.GetMaxThreads***. When using several components that can each create a socket connection or a single component that can create multiple socket connections, the application may enter a state in which all of the pool threads are in use for receiving. In a scenario such as this, the remote hosts may be waiting for data from the application before sending, but the application cannot send that data because all the threads are tied up waiting for inbound data. This is particularly important for server applications that use a daemon component. For example, say a server application 'S' has a max thread pool size of three, and clients 'A' and 'B' connect to it and each client uploads a large file. After all uploads are complete, 'S' enqueues an asynchronous read request in the thread pool for each client. Because no work is being done, the thread pool immediately consumes two threads that wait for any further data from 'A' and 'B'. While 'S' is still processing the first two files it has received, client 'C' connects and uploads a relatively small file. Similarly, once that upload has completed 'S' enqueues a third read request, and the thread pool immediately consumes the third and final thread to wait for further data from 'C'. Once 'S' completes processing any of the files, it will enqueue a send request. However, because all three threads are in use and waiting for data from the clients, the send operation cannot be completed. The entire system becomes deadlocked because each of the clients is waiting for data from the server, which cannot send that data because all of its pool threads are in turn waiting for data from the clients. To avoid a deadlock situation such as this, it is necessary to ensure that the maximum number of socket connections an application can make is always at least one less than the number of available worker threads. One method to achieve this is to call ***System.Threading.ThreadPool.SetMaxThreads*** during the application's startup to set the maximum number of threads to a value high enough to support the application for the duration of its execution. Another option is to trap an event such as [ConnectionRequest](#connectionrequest-event-sftpserver-component) and [Disconnected](#disconnected-event-sftpserver-component) from each component instance with logic to manage the maximum thread pool size according to the application's current needs. NOTE: Server components are designed to process events as they occur. To ensure that events are processed in a timely manner, [DoEvents](#doevents-method-sftpserver-component) should be called in a loop after the server is started. ## Property List *The following is the full list of the properties of the component with short descriptions. Click on the links for further details.* | | | | --- | --- | | [ConnectionBacklog](#connectionbacklog-property-sftpserver-component) | This property includes the maximum number of pending connections maintained by the Transmission Control Protocol (TCP)/IP subsystem. | | [Connections](#connections-property-sftpserver-component) | The collection of currently connected secure file transfer protocol (SFTP) clients. | | [DefaultAuthMethods](#defaultauthmethods-property-sftpserver-component) | The supported authentication methods. | | [DefaultTimeout](#defaulttimeout-property-sftpserver-component) | The initial timeout value to be used by incoming connections. | | [KeyboardInteractiveMessage](#keyboardinteractivemessage-property-sftpserver-component) | The instructions to send to the client during keyboard-interactive authentication. | | [KeyboardInteractivePrompts](#keyboardinteractiveprompts-property-sftpserver-component) | A collection of prompts to present to the user during keyboard-interactive authentication. | | [Listening](#listening-property-sftpserver-component) | This property indicates whether the component is listening for incoming connections on LocalPort. | | [LocalHost](#localhost-property-sftpserver-component) | The name of the local host or user-assigned IP interface through which connections are initiated or accepted. | | [LocalPort](#localport-property-sftpserver-component) | The Transmission Control Protocol (TCP) port in the local host where the component listens. | | [RootDirectory](#rootdirectory-property-sftpserver-component) | The root directory for the entire secure file transfer protocol (SFTP) server. | | [SSHCert](#sshcert-property-sftpserver-component) | The certificate(s) to be used during Secure Shell (SSH) negotiation. | | [SSHCompressionAlgorithms](#sshcompressionalgorithms-property-sftpserver-component) | The comma-separated list containing all allowable compression algorithms. | | [SSHEncryptionAlgorithms](#sshencryptionalgorithms-property-sftpserver-component) | The comma-separated list containing all allowable encryption algorithms. | ## Method List *The following is the full list of the methods of the component with short descriptions. Click on the links for further details.* | | | | --- | --- | | [Config](#config-method-sftpserver-component) | Sets or retrieves a configuration setting. | | [Disconnect](#disconnect-method-sftpserver-component) | This method disconnects the specified client. | | [DoEvents](#doevents-method-sftpserver-component) | This method processes events from the internal message queue. | | [ExchangeKeys](#exchangekeys-method-sftpserver-component) | Causes the component to exchange a new set of session keys on the specified connection. | | [Reset](#reset-method-sftpserver-component) | This method will reset the component. | | [SetFileList](#setfilelist-method-sftpserver-component) | Sets the file list for a connection during a directory listing request. | | [Shutdown](#shutdown-method-sftpserver-component) | This method shuts down the server. | | [StartListening](#startlistening-method-sftpserver-component) | This method starts listening for incoming connections. | | [StopListening](#stoplistening-method-sftpserver-component) | This method stops listening for new connections. | ## Event List *The following is the full list of the events fired by the component with short descriptions. Click on the links for further details.* | | | | --- | --- | | [Connected](#connected-event-sftpserver-component) | Fired immediately after a connection completes (or fails). | | [ConnectionRequest](#connectionrequest-event-sftpserver-component) | This event is fired when a request for connection comes from a remote host. | | [DirCreate](#dircreate-event-sftpserver-component) | Fired when a client wants to create a new directory. | | [DirList](#dirlist-event-sftpserver-component) | Fired when a client attempts to open a directory for listing. | | [DirRemove](#dirremove-event-sftpserver-component) | Fired when a client wants to delete a directory. | | [Disconnected](#disconnected-event-sftpserver-component) | This event is fired when a connection is closed. | | [Error](#error-event-sftpserver-component) | Fired when errors occur during data delivery. | | [FileClose](#fileclose-event-sftpserver-component) | Fired when a client attempts to close an open file or directory handle. | | [FileOpen](#fileopen-event-sftpserver-component) | Fired when a client wants to open or create a file. | | [FileRead](#fileread-event-sftpserver-component) | Fired when a client wants to read from an open file. | | [FileRemove](#fileremove-event-sftpserver-component) | Fired when a client wants to delete a file. | | [FileRename](#filerename-event-sftpserver-component) | Fired when a client wants to rename a file. | | [FileWrite](#filewrite-event-sftpserver-component) | Fired when a client wants to write to an open file. | | [GetAttributes](#getattributes-event-sftpserver-component) | Fired when a client needs to get file information. | | [Log](#log-event-sftpserver-component) | Fired once for each log message. | | [ResolvePath](#resolvepath-event-sftpserver-component) | Fired when a client attempts to canonicalize a path. | | [SetAttributes](#setattributes-event-sftpserver-component) | Fired when a client attempts to set file or directory attributes. | | [SSHStatus](#sshstatus-event-sftpserver-component) | Fired to track the progress of the secure connection. | | [SSHUserAuthRequest](#sshuserauthrequest-event-sftpserver-component) | Fired when a client attempts to authenticate a connection. | ## Config Settings *The following is a list of config settings for the component with short descriptions. Click on the links for further details.* | | | | --- | --- | | [DirListBufferSize\[ConnectionId\]](#DirListBufferSize[ConnectionId]) | The number of entries to be returned in one response to a request for a directory listing. | | [MaskSensitiveData](#MaskSensitiveData) | Masks passwords in logs. | | [MaxStartupsConnections](#MaxStartupsConnections) | The number of unauthenticated connections that the server will accept. | | [ProtocolVersion](#ProtocolVersion) | The highest allowable SFTP version to use. | | [ResolveOwnerAndGroup\[ConnectionId\]](#ResolveOwnerAndGroup[ConnectionId]) | Whether to automatically determine the FileOwner and FileGroup. | | [RestrictUserToHomeDir\[ConnectionId\]](#RestrictUserToHomeDir[ConnectionId]) | Whether to restrict the user to their home directory. | | [ServerEOL](#ServerEOL) | Specifies the line endings used in files on the server. | | [SFTPErrorMessage\[ConnectionId\]](#SFTPErrorMessage[ConnectionId]) | Specifies the error message to be returned to the client. | | [UnixStyleDateFormat](#UnixStyleDateFormat) | Controls whether to use the Unix-style date format in directory listings. | | [UserRootDirectory\[ConnectionId\]](#UserRootDirectory[ConnectionId]) | The path of the server root directory for a particular user. | | [AltSSHCertCount](#AltSSHCertCount) | The number of records in the AltSSHCert configuration settings. | | [AltSSHCertStore\[i\]](#AltSSHCertStore[i]) | The name of the certificate store. | | [AltSSHCertStorePassword\[i\]](#AltSSHCertStorePassword[i]) | The password used to open the certificate store. | | [AltSSHCertStoreType\[i\]](#AltSSHCertStoreType[i]) | The type of certificate store. | | [AltSSHCertSubject\[i\]](#AltSSHCertSubject[i]) | The alternative certificate subject. | | [ClientSSHVersionString\[ConnectionId\]](#ClientSSHVersionString[ConnectionId]) | The client's version string. | | [FireAuthRequestAfterSig](#FireAuthRequestAfterSig) | Whether to fire an informational event after the public key signature has been verified. | | [KeyboardInteractivePrompts\[ConnectionId\]](#KeyboardInteractivePrompts[ConnectionId]) | Specifies custom keyboard-interactive prompts for particular connections. | | [KeyRenegotiationThreshold](#KeyRenegotiationThreshold) | Sets the threshold for the SSH Key Renegotiation. | | [LogLevel](#LogLevel) | Specifies the level of detail that is logged. | | [MaxAuthAttempts](#MaxAuthAttempts) | The maximum authentication attempts allowed before forcing a disconnect. | | [NegotiatedStrictKex\[ConnectionId\]](#NegotiatedStrictKex[ConnectionId]) | Returns whether strict key exchange was negotiated to be used. | | [ServerSSHVersionString](#ServerSSHVersionString) | The SSH version string sent to connecting clients. | | [SSHKeepAliveCountMax](#SSHKeepAliveCountMax) | The maximum number of keep alive packets to send without a response. | | [SSHKeepAliveInterval](#SSHKeepAliveInterval) | The interval between keep alive packets. | | [SSHKeyExchangeAlgorithms](#SSHKeyExchangeAlgorithms) | Specifies the supported key exchange algorithms. | | [SSHMacAlgorithms](#SSHMacAlgorithms) | Specifies the supported Mac algorithms. | | [SSHPubKeyAuthSigAlgorithms](#SSHPubKeyAuthSigAlgorithms) | Specifies the allowed signature algorithms used by a client performing public key authentication. | | [SSHPublicKeyAlgorithms](#SSHPublicKeyAlgorithms) | Specifies the supported public key algorithms for the server's public key. | | [SSHVersionPattern](#SSHVersionPattern) | The pattern used to match the remote host's version string. | | [UserAuthBanner\[ConnectionId\]](#UserAuthBanner[ConnectionId]) | A custom user authentication banner. | | [UseStrictKeyExchange](#UseStrictKeyExchange) | Specifies how strict key exchange is supported. | | [AllowedClients](#AllowedClients) | A comma-separated list of host names or IP addresses that can access the component. | | [BindExclusively](#BindExclusively) | Whether or not the component considers a local port reserved for exclusive use. | | [BlockedClients](#BlockedClients) | A comma-separated list of host names or IP addresses that cannot access the component. | | [CloseStreamAfterTransfer](#CloseStreamAfterTransfer) | If true, the component will close the upload or download stream after the transfer. | | [DefaultConnectionTimeout](#DefaultConnectionTimeout) | The inactivity timeout applied to the SSL handshake. | | [InBufferSize](#InBufferSize) | The size in bytes of the incoming queue of the socket. | | [KeepAliveInterval](#KeepAliveInterval) | The retry interval, in milliseconds, to be used when a TCP keep-alive packet is sent and no response is received. | | [KeepAliveTime](#KeepAliveTime) | The inactivity time in milliseconds before a TCP keep-alive packet is sent. | | [MaxConnections](#MaxConnections) | The maximum number of connections available. | | [OutBufferSize](#OutBufferSize) | The size in bytes of the outgoing queue of the socket. | | [PreferredDHGroupBits](#PreferredDHGroupBits) | Size of the Diffie-Hellman group, in bits. | | [TcpNoDelay](#TcpNoDelay) | Whether or not to delay when sending packets. | | [UseBackgroundThread](#UseBackgroundThread) | Whether threads created by the component are background threads. | | [UseIPv6](#UseIPv6) | Whether to use IPv6. | | [BuildInfo](#BuildInfo) | Information about the product's build. | | [GUIAvailable](#GUIAvailable) | Whether or not a message loop is available for processing events. | | [LicenseInfo](#LicenseInfo) | Information about the current license. | | [MaskSensitiveData](#MaskSensitiveData) | Whether sensitive data is masked in log messages. | | [UseFIPSCompliantAPI](#UseFIPSCompliantAPI) | Tells the component whether or not to use FIPS certified APIs. | | [UseInternalSecurityAPI](#UseInternalSecurityAPI) | Whether or not to use the system security libraries or an internal implementation. | # ConnectionBacklog Property ([SFTPServer](#sftpserver-component) Component) This property includes the maximum number of pending connections maintained by the Transmission Control Protocol (TCP)/IP subsystem. ## Syntax ```text public int ConnectionBacklog { get; set; } ``` ## Default Value 5 ## Remarks This property contains the maximum number of pending connections maintained by the TCP/IP subsystem. This value reflects the SOMAXCONN option for the main listening socket. The default value for most systems is 5. You may set this property to a larger value if the server is expected to receive a large number of connections, and queuing them is desirable. This property is not available at design time. # Connections Property ([SFTPServer](#sftpserver-component) Component) The collection of currently connected secure file transfer protocol (SFTP) clients. ## Syntax ```text public SFTPConnectionMap Connections { get; } ``` ## Remarks This property is the collection of currently connected clients. All of the connections may be managed using this property. Each connection is described by the different fields of the [SFTPConnection](#sftpconnection-type) type. This property is read-only. Please refer to the [SFTPConnection](#sftpconnection-type) type for a complete list of fields. # DefaultAuthMethods Property ([SFTPServer](#sftpserver-component) Component) The supported authentication methods. ## Syntax ```text public string DefaultAuthMethods { get; set; } ``` ## Default Value "password,publickey" ## Remarks This property specifies the supported authentication methods. The client will choose one of the supported mechanisms when authenticating to the component. This must be a comma-separated list of values. For more information on authenticating clients, see the [SSHUserAuthRequest](#sshuserauthrequest-event-sftpserver-component) event. The following is a list of methods implemented by the component: | | | | --- | --- | | none | This authentication method is used by most Secure Shell (SSH) clients to obtain the list of authentication methods available for the user's account. In most cases, you should not accept a request using this authentication method. | | password | AuthParam will contain the user-supplied password. If the password is correct, set Accept to True. | | publickey | AuthParam will contain an SSH2 public key blob. If the user's public key is acceptable, set Accept or PartialSuccess to true. The component will then handle verifying the digital signature and will respond to the client accordingly. | | keyboard-interactive | [SSHUserAuthRequest](#sshuserauthrequest-event-sftpserver-component) will fire multiple times for keyboard-interactive authentication: It will fire once for each response sent by the client in the SSH_MSG_USERAUTH_INFO_RESPONSE packet (one time for each prompt specified by the daemon). The index of each response will be specified as a suffix in AuthMethod, with AuthParam containing the response to the corresponding prompt (e.g., keyboard-interactive-1, keyboard-interactive-2, and so on). Finally, [SSHUserAuthRequest](#sshuserauthrequest-event-sftpserver-component) will fire one last time with AuthMethod set to "keyboard-interactive" and AuthParam set to an empty string. The daemon must set Accept to True every time to allow the authentication process to succeed. | # DefaultTimeout Property ([SFTPServer](#sftpserver-component) Component) The initial timeout value to be used by incoming connections. ## Syntax ```text public int DefaultTimeout { get; set; } ``` ## Default Value 60 ## Remarks If the DefaultTimeout property is set to 0, all operations will run uninterrupted until successful completion or an error condition is encountered. If DefaultTimeout is set to a positive value, the component will wait for the operation to complete before returning control. The component will use [DoEvents](#doevents-method-sftpserver-component) to enter an efficient wait loop during any potential waiting period, making sure that all system events are processed immediately as they arrive. This ensures that the host application does not freeze and remains responsive. If Timeout expires, and the operation is not yet complete, the component throws an exception. NOTE: By default, all timeouts are *inactivity timeouts*, that is, the timeout period is extended by Timeout seconds when any amount of data is successfully sent or received. The default value for the DefaultTimeout property is 60 (seconds). # KeyboardInteractiveMessage Property ([SFTPServer](#sftpserver-component) Component) The instructions to send to the client during keyboard-interactive authentication. ## Syntax ```text public string KeyboardInteractiveMessage { get; set; } ``` ## Default Value "" ## Remarks This property should be set to the main instructions to send to the client during keyboard-interactive authentication. # KeyboardInteractivePrompts Property ([SFTPServer](#sftpserver-component) Component) A collection of prompts to present to the user during keyboard-interactive authentication. ## Syntax ```text public SSHPromptList KeyboardInteractivePrompts { get; } ``` ## Remarks This property is a collection of prompts to present to the user during keyboard-authentication. It is used together with the [KeyboardInteractiveMessage](#keyboardinteractivemessage-property-sftpserver-component) property. Please refer to the [SSHPrompt](#sshprompt-type) type for a complete list of fields. # Listening Property ([SFTPServer](#sftpserver-component) Component) This property indicates whether the component is listening for incoming connections on LocalPort. ## Syntax ```text public bool Listening { get; } ``` ## Default Value False ## Remarks This property indicates whether the component is listening for connections on the port specified by the [LocalPort](#localport-property-sftpserver-component) property. Use the [StartListening](#startlistening-method-sftpserver-component) and [StopListening](#stoplistening-method-sftpserver-component) methods to control whether the component is listening. This property is read-only and not available at design time. # LocalHost Property ([SFTPServer](#sftpserver-component) Component) The name of the local host or user-assigned IP interface through which connections are initiated or accepted. ## Syntax ```text public string LocalHost { get; set; } ``` ## Default Value "" ## Remarks This property contains the name of the local host as obtained by the *gethostname()* system call, or if the user has assigned an IP address, the value of that address. In multihomed hosts (machines with more than one IP interface) setting LocalHost to the IP address of an interface will make the component initiate connections (or accept in the case of server components) only through that interface. It is recommended to provide an IP address rather than a hostname when setting this property to ensure the desired interface is used. If the component is connected, the LocalHost property shows the IP address of the interface through which the connection is made in internet dotted format (aaa.bbb.ccc.ddd). In most cases, this is the address of the local host, except for multihomed hosts (machines with more than one IP interface). NOTE: LocalHost is not persistent. You must always set it in code, and never in the property window. # LocalPort Property ([SFTPServer](#sftpserver-component) Component) The Transmission Control Protocol (TCP) port in the local host where the component listens. ## Syntax ```text public int LocalPort { get; set; } ``` ## Default Value 22 ## Remarks The LocalPort property must be set before TCPServer starts listening. If its value is 0, then the TCP/IP subsystem picks a port number at random. The port number can be found by checking the value of the LocalPort property after TCPServer is in listening mode (after successfully assigning True to the [Listening](#listening-property-sftpserver-component) property). NOTE: The service port is not shared among servers (i.e., only one TCPServer can be 'listening' on a particular port at one time). # RootDirectory Property ([SFTPServer](#sftpserver-component) Component) The root directory for the entire secure file transfer protocol (SFTP) server. ## Syntax ```text public string RootDirectory { get; set; } ``` ## Default Value "" ## Remarks RootDirectory specifies the root of the SFTP server ('/'). If a value is provided, the component will handle all requests by doing all file operations itself, but the events will still give you the opportunity to override the default values and operations, as necessary. If a value is not provided, all events must be handled appropriately to ensure correct operation. # SSHCert Property ([SFTPServer](#sftpserver-component) Component) The certificate(s) to be used during Secure Shell (SSH) negotiation. ## Syntax ```text public CertificateList SSHCert { get; } ``` ## Remarks The digital certificate(s) that the server will use during SSH negotiation. Certificates with a private key are required for session authentication and encryption. These are the server's certificates, and they must be specified before the server starts listening. Please refer to the [Certificate](#certificate-type) type for a complete list of fields. # SSHCompressionAlgorithms Property ([SFTPServer](#sftpserver-component) Component) The comma-separated list containing all allowable compression algorithms. ## Syntax ```text public string SSHCompressionAlgorithms { get; set; } ``` ## Default Value "none,zlib" ## Remarks During the Secure Shell (SSH) handshake, this list will be used to negotiate the compression algorithm to be used between the client and server. This list is used for both directions: client to server and server to client. When negotiating algorithms, each side sends a list of all algorithms it supports or allows. The algorithm chosen for each direction is the first algorithm to appear in the sender's list that the receiver supports. Therefore, it is important to list multiple algorithms in preferential order. If no algorithm can be agreed on, the component will raise an error and the connection will be aborted. At least one supported algorithm must appear in this list. The following compression algorithms are supported by the component: - zlib - zlib@openssh.com - none # SSHEncryptionAlgorithms Property ([SFTPServer](#sftpserver-component) Component) The comma-separated list containing all allowable encryption algorithms. ## Syntax ```text public string SSHEncryptionAlgorithms { get; set; } ``` ## Default Value "aes256-ctr,aes192-ctr,aes128-ctr,3des-ctr,aes256-gcm@openssh.com,aes128-gcm@openssh.com,chacha20-poly1305@openssh.com" ## Remarks During the Secure Shell (SSH) handshake, this list will be used to negotiate the encryption algorithm to be used between the client and server. This list is used for both directions: client to server and server to client. When negotiating algorithms, each side sends a list of all algorithms it supports or allows. The algorithm chosen for each direction is the first algorithm to appear in the sender's list that the receiver supports. Therefore, it is important to list multiple algorithms in preferential order. If no algorithm can be agreed on, the component will raise an error and the connection will be aborted. At least one supported algorithm must appear in this list. The following encryption algorithms are supported by the component: - aes256-ctr - aes256-cbc - aes192-ctr - aes192-cbc - aes128-ctr - aes128-cbc - 3des-ctr - 3des-cbc - cast128-cbc - blowfish-cbc - arcfour - arcfour128 - arcfour256 - aes256-gcm@openssh.com - aes128-gcm@openssh.com - chacha20-poly1305@openssh.com # Config Method ([SFTPServer](#sftpserver-component) Component) Sets or retrieves a configuration setting. ## Syntax ```text public string Config(string configurationString); Async Version public async Task Config(string configurationString); public async Task Config(string configurationString, CancellationToken cancellationToken); ``` ## Remarks Config is a generic method available in every component. It is used to set and retrieve [configuration settings](#config-settings-sftpserver-component) for the component. These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these *internal properties* is provided through the Config method. To set a configuration setting named *PROPERTY*, you must call *Config("PROPERTY=VALUE")*, where *VALUE* is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter). To read (query) the value of a [configuration setting](#config-settings-sftpserver-component), you must call *Config("PROPERTY")*. The value will be returned as a string. # Disconnect Method ([SFTPServer](#sftpserver-component) Component) This method disconnects the specified client. ## Syntax ```text public void Disconnect(string connectionId); Async Version public async Task Disconnect(string connectionId); public async Task Disconnect(string connectionId, CancellationToken cancellationToken); ``` ## Remarks Calling this method will disconnect the client specified by the *ConnectionId* parameter. # DoEvents Method ([SFTPServer](#sftpserver-component) Component) This method processes events from the internal message queue. ## Syntax ```text public void DoEvents(); Async Version public async Task DoEvents(); public async Task DoEvents(CancellationToken cancellationToken); ``` ## Remarks When DoEvents is called, the component processes any available events. If no events are available, it waits for a preset period of time, and then returns. # ExchangeKeys Method ([SFTPServer](#sftpserver-component) Component) Causes the component to exchange a new set of session keys on the specified connection. ## Syntax ```text public void ExchangeKeys(string connectionId); Async Version public async Task ExchangeKeys(string connectionId); public async Task ExchangeKeys(string connectionId, CancellationToken cancellationToken); ``` ## Remarks Secure Shell (SSH) key renegotiation can be initiated by either end of an established SSH connection. ExchangeKeys allows the server to start such a renegotiation with the client. During this process, [SSHStatus](#sshstatus-event-sftpserver-component) events will fire with updates about the key negotiation process. The SSH 2.0 specification recommends that key renegotiation be done once for 2 gigabytes (GB) of data processed by the connection, or once every day. This makes it more difficult to break the security of data-intensive or long-lived connections. # Reset Method ([SFTPServer](#sftpserver-component) Component) This method will reset the component. ## Syntax ```text public void Reset(); Async Version public async Task Reset(); public async Task Reset(CancellationToken cancellationToken); ``` ## Remarks This method will reset the component's properties to their default values. # SetFileList Method ([SFTPServer](#sftpserver-component) Component) Sets the file list for a connection during a directory listing request. ## Syntax ```text public void SetFileList(string connectionId, string[] list); Async Version public async Task SetFileList(string connectionId, string[] list); public async Task SetFileList(string connectionId, string[] list, CancellationToken cancellationToken); ``` ## Remarks SetFileList should be set when a directory listing is requested by the client. # Shutdown Method ([SFTPServer](#sftpserver-component) Component) This method shuts down the server. ## Syntax ```text public void Shutdown(); Async Version public async Task Shutdown(); public async Task Shutdown(CancellationToken cancellationToken); ``` ## Remarks This method shuts down the server. Calling this method is equivalent to calling [StopListening](#stoplistening-method-sftpserver-component) and then breaking every client connection by calling [Disconnect](#disconnect-method-sftpserver-component). # StartListening Method ([SFTPServer](#sftpserver-component) Component) This method starts listening for incoming connections. ## Syntax ```text public void StartListening(); Async Version public async Task StartListening(); public async Task StartListening(CancellationToken cancellationToken); ``` ## Remarks This method begins listening for incoming connections on the port specified by [LocalPort](#localport-property-sftpserver-component). Once listening, events will fire as new clients connect and data are transferred. To stop listening for new connections, call [StopListening](#stoplistening-method-sftpserver-component). To stop listening for new connections and to disconnect all existing clients, call [Shutdown](#shutdown-method-sftpserver-component). # StopListening Method ([SFTPServer](#sftpserver-component) Component) This method stops listening for new connections. ## Syntax ```text public void StopListening(); Async Version public async Task StopListening(); public async Task StopListening(CancellationToken cancellationToken); ``` ## Remarks This method stops listening for new connections. After being called, any new connection attempts will be rejected. Calling this method does not disconnect existing connections. To stop listening and to disconnect all existing clients, call [Shutdown](#shutdown-method-sftpserver-component) instead. # Connected Event ([SFTPServer](#sftpserver-component) Component) Fired immediately after a connection completes (or fails). ## Syntax ```text public event OnConnectedHandler OnConnected; public delegate void OnConnectedHandler(object sender, SFTPServerConnectedEventArgs e); public class SFTPServerConnectedEventArgs : EventArgs { public string ConnectionId { get; } public int StatusCode { get; } public string Description { get; } public int CertStoreType { get; set; } public string CertStore { get; set; } public string CertPassword { get; set; } public string CertSubject { get; set; } } ``` ## Remarks If the connection is made normally, *StatusCode* is 0, and *Description* is "OK". If the connection fails, *StatusCode* has the error code returned by the system. *Description* contains a description of this code. The value of *StatusCode* is equal to the value of the system error. Please refer to the [Error Codes](#trappable-errors-sftpserver-component) section for more information. *ConnectionId* is the connection Id of the client requesting the connection. *CertStoreType* is the store type of the alternate certificate to use for this connection. The component supports both public and private keys in a variety of formats. When the *cstAuto* value is used, the component will automatically determine the type. This field can take one of the following values: ```csharp sftp.SSHCert = new Certificate(CertStoreTypes.cstPKCS11, @"C:\Program Files\OpenSC Project\OpenSC\pkcs11\opensc-pkcs11.dll", "123456", // PIN "CN=cert_subject"); sftp.SSHUser = "test"; sftp.SSHLogon("myhost", 22); ``` ```csharp certmgr.CertStoreType = CertStoreTypes.cstPKCS11; certmgr.OnCertList += (s, e) => { secKeyBlob = e.CertEncoded; }; certmgr.CertStore = @"C:\Program Files\OpenSC Project\OpenSC\pkcs11\opensc-pkcs11.dll"; certmgr.CertStorePassword = "123456"; // PIN certmgr.ListStoreCertificates(); sftp.SSHCert = new Certificate(CertStoreTypes.cstPKCS11, secKeyBlob, "123456", "*"); sftp.SSHUser = "test"; sftp.SSHLogon("myhost", 22); ``` | | | | --- | --- | | 0 (cstUser - default) | For Windows, this specifies that the certificate store is a certificate store owned by the current user. NOTE: This store type is not available in Java. | | 1 (cstMachine) | For Windows, this specifies that the certificate store is a machine store. NOTE: This store type is not available in Java. | | 2 (cstPFXFile) | The certificate store is the name of a PFX (PKCS#12) file containing certificates. | | 3 (cstPFXBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in PFX (PKCS#12) format. | | 4 (cstJKSFile) | The certificate store is the name of a Java Key Store (JKS) file containing certificates. NOTE: This store type is only available in Java. | | 5 (cstJKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in Java Key Store (JKS) format. NOTE: This store type is only available in Java. | | 6 (cstPEMKeyFile) | The certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate. | | 7 (cstPEMKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a private key and an optional certificate. | | 8 (cstPublicKeyFile) | The certificate store is the name of a file that contains a PEM- or DER-encoded public key certificate. | | 9 (cstPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a PEM- or DER-encoded public key certificate. | | 10 (cstSSHPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains an SSH-style public key. | | 11 (cstP7BFile) | The certificate store is the name of a PKCS#7 file containing certificates. | | 12 (cstP7BBlob) | The certificate store is a string (binary) representing a certificate store in PKCS#7 format. | | 13 (cstSSHPublicKeyFile) | The certificate store is the name of a file that contains an SSH-style public key. | | 14 (cstPPKFile) | The certificate store is the name of a file that contains a PPK (PuTTY Private Key). | | 15 (cstPPKBlob) | The certificate store is a string (binary) that contains a PPK (PuTTY Private Key). | | 16 (cstXMLFile) | The certificate store is the name of a file that contains a certificate in XML format. | | 17 (cstXMLBlob) | The certificate store is a string that contains a certificate in XML format. | | 18 (cstJWKFile) | The certificate store is the name of a file that contains a JWK (JSON Web Key). | | 19 (cstJWKBlob) | The certificate store is a string that contains a JWK (JSON Web Key). | | 21 (cstBCFKSFile) | The certificate store is the name of a file that contains a BCFKS (Bouncy Castle FIPS Key Store). NOTE: This store type is only available in Java and .NET. | | 22 (cstBCFKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in BCFKS (Bouncy Castle FIPS Key Store) format. NOTE: This store type is only available in Java and .NET. | | 23 (cstPKCS11) | The certificate is present on a physical security key accessible via a PKCS#11 interface. To use a security key, create a new [Certificate](#certificate-type) object and pass cstPKCS11 as the [StoreType](#Certificate_f_StoreType), the full path of the PKCS#11 DLL as the [Store](#Certificate_f_Store), and the PIN as the [StorePassword](#Certificate_f_StorePassword). Code Example. SSH Authentication with Security Key (without CertMgr): Alternatively, collect the necessary data using the [CertMgr](CertMgr.md#CertMgr) component by calling the [ListStoreCertificates](CertMgr.md#CertMgr_m_ListStoreCertificates) method after setting the corresponding properties accordingly. The certificate information returned in the [CertList](CertMgr.md#CertMgr_e_CertList) event's CertEncoded parameter may be saved for later use. When using a certificate obtained with this approach, pass the previously saved security key information as the [Store](#Certificate_f_Store) and set [StorePassword](#Certificate_f_StorePassword) to the PIN. Code Example. SSH Authentication with Security Key (with CertMgr): | | 99 (cstAuto) | The store type is automatically detected from the input data. This setting may be used with both public and private keys and can detect any of the supported formats automatically. | *CertStore* is the store name or location of the alternate certificate to use for this connection. Designations of certificate stores are platform dependent. The following designations are the most common User and Machine certificate stores in Windows: | | | | --- | --- | | MY | A certificate store holding personal certificates with their associated private keys. | | CA | Certifying authority certificates. | | ROOT | Root certificates. | When the certificate store type is *cstPFXFile*, this property must be set to the name of the file. When the type is *cstPFXBlob*, the property must be set to the binary contents of a PFX file (i.e., PKCS#12 certificate store). *CertPassword* is the password of the certificate store containing the alternate certificate to use for this connection. *CertSubject* is the subject of the alternate certificate to use for this connection. The special value *** matches any subject and will select the first certificate in the store. The certificate subject is a comma-separated list of distinguished name fields and values. For instance, "CN=www.server.com, OU=test, C=US, E=example@email.com". Common fields and their meanings are as follows: | Field | Meaning | | --- | --- | | CN | Common Name. This is commonly a hostname like www.server.com. | | O | Organization | | OU | Organizational Unit | | L | Locality | | S | State | | C | Country | | E | Email Address | If a field value contains a comma, it must be quoted. # ConnectionRequest Event ([SFTPServer](#sftpserver-component) Component) This event is fired when a request for connection comes from a remote host. ## Syntax ```text public event OnConnectionRequestHandler OnConnectionRequest; public delegate void OnConnectionRequestHandler(object sender, SFTPServerConnectionRequestEventArgs e); public class SFTPServerConnectionRequestEventArgs : EventArgs { public string Address { get; } public int Port { get; } public bool Accept { get; set; } } ``` ## Remarks This event indicates an incoming connection. The connection is accepted by default. *Address* and *Port* will contain information about the remote host requesting the inbound connection. If you want to refuse it, you can set the *Accept* parameter to False. # DirCreate Event ([SFTPServer](#sftpserver-component) Component) Fired when a client wants to create a new directory. ## Syntax ```text public event OnDirCreateHandler OnDirCreate; public delegate void OnDirCreateHandler(object sender, SFTPServerDirCreateEventArgs e); public class SFTPServerDirCreateEventArgs : EventArgs { public string ConnectionId { get; } public string User { get; } public string Path { get; } public int FileType { get; } public long FileSize { get; } public string FileOwner { get; } public string FileGroup { get; } public int FilePermissions { get; } public long FileATime { get; } public long FileCreateTime { get; } public long FileMTime { get; } public int FileAttribBits { get; } public int FileAttribBitsValid { get; } public string OtherAttributes { get; } public bool BeforeExec { get; } public int StatusCode { get; set; } } ``` ## Remarks The *Path* parameter specifies the path and name of the new directory. This event is fired both before and after the directory is created. The *BeforeExec* parameter is *True* before the operation has been executed and *False* otherwise. Handling this event before execution of the operation provides an opportunity to add custom logic that may prevent or deny the operation. Handling this event after execution of the operation provides an opportunity to report any errors that may have occurred during the operation. File/Directory Attributes are specified using the following values: *FileType*: The type of file. Can be one of the following values: - SSH_FILEXFER_TYPE_REGULAR (1) - SSH_FILEXFER_TYPE_DIRECTORY (2) - SSH_FILEXFER_TYPE_SYMLINK (3) - SSH_FILEXFER_TYPE_SPECIAL (4) - SSH_FILEXFER_TYPE_UNKNOWN (5) - SSH_FILEXFER_TYPE_SOCKET (6) - SSH_FILEXFER_TYPE_CHAR_DEVICE (7) - SSH_FILEXFER_TYPE_BLOCK_DEVICE (8) - SSH_FILEXFER_TYPE_FIFO (9) *FileSize*: The file size, in bytes. *FileOwner*: The file owner. If the ProtocolVersion configuration option is "3" (default), this field should be a numeric Unix-like user identifier. V4, V5, and V6 of the secure file transfer protocol (SFTP) allow for an arbitrary string. *FileGroup*: The file owner group. If the ProtocolVersion configuration option is "3" (default), this field should be a numeric Unix-like group identifier. V4, V5, and V6 of the SFTP allow for an arbitrary string. *FilePermissions*: The POSIX-style file permissions. *FileATime*: The file last-access time, in milliseconds since January 1, 1970, in UTC. *FileCreateTime*: The file creation time, in milliseconds since January 1, 1970, in UTC. *FileMTime*: The file last-modified time, in milliseconds since January 1, 1970, in UTC. *FileAttrBits*: The file attributes, as a combination of the following values: - SSH_FILEXFER_ATTR_FLAGS_READONLY (0x00000001) - SSH_FILEXFER_ATTR_FLAGS_SYSTEM (0x00000002) - SSH_FILEXFER_ATTR_FLAGS_HIDDEN (0x00000004) - SSH_FILEXFER_ATTR_FLAGS_CASE_INSENSITIVE (0x00000008) - SSH_FILEXFER_ATTR_FLAGS_ARCHIVE (0x00000010) - SSH_FILEXFER_ATTR_FLAGS_ENCRYPTED (0x00000020) - SSH_FILEXFER_ATTR_FLAGS_COMPRESSED (0x00000040) - SSH_FILEXFER_ATTR_FLAGS_SPARSE (0x00000080) - SSH_FILEXFER_ATTR_FLAGS_APPEND_ONLY (0x00000100) - SSH_FILEXFER_ATTR_FLAGS_IMMUTABLE (0x00000200) - SSH_FILEXFER_ATTR_FLAGS_SYNC (0x00000400) - SSH_FILEXFER_ATTR_FLAGS_TRANSLATION_ERR (0x00000800) *FileAttrBitsValid*: A mask specifying which bits in *FileAttrBits* are supported by the server. *OtherAttributes*: A semicolon (;) delimited list of Name=Value pairs of other attributes supported by SFTP. These include the following: - MIMEType (String) - AllocationSize (64-bit int) - ATimeNS (int): ATime nanoseconds - CreateTimeNS (int): CreateTime nanoseconds - MTimeNS (int): MTime nanoseconds - TextHint (8-bit int) - LinkCount (int) - UntranslatedName (String) *FileMimeType*: The MIME type of the file. Valid status codes are as follows: - SSH_FX_OK 0 - SSH_FX_EOF 1 - SSH_FX_NO_SUCH_FILE 2 - SSH_FX_PERMISSION_DENIED 3 - SSH_FX_FAILURE 4 - SSH_FX_BAD_MESSAGE 5 - SSH_FX_NO_CONNECTION 6 - SSH_FX_CONNECTION_LOST 7 - SSH_FX_OP_UNSUPPORTED 8 - SSH_FX_INVALID_HANDLE 9 - SSH_FX_NO_SUCH_PATH 10 - SSH_FX_FILE_ALREADY_EXISTS 11 - SSH_FX_WRITE_PROTECT 12 - SSH_FX_NO_MEDIA 13 - SSH_FX_NO_SPACE_ON_FILESYSTEM 14 - SSH_FX_QUOTA_EXCEEDED 15 - SSH_FX_UNKNOWN_PRINCIPAL 16 - SSH_FX_LOCK_CONFLICT 17 - SSH_FX_DIR_NOT_EMPTY 18 - SSH_FX_NOT_A_DIRECTORY 19 - SSH_FX_INVALID_FILENAME 20 - SSH_FX_LINK_LOOP 21 - SSH_FX_CANNOT_DELETE 22 - SSH_FX_INVALID_PARAMETER 23 - SSH_FX_FILE_IS_A_DIRECTORY 24 - SSH_FX_BYTE_RANGE_LOCK_CONFLICT 25 - SSH_FX_BYTE_RANGE_LOCK_REFUSED 26 - SSH_FX_DELETE_PENDING 27 - SSH_FX_FILE_CORRUPT 28 - SSH_FX_OWNER_INVALID 29 - SSH_FX_GROUP_INVALID 30 - SSH_FX_NO_MATCHING_BYTE_RANGE_LOCK 31 # DirList Event ([SFTPServer](#sftpserver-component) Component) Fired when a client attempts to open a directory for listing. ## Syntax ```text public event OnDirListHandler OnDirList; public delegate void OnDirListHandler(object sender, SFTPServerDirListEventArgs e); public class SFTPServerDirListEventArgs : EventArgs { public string ConnectionId { get; } public string User { get; } public string Path { get; } public bool BeforeExec { get; } public int StatusCode { get; set; } } ``` ## Remarks The DirList event is fired when a secure file transfer protocol (SFTP) client sends an SSH_FXP_OPENDIR request. The *Path* parameter will contain the path of the directory to list. When necessary, you should call [SetFileList](#setfilelist-method-sftpserver-component) with the list of files and directories in *Path*. This event is fired both before and after the directory is listed. The *BeforeExec* parameter is *True* before the operation has been executed and *False* otherwise. Handling this event before execution of the operation provides an opportunity to add custom logic that may prevent or deny the operation. Handling this event after execution of the operation provides an opportunity to report any errors that may have occurred during the operation. Valid status codes are as follows: - SSH_FX_OK 0 - SSH_FX_EOF 1 - SSH_FX_NO_SUCH_FILE 2 - SSH_FX_PERMISSION_DENIED 3 - SSH_FX_FAILURE 4 - SSH_FX_BAD_MESSAGE 5 - SSH_FX_NO_CONNECTION 6 - SSH_FX_CONNECTION_LOST 7 - SSH_FX_OP_UNSUPPORTED 8 - SSH_FX_INVALID_HANDLE 9 - SSH_FX_NO_SUCH_PATH 10 - SSH_FX_FILE_ALREADY_EXISTS 11 - SSH_FX_WRITE_PROTECT 12 - SSH_FX_NO_MEDIA 13 - SSH_FX_NO_SPACE_ON_FILESYSTEM 14 - SSH_FX_QUOTA_EXCEEDED 15 - SSH_FX_UNKNOWN_PRINCIPAL 16 - SSH_FX_LOCK_CONFLICT 17 - SSH_FX_DIR_NOT_EMPTY 18 - SSH_FX_NOT_A_DIRECTORY 19 - SSH_FX_INVALID_FILENAME 20 - SSH_FX_LINK_LOOP 21 - SSH_FX_CANNOT_DELETE 22 - SSH_FX_INVALID_PARAMETER 23 - SSH_FX_FILE_IS_A_DIRECTORY 24 - SSH_FX_BYTE_RANGE_LOCK_CONFLICT 25 - SSH_FX_BYTE_RANGE_LOCK_REFUSED 26 - SSH_FX_DELETE_PENDING 27 - SSH_FX_FILE_CORRUPT 28 - SSH_FX_OWNER_INVALID 29 - SSH_FX_GROUP_INVALID 30 - SSH_FX_NO_MATCHING_BYTE_RANGE_LOCK 31 # DirRemove Event ([SFTPServer](#sftpserver-component) Component) Fired when a client wants to delete a directory. ## Syntax ```text public event OnDirRemoveHandler OnDirRemove; public delegate void OnDirRemoveHandler(object sender, SFTPServerDirRemoveEventArgs e); public class SFTPServerDirRemoveEventArgs : EventArgs { public string ConnectionId { get; } public string User { get; } public string Path { get; } public bool BeforeExec { get; } public int StatusCode { get; set; } } ``` ## Remarks The *Path* parameter will specify the directory to delete. This event is fired both before and after the directory is deleted. The *BeforeExec* parameter is *True* before the operation has been executed and *False* otherwise. Handling this event before execution of the operation provides an opportunity to add custom logic that may prevent or deny the operation. Handling this event after execution of the operation provides an opportunity to report any errors that may have occurred during the operation. Valid status codes are as follows: - SSH_FX_OK 0 - SSH_FX_EOF 1 - SSH_FX_NO_SUCH_FILE 2 - SSH_FX_PERMISSION_DENIED 3 - SSH_FX_FAILURE 4 - SSH_FX_BAD_MESSAGE 5 - SSH_FX_NO_CONNECTION 6 - SSH_FX_CONNECTION_LOST 7 - SSH_FX_OP_UNSUPPORTED 8 - SSH_FX_INVALID_HANDLE 9 - SSH_FX_NO_SUCH_PATH 10 - SSH_FX_FILE_ALREADY_EXISTS 11 - SSH_FX_WRITE_PROTECT 12 - SSH_FX_NO_MEDIA 13 - SSH_FX_NO_SPACE_ON_FILESYSTEM 14 - SSH_FX_QUOTA_EXCEEDED 15 - SSH_FX_UNKNOWN_PRINCIPAL 16 - SSH_FX_LOCK_CONFLICT 17 - SSH_FX_DIR_NOT_EMPTY 18 - SSH_FX_NOT_A_DIRECTORY 19 - SSH_FX_INVALID_FILENAME 20 - SSH_FX_LINK_LOOP 21 - SSH_FX_CANNOT_DELETE 22 - SSH_FX_INVALID_PARAMETER 23 - SSH_FX_FILE_IS_A_DIRECTORY 24 - SSH_FX_BYTE_RANGE_LOCK_CONFLICT 25 - SSH_FX_BYTE_RANGE_LOCK_REFUSED 26 - SSH_FX_DELETE_PENDING 27 - SSH_FX_FILE_CORRUPT 28 - SSH_FX_OWNER_INVALID 29 - SSH_FX_GROUP_INVALID 30 - SSH_FX_NO_MATCHING_BYTE_RANGE_LOCK 31 # Disconnected Event ([SFTPServer](#sftpserver-component) Component) This event is fired when a connection is closed. ## Syntax ```text public event OnDisconnectedHandler OnDisconnected; public delegate void OnDisconnectedHandler(object sender, SFTPServerDisconnectedEventArgs e); public class SFTPServerDisconnectedEventArgs : EventArgs { public string ConnectionId { get; } public int StatusCode { get; } public string Description { get; } } ``` ## Remarks If the connection is broken normally, *StatusCode* is 0, and *Description* is "OK". If the connection is broken for any other reason, *StatusCode* has the error code returned by the system. *Description* contains a description of this code. The value of *StatusCode* is equal to the value of the system error. Please refer to the [Error Codes](#trappable-errors-sftpserver-component) section for more information. # Error Event ([SFTPServer](#sftpserver-component) Component) Fired when errors occur during data delivery. ## Syntax ```text public event OnErrorHandler OnError; public delegate void OnErrorHandler(object sender, SFTPServerErrorEventArgs e); public class SFTPServerErrorEventArgs : EventArgs { public string ConnectionId { get; } public int ErrorCode { get; } public string Description { get; } } ``` ## Remarks The Error event is fired in case of exceptional conditions during message processing. Normally the component throws an exception. *ConnectionId* contains an error code and *Description* contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the [Error Codes](#trappable-errors-sftpserver-component) section. *ErrorCode* contains an error code and *Description* contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the [Error Codes](#trappable-errors-sftpserver-component) section. # FileClose Event ([SFTPServer](#sftpserver-component) Component) Fired when a client attempts to close an open file or directory handle. ## Syntax ```text public event OnFileCloseHandler OnFileClose; public delegate void OnFileCloseHandler(object sender, SFTPServerFileCloseEventArgs e); public class SFTPServerFileCloseEventArgs : EventArgs { public string ConnectionId { get; } public string User { get; } public string Path { get; } public string Handle { get; } public int StatusCode { get; set; } } ``` ## Remarks The FileClose event is fired when a secure file transfer protocol (SFTP) client sends an SSH_FXP_CLOSE request. The *Path* parameter will contain the path of the file to close. Valid status codes are as follows: - SSH_FX_OK 0 - SSH_FX_EOF 1 - SSH_FX_NO_SUCH_FILE 2 - SSH_FX_PERMISSION_DENIED 3 - SSH_FX_FAILURE 4 - SSH_FX_BAD_MESSAGE 5 - SSH_FX_NO_CONNECTION 6 - SSH_FX_CONNECTION_LOST 7 - SSH_FX_OP_UNSUPPORTED 8 - SSH_FX_INVALID_HANDLE 9 - SSH_FX_NO_SUCH_PATH 10 - SSH_FX_FILE_ALREADY_EXISTS 11 - SSH_FX_WRITE_PROTECT 12 - SSH_FX_NO_MEDIA 13 - SSH_FX_NO_SPACE_ON_FILESYSTEM 14 - SSH_FX_QUOTA_EXCEEDED 15 - SSH_FX_UNKNOWN_PRINCIPAL 16 - SSH_FX_LOCK_CONFLICT 17 - SSH_FX_DIR_NOT_EMPTY 18 - SSH_FX_NOT_A_DIRECTORY 19 - SSH_FX_INVALID_FILENAME 20 - SSH_FX_LINK_LOOP 21 - SSH_FX_CANNOT_DELETE 22 - SSH_FX_INVALID_PARAMETER 23 - SSH_FX_FILE_IS_A_DIRECTORY 24 - SSH_FX_BYTE_RANGE_LOCK_CONFLICT 25 - SSH_FX_BYTE_RANGE_LOCK_REFUSED 26 - SSH_FX_DELETE_PENDING 27 - SSH_FX_FILE_CORRUPT 28 - SSH_FX_OWNER_INVALID 29 - SSH_FX_GROUP_INVALID 30 - SSH_FX_NO_MATCHING_BYTE_RANGE_LOCK 31 # FileOpen Event ([SFTPServer](#sftpserver-component) Component) Fired when a client wants to open or create a file. ## Syntax ```text public event OnFileOpenHandler OnFileOpen; public delegate void OnFileOpenHandler(object sender, SFTPServerFileOpenEventArgs e); public class SFTPServerFileOpenEventArgs : EventArgs { public string ConnectionId { get; } public string User { get; } public string Path { get; } public int DesiredAccess { get; } public int Flags { get; } public int FileType { get; } public long FileSize { get; } public string FileOwner { get; } public string FileGroup { get; } public int FilePermissions { get; } public long FileATime { get; } public long FileCreateTime { get; } public long FileMTime { get; } public int FileAttribBits { get; } public int FileAttribBitsValid { get; } public string OtherAttributes { get; } public string Handle { get; set; } public bool BeforeExec { get; } public int StatusCode { get; set; } } ``` ## Remarks The *Path* parameter specifies the path and name of the file to open, create. If the operation can be completed successfully, the *Handle* parameter should be set to the handle identifying the opened file. NOTE: The *Handle* parameter is limited to a 256-byte string. By default, the component will provide an incremental numeric string value for the Handle. This event is fired both before and after the file is opened. The *BeforeExec* parameter is *True* before the operation has been executed and *False* otherwise. Handling this event before execution of the operation provides an opportunity to add custom logic that may prevent or deny the operation. Handling this event after execution of the operation provides an opportunity to report any errors that may have occurred during the operation. The *Flags* parameter specifies file creation and locking options as a bitmask. This may be a combination of the following values: - SSH_FXF_READ (0x00000001) - SSH_FXF_WRITE (0x00000002) - SSH_FXF_APPEND (0x00000004) - SSH_FXF_CREAT (0x00000008) - SSH_FXF_TRUNC (0x00000010) - SSH_FXF_EXCL (0x00000020) The *DesiredAccess* parameter is a bitmask containing a combination of values from the ace-mask flags (only for protocol versions 4 and up). This may be a combination of the following values: - ACE4_READ_DATA (0x00000001) - ACE4_LIST_DIRECTORY (0x00000001) - ACE4_WRITE_DATA (0x00000002) - ACE4_ADD_FILE (0x00000002) - ACE4_APPEND_DATA (0x00000004) - ACE4_ADD_SUBDIRECTORY (0x00000004) - ACE4_READ_NAMED_ATTRS (0x00000008) - ACE4_WRITE_NAMED_ATTRS (0x00000010) - ACE4_EXECUTE (0x00000020) - ACE4_DELETE_CHILD (0x00000040) - ACE4_READ_ATTRIBUTES (0x00000080) - ACE4_WRITE_ATTRIBUTES (0x00000100) - ACE4_DELETE (0x00010000) - ACE4_READ_ACL (0x00020000) - ACE4_WRITE_ACL (0x00040000) - ACE4_WRITE_OWNER (0x00080000) - ACE4_SYNCHRONIZE (0x00100000) Please see RFC 3010 for more information on the semantics of these values. File/Directory Attributes are specified using the following values: *FileType*: The type of file. Can be one of the following values: - SSH_FILEXFER_TYPE_REGULAR (1) - SSH_FILEXFER_TYPE_DIRECTORY (2) - SSH_FILEXFER_TYPE_SYMLINK (3) - SSH_FILEXFER_TYPE_SPECIAL (4) - SSH_FILEXFER_TYPE_UNKNOWN (5) - SSH_FILEXFER_TYPE_SOCKET (6) - SSH_FILEXFER_TYPE_CHAR_DEVICE (7) - SSH_FILEXFER_TYPE_BLOCK_DEVICE (8) - SSH_FILEXFER_TYPE_FIFO (9) *FileSize*: The file size, in bytes. *FileOwner*: The file owner. If the ProtocolVersion configuration option is "3" (default), this field should be a numeric Unix-like user identifier. V4, V5, and V6 of the secure file transfer protocol (SFTP) allow for an arbitrary string. *FileGroup*: The file owner group. If the ProtocolVersion configuration option is "3" (default), this field should be a numeric Unix-like group identifier. V4, V5, and V6 of the SFTP allow for an arbitrary string. *FilePermissions*: The POSIX-style file permissions. *FileATime*: The file last-access time, in milliseconds since January 1, 1970, in UTC. *FileCreateTime*: The file creation time, in milliseconds since January 1, 1970, in UTC. *FileMTime*: The file last-modified time, in milliseconds since January 1, 1970, in UTC. *FileAttrBits*: The file attributes, as a combination of the following values: - SSH_FILEXFER_ATTR_FLAGS_READONLY (0x00000001) - SSH_FILEXFER_ATTR_FLAGS_SYSTEM (0x00000002) - SSH_FILEXFER_ATTR_FLAGS_HIDDEN (0x00000004) - SSH_FILEXFER_ATTR_FLAGS_CASE_INSENSITIVE (0x00000008) - SSH_FILEXFER_ATTR_FLAGS_ARCHIVE (0x00000010) - SSH_FILEXFER_ATTR_FLAGS_ENCRYPTED (0x00000020) - SSH_FILEXFER_ATTR_FLAGS_COMPRESSED (0x00000040) - SSH_FILEXFER_ATTR_FLAGS_SPARSE (0x00000080) - SSH_FILEXFER_ATTR_FLAGS_APPEND_ONLY (0x00000100) - SSH_FILEXFER_ATTR_FLAGS_IMMUTABLE (0x00000200) - SSH_FILEXFER_ATTR_FLAGS_SYNC (0x00000400) - SSH_FILEXFER_ATTR_FLAGS_TRANSLATION_ERR (0x00000800) *FileAttrBitsValid*: A mask specifying which bits in *FileAttrBits* are supported by the server. *OtherAttributes*: A semicolon (;) delimited list of Name=Value pairs of other attributes supported by SFTP. These include the following: - MIMEType (String) - AllocationSize (64-bit int) - ATimeNS (int): ATime nanoseconds - CreateTimeNS (int): CreateTime nanoseconds - MTimeNS (int): MTime nanoseconds - TextHint (8-bit int) - LinkCount (int) - UntranslatedName (String) *FileMimeType*: The MIME type of the file. Valid status codes are as follows: - SSH_FX_OK 0 - SSH_FX_EOF 1 - SSH_FX_NO_SUCH_FILE 2 - SSH_FX_PERMISSION_DENIED 3 - SSH_FX_FAILURE 4 - SSH_FX_BAD_MESSAGE 5 - SSH_FX_NO_CONNECTION 6 - SSH_FX_CONNECTION_LOST 7 - SSH_FX_OP_UNSUPPORTED 8 - SSH_FX_INVALID_HANDLE 9 - SSH_FX_NO_SUCH_PATH 10 - SSH_FX_FILE_ALREADY_EXISTS 11 - SSH_FX_WRITE_PROTECT 12 - SSH_FX_NO_MEDIA 13 - SSH_FX_NO_SPACE_ON_FILESYSTEM 14 - SSH_FX_QUOTA_EXCEEDED 15 - SSH_FX_UNKNOWN_PRINCIPAL 16 - SSH_FX_LOCK_CONFLICT 17 - SSH_FX_DIR_NOT_EMPTY 18 - SSH_FX_NOT_A_DIRECTORY 19 - SSH_FX_INVALID_FILENAME 20 - SSH_FX_LINK_LOOP 21 - SSH_FX_CANNOT_DELETE 22 - SSH_FX_INVALID_PARAMETER 23 - SSH_FX_FILE_IS_A_DIRECTORY 24 - SSH_FX_BYTE_RANGE_LOCK_CONFLICT 25 - SSH_FX_BYTE_RANGE_LOCK_REFUSED 26 - SSH_FX_DELETE_PENDING 27 - SSH_FX_FILE_CORRUPT 28 - SSH_FX_OWNER_INVALID 29 - SSH_FX_GROUP_INVALID 30 - SSH_FX_NO_MATCHING_BYTE_RANGE_LOCK 31 # FileRead Event ([SFTPServer](#sftpserver-component) Component) Fired when a client wants to read from an open file. ## Syntax ```text public event OnFileReadHandler OnFileRead; public delegate void OnFileReadHandler(object sender, SFTPServerFileReadEventArgs e); public class SFTPServerFileReadEventArgs : EventArgs { public string ConnectionId { get; } public string User { get; } public string Handle { get; } public long FileOffset { get; } public int Length { get; } public int StatusCode { get; set; } } ``` ## Remarks The *Handle* parameter identifies an open file on the server. *FileOffset* specifies the position from which to read data. *Length* specifies how much data to read. The data read should be set to through [FileData](#SFTPConnection_f_FileData) When processing a read request, the server should attempt to read at most *Length* bytes, but it is okay to read less than *Length* bytes as well, if no more data are available. When there are no more data to be read from the file, set *StatusCode* to SSH_FXS_EOF. Valid status codes are as follows: - SSH_FX_OK 0 - SSH_FX_EOF 1 - SSH_FX_NO_SUCH_FILE 2 - SSH_FX_PERMISSION_DENIED 3 - SSH_FX_FAILURE 4 - SSH_FX_BAD_MESSAGE 5 - SSH_FX_NO_CONNECTION 6 - SSH_FX_CONNECTION_LOST 7 - SSH_FX_OP_UNSUPPORTED 8 - SSH_FX_INVALID_HANDLE 9 - SSH_FX_NO_SUCH_PATH 10 - SSH_FX_FILE_ALREADY_EXISTS 11 - SSH_FX_WRITE_PROTECT 12 - SSH_FX_NO_MEDIA 13 - SSH_FX_NO_SPACE_ON_FILESYSTEM 14 - SSH_FX_QUOTA_EXCEEDED 15 - SSH_FX_UNKNOWN_PRINCIPAL 16 - SSH_FX_LOCK_CONFLICT 17 - SSH_FX_DIR_NOT_EMPTY 18 - SSH_FX_NOT_A_DIRECTORY 19 - SSH_FX_INVALID_FILENAME 20 - SSH_FX_LINK_LOOP 21 - SSH_FX_CANNOT_DELETE 22 - SSH_FX_INVALID_PARAMETER 23 - SSH_FX_FILE_IS_A_DIRECTORY 24 - SSH_FX_BYTE_RANGE_LOCK_CONFLICT 25 - SSH_FX_BYTE_RANGE_LOCK_REFUSED 26 - SSH_FX_DELETE_PENDING 27 - SSH_FX_FILE_CORRUPT 28 - SSH_FX_OWNER_INVALID 29 - SSH_FX_GROUP_INVALID 30 - SSH_FX_NO_MATCHING_BYTE_RANGE_LOCK 31 # FileRemove Event ([SFTPServer](#sftpserver-component) Component) Fired when a client wants to delete a file. ## Syntax ```text public event OnFileRemoveHandler OnFileRemove; public delegate void OnFileRemoveHandler(object sender, SFTPServerFileRemoveEventArgs e); public class SFTPServerFileRemoveEventArgs : EventArgs { public string ConnectionId { get; } public string User { get; } public string Path { get; } public bool BeforeExec { get; } public int StatusCode { get; set; } } ``` ## Remarks The *Path* parameter will specify the file to delete. This event is fired both before and after the file is removed. The *BeforeExec* parameter is *True* before the operation has been executed and *False* otherwise. Handling this event before execution of the operation provides an opportunity to add custom logic that may prevent or deny the operation. Handling this event after execution of the operation provides an opportunity to report any errors that may have occurred during the operation. Valid status codes are as follows: - SSH_FX_OK 0 - SSH_FX_EOF 1 - SSH_FX_NO_SUCH_FILE 2 - SSH_FX_PERMISSION_DENIED 3 - SSH_FX_FAILURE 4 - SSH_FX_BAD_MESSAGE 5 - SSH_FX_NO_CONNECTION 6 - SSH_FX_CONNECTION_LOST 7 - SSH_FX_OP_UNSUPPORTED 8 - SSH_FX_INVALID_HANDLE 9 - SSH_FX_NO_SUCH_PATH 10 - SSH_FX_FILE_ALREADY_EXISTS 11 - SSH_FX_WRITE_PROTECT 12 - SSH_FX_NO_MEDIA 13 - SSH_FX_NO_SPACE_ON_FILESYSTEM 14 - SSH_FX_QUOTA_EXCEEDED 15 - SSH_FX_UNKNOWN_PRINCIPAL 16 - SSH_FX_LOCK_CONFLICT 17 - SSH_FX_DIR_NOT_EMPTY 18 - SSH_FX_NOT_A_DIRECTORY 19 - SSH_FX_INVALID_FILENAME 20 - SSH_FX_LINK_LOOP 21 - SSH_FX_CANNOT_DELETE 22 - SSH_FX_INVALID_PARAMETER 23 - SSH_FX_FILE_IS_A_DIRECTORY 24 - SSH_FX_BYTE_RANGE_LOCK_CONFLICT 25 - SSH_FX_BYTE_RANGE_LOCK_REFUSED 26 - SSH_FX_DELETE_PENDING 27 - SSH_FX_FILE_CORRUPT 28 - SSH_FX_OWNER_INVALID 29 - SSH_FX_GROUP_INVALID 30 - SSH_FX_NO_MATCHING_BYTE_RANGE_LOCK 31 # FileRename Event ([SFTPServer](#sftpserver-component) Component) Fired when a client wants to rename a file. ## Syntax ```text public event OnFileRenameHandler OnFileRename; public delegate void OnFileRenameHandler(object sender, SFTPServerFileRenameEventArgs e); public class SFTPServerFileRenameEventArgs : EventArgs { public string ConnectionId { get; } public string User { get; } public string Path { get; } public string NewPath { get; } public int Flags { get; } public bool BeforeExec { get; } public int StatusCode { get; set; } } ``` ## Remarks The *Path* parameter will specify the file to rename and *NewPath* will specify the new name. The *Flags* parameter will be a bit mask of the values SSH_FXF_RENAME_OVERWRITE (0x00000001), SSH_FXF_RENAME_ATOMIC (0x00000002), and SSH_FXF_RENAME_NATIVE (0x00000004). This event is fired both before and after the file is renamed. The *BeforeExec* parameter is *True* before the operation has been executed and *False* otherwise. Handling this event before execution of the operation provides an opportunity to add custom logic that may prevent or deny the operation. Handling this event after execution of the operation provides an opportunity to report any errors that may have occurred during the operation. Valid status codes are as follows: - SSH_FX_OK 0 - SSH_FX_EOF 1 - SSH_FX_NO_SUCH_FILE 2 - SSH_FX_PERMISSION_DENIED 3 - SSH_FX_FAILURE 4 - SSH_FX_BAD_MESSAGE 5 - SSH_FX_NO_CONNECTION 6 - SSH_FX_CONNECTION_LOST 7 - SSH_FX_OP_UNSUPPORTED 8 - SSH_FX_INVALID_HANDLE 9 - SSH_FX_NO_SUCH_PATH 10 - SSH_FX_FILE_ALREADY_EXISTS 11 - SSH_FX_WRITE_PROTECT 12 - SSH_FX_NO_MEDIA 13 - SSH_FX_NO_SPACE_ON_FILESYSTEM 14 - SSH_FX_QUOTA_EXCEEDED 15 - SSH_FX_UNKNOWN_PRINCIPAL 16 - SSH_FX_LOCK_CONFLICT 17 - SSH_FX_DIR_NOT_EMPTY 18 - SSH_FX_NOT_A_DIRECTORY 19 - SSH_FX_INVALID_FILENAME 20 - SSH_FX_LINK_LOOP 21 - SSH_FX_CANNOT_DELETE 22 - SSH_FX_INVALID_PARAMETER 23 - SSH_FX_FILE_IS_A_DIRECTORY 24 - SSH_FX_BYTE_RANGE_LOCK_CONFLICT 25 - SSH_FX_BYTE_RANGE_LOCK_REFUSED 26 - SSH_FX_DELETE_PENDING 27 - SSH_FX_FILE_CORRUPT 28 - SSH_FX_OWNER_INVALID 29 - SSH_FX_GROUP_INVALID 30 - SSH_FX_NO_MATCHING_BYTE_RANGE_LOCK 31 # FileWrite Event ([SFTPServer](#sftpserver-component) Component) Fired when a client wants to write to an open file. ## Syntax ```text public event OnFileWriteHandler OnFileWrite; public delegate void OnFileWriteHandler(object sender, SFTPServerFileWriteEventArgs e); public class SFTPServerFileWriteEventArgs : EventArgs { public string ConnectionId { get; } public string User { get; } public string Handle { get; } public long FileOffset { get; } public bool BeforeExec { get; } public int StatusCode { get; set; } } ``` ## Remarks The *Handle* parameter identifies an open file on the server. *FileOffset* specifies the position at which to write data. The data to write can be retrieved through [FileData](#SFTPConnection_f_FileData) This event is fired both before and after the file is written. The *BeforeExec* parameter is *True* before the operation has been executed and *False* otherwise. Handling this event before execution of the operation provides an opportunity to add custom logic that may prevent or deny the operation. Handling this event after execution of the operation provides an opportunity to report any errors that may have occurred during the operation. Valid status codes are as follows: - SSH_FX_OK 0 - SSH_FX_EOF 1 - SSH_FX_NO_SUCH_FILE 2 - SSH_FX_PERMISSION_DENIED 3 - SSH_FX_FAILURE 4 - SSH_FX_BAD_MESSAGE 5 - SSH_FX_NO_CONNECTION 6 - SSH_FX_CONNECTION_LOST 7 - SSH_FX_OP_UNSUPPORTED 8 - SSH_FX_INVALID_HANDLE 9 - SSH_FX_NO_SUCH_PATH 10 - SSH_FX_FILE_ALREADY_EXISTS 11 - SSH_FX_WRITE_PROTECT 12 - SSH_FX_NO_MEDIA 13 - SSH_FX_NO_SPACE_ON_FILESYSTEM 14 - SSH_FX_QUOTA_EXCEEDED 15 - SSH_FX_UNKNOWN_PRINCIPAL 16 - SSH_FX_LOCK_CONFLICT 17 - SSH_FX_DIR_NOT_EMPTY 18 - SSH_FX_NOT_A_DIRECTORY 19 - SSH_FX_INVALID_FILENAME 20 - SSH_FX_LINK_LOOP 21 - SSH_FX_CANNOT_DELETE 22 - SSH_FX_INVALID_PARAMETER 23 - SSH_FX_FILE_IS_A_DIRECTORY 24 - SSH_FX_BYTE_RANGE_LOCK_CONFLICT 25 - SSH_FX_BYTE_RANGE_LOCK_REFUSED 26 - SSH_FX_DELETE_PENDING 27 - SSH_FX_FILE_CORRUPT 28 - SSH_FX_OWNER_INVALID 29 - SSH_FX_GROUP_INVALID 30 - SSH_FX_NO_MATCHING_BYTE_RANGE_LOCK 31 # GetAttributes Event ([SFTPServer](#sftpserver-component) Component) Fired when a client needs to get file information. ## Syntax ```text public event OnGetAttributesHandler OnGetAttributes; public delegate void OnGetAttributesHandler(object sender, SFTPServerGetAttributesEventArgs e); public class SFTPServerGetAttributesEventArgs : EventArgs { public string ConnectionId { get; } public string User { get; } public string Path { get; } public int Flags { get; } public int FileType { get; set; } public long FileSize { get; set; } public string FileOwner { get; set; } public string FileGroup { get; set; } public int FilePermissions { get; set; } public long FileATime { get; set; } public long FileCreateTime { get; set; } public long FileMTime { get; set; } public int FileAttribBits { get; set; } public int FileAttribBitsValid { get; set; } public string OtherAttributes { get; set; } public int StatusCode { get; set; } } ``` ## Remarks The GetAttributes event fires when a secure file transfer protocol (SFTP) client sends an SSH_FXP_STAT, SSH_FXP_LSTAT, or SSH_FXP_FSTAT request. *Path* is the file path. *Flags* specifies the set of file attributes the client is interested in. File/Directory Attributes are specified using the following values: *FileType*: The type of file. Can be one of the following values: - SSH_FILEXFER_TYPE_REGULAR (1) - SSH_FILEXFER_TYPE_DIRECTORY (2) - SSH_FILEXFER_TYPE_SYMLINK (3) - SSH_FILEXFER_TYPE_SPECIAL (4) - SSH_FILEXFER_TYPE_UNKNOWN (5) - SSH_FILEXFER_TYPE_SOCKET (6) - SSH_FILEXFER_TYPE_CHAR_DEVICE (7) - SSH_FILEXFER_TYPE_BLOCK_DEVICE (8) - SSH_FILEXFER_TYPE_FIFO (9) *FileSize*: The file size, in bytes. *FileOwner*: The file owner. If the ProtocolVersion configuration option is "3" (default), this field should be a numeric Unix-like user identifier. V4, V5, and V6 of the secure file transfer protocol (SFTP) allow for an arbitrary string. *FileGroup*: The file owner group. If the ProtocolVersion configuration option is "3" (default), this field should be a numeric Unix-like group identifier. V4, V5, and V6 of the SFTP allow for an arbitrary string. *FilePermissions*: The POSIX-style file permissions. *FileATime*: The file last-access time, in milliseconds since January 1, 1970, in UTC. *FileCreateTime*: The file creation time, in milliseconds since January 1, 1970, in UTC. *FileMTime*: The file last-modified time, in milliseconds since January 1, 1970, in UTC. *FileAttrBits*: The file attributes, as a combination of the following values: - SSH_FILEXFER_ATTR_FLAGS_READONLY (0x00000001) - SSH_FILEXFER_ATTR_FLAGS_SYSTEM (0x00000002) - SSH_FILEXFER_ATTR_FLAGS_HIDDEN (0x00000004) - SSH_FILEXFER_ATTR_FLAGS_CASE_INSENSITIVE (0x00000008) - SSH_FILEXFER_ATTR_FLAGS_ARCHIVE (0x00000010) - SSH_FILEXFER_ATTR_FLAGS_ENCRYPTED (0x00000020) - SSH_FILEXFER_ATTR_FLAGS_COMPRESSED (0x00000040) - SSH_FILEXFER_ATTR_FLAGS_SPARSE (0x00000080) - SSH_FILEXFER_ATTR_FLAGS_APPEND_ONLY (0x00000100) - SSH_FILEXFER_ATTR_FLAGS_IMMUTABLE (0x00000200) - SSH_FILEXFER_ATTR_FLAGS_SYNC (0x00000400) - SSH_FILEXFER_ATTR_FLAGS_TRANSLATION_ERR (0x00000800) *FileAttrBitsValid*: A mask specifying which bits in *FileAttrBits* are supported by the server. *OtherAttributes*: A semicolon (;) delimited list of Name=Value pairs of other attributes supported by SFTP. These include the following: - MIMEType (String) - AllocationSize (64-bit int) - ATimeNS (int): ATime nanoseconds - CreateTimeNS (int): CreateTime nanoseconds - MTimeNS (int): MTime nanoseconds - TextHint (8-bit int) - LinkCount (int) - UntranslatedName (String) *FileMimeType*: The MIME type of the file. Valid status codes are as follows: - SSH_FX_OK 0 - SSH_FX_EOF 1 - SSH_FX_NO_SUCH_FILE 2 - SSH_FX_PERMISSION_DENIED 3 - SSH_FX_FAILURE 4 - SSH_FX_BAD_MESSAGE 5 - SSH_FX_NO_CONNECTION 6 - SSH_FX_CONNECTION_LOST 7 - SSH_FX_OP_UNSUPPORTED 8 - SSH_FX_INVALID_HANDLE 9 - SSH_FX_NO_SUCH_PATH 10 - SSH_FX_FILE_ALREADY_EXISTS 11 - SSH_FX_WRITE_PROTECT 12 - SSH_FX_NO_MEDIA 13 - SSH_FX_NO_SPACE_ON_FILESYSTEM 14 - SSH_FX_QUOTA_EXCEEDED 15 - SSH_FX_UNKNOWN_PRINCIPAL 16 - SSH_FX_LOCK_CONFLICT 17 - SSH_FX_DIR_NOT_EMPTY 18 - SSH_FX_NOT_A_DIRECTORY 19 - SSH_FX_INVALID_FILENAME 20 - SSH_FX_LINK_LOOP 21 - SSH_FX_CANNOT_DELETE 22 - SSH_FX_INVALID_PARAMETER 23 - SSH_FX_FILE_IS_A_DIRECTORY 24 - SSH_FX_BYTE_RANGE_LOCK_CONFLICT 25 - SSH_FX_BYTE_RANGE_LOCK_REFUSED 26 - SSH_FX_DELETE_PENDING 27 - SSH_FX_FILE_CORRUPT 28 - SSH_FX_OWNER_INVALID 29 - SSH_FX_GROUP_INVALID 30 - SSH_FX_NO_MATCHING_BYTE_RANGE_LOCK 31 # Log Event ([SFTPServer](#sftpserver-component) Component) Fired once for each log message. ## Syntax ```text public event OnLogHandler OnLog; public delegate void OnLogHandler(object sender, SFTPServerLogEventArgs e); public class SFTPServerLogEventArgs : EventArgs { public string ConnectionId { get; } public int LogLevel { get; } public string Message { get; } public string LogType { get; } } ``` ## Remarks Fired once for each log message generated by the component. The verbosity is controlled by the [LogLevel](#LogLevel) setting. *LogLevel* indicates the detail level of the message. Possible values are as follows: | | | | --- | --- | | 0 (None) | No messages are logged. | | 1 (Info - Default) | Informational events such as Secure Shell (SSH) handshake messages are logged. | | 2 (Verbose) | Detailed data such as individual packet information are logged. | | 3 (Debug) | Debug data including all relevant sent and received bytes are logged. | *Message* is the log message. *LogType* is reserved for future use. *ConnectionId* identifies the connection to which the log message applies. # ResolvePath Event ([SFTPServer](#sftpserver-component) Component) Fired when a client attempts to canonicalize a path. ## Syntax ```text public event OnResolvePathHandler OnResolvePath; public delegate void OnResolvePathHandler(object sender, SFTPServerResolvePathEventArgs e); public class SFTPServerResolvePathEventArgs : EventArgs { public string ConnectionId { get; } public string User { get; } public string OriginalPath { get; } public int ControlFlags { get; } public string RealPath { get; set; } public int StatusCode { get; set; } } ``` ## Remarks The ResolvePath event is fired when a secure file transfer protocol (SFTP) client sends an SSH_FXP_REALPATH request. The *OriginalPath* parameter will contain the path the client wants to canonicalize. *ControlFlags* can have one of the following values: | | | | --- | --- | | SSH_FXP_REALPATH_NO_CHECK (0x00000001) | Server should not check if the path exists. | | SSH_FXP_REALPATH_STAT_IF (0x00000002) | Server should return the file/directory attributes if the path exists and is accessible, but otherwise should not fail. | | SSH_FXP_REALPATH_STAT_ALWAYS (0x00000003) | Server should return the file/directory attributes if the path exists and is accessible, but otherwise will fail with an error. | *RealPath* should be set to the resulting canonicalized path, and *StatusCode* should be set to indicate the success or failure of the operation to the client. Valid status codes are as follows: - SSH_FX_OK 0 - SSH_FX_EOF 1 - SSH_FX_NO_SUCH_FILE 2 - SSH_FX_PERMISSION_DENIED 3 - SSH_FX_FAILURE 4 - SSH_FX_BAD_MESSAGE 5 - SSH_FX_NO_CONNECTION 6 - SSH_FX_CONNECTION_LOST 7 - SSH_FX_OP_UNSUPPORTED 8 - SSH_FX_INVALID_HANDLE 9 - SSH_FX_NO_SUCH_PATH 10 - SSH_FX_FILE_ALREADY_EXISTS 11 - SSH_FX_WRITE_PROTECT 12 - SSH_FX_NO_MEDIA 13 - SSH_FX_NO_SPACE_ON_FILESYSTEM 14 - SSH_FX_QUOTA_EXCEEDED 15 - SSH_FX_UNKNOWN_PRINCIPAL 16 - SSH_FX_LOCK_CONFLICT 17 - SSH_FX_DIR_NOT_EMPTY 18 - SSH_FX_NOT_A_DIRECTORY 19 - SSH_FX_INVALID_FILENAME 20 - SSH_FX_LINK_LOOP 21 - SSH_FX_CANNOT_DELETE 22 - SSH_FX_INVALID_PARAMETER 23 - SSH_FX_FILE_IS_A_DIRECTORY 24 - SSH_FX_BYTE_RANGE_LOCK_CONFLICT 25 - SSH_FX_BYTE_RANGE_LOCK_REFUSED 26 - SSH_FX_DELETE_PENDING 27 - SSH_FX_FILE_CORRUPT 28 - SSH_FX_OWNER_INVALID 29 - SSH_FX_GROUP_INVALID 30 - SSH_FX_NO_MATCHING_BYTE_RANGE_LOCK 31 # SetAttributes Event ([SFTPServer](#sftpserver-component) Component) Fired when a client attempts to set file or directory attributes. ## Syntax ```text public event OnSetAttributesHandler OnSetAttributes; public delegate void OnSetAttributesHandler(object sender, SFTPServerSetAttributesEventArgs e); public class SFTPServerSetAttributesEventArgs : EventArgs { public string ConnectionId { get; } public string User { get; } public string Path { get; } public int FileType { get; } public long FileSize { get; } public string FileOwner { get; } public string FileGroup { get; } public int FilePermissions { get; } public long FileATime { get; } public long FileCreateTime { get; } public long FileMTime { get; } public int FileAttribBits { get; } public int FileAttribBitsValid { get; } public string OtherAttributes { get; } public bool BeforeExec { get; } public int StatusCode { get; set; } } ``` ## Remarks The SetAttributes event is fired when a secure file transfer protocol (SFTP) client sends an SSH_FXP_SETSTAT, SSH_FXP_FSETSTAT, or SSH_FXP_FSTAT request. *Path* is the path of the file or directory the client wants to set attributes for. This event is fired both before and after the attributes are set. The *BeforeExec* parameter is *True* before the operation has been executed and *False* otherwise. Handling this event before execution of the operation provides an opportunity to add custom logic that may prevent or deny the operation. Handling this event after execution of the operation provides an opportunity to report any errors that may have occurred during the operation. File/Directory Attributes are specified using the following values: *FileType*: The type of file. Can be one of the following values: - SSH_FILEXFER_TYPE_REGULAR (1) - SSH_FILEXFER_TYPE_DIRECTORY (2) - SSH_FILEXFER_TYPE_SYMLINK (3) - SSH_FILEXFER_TYPE_SPECIAL (4) - SSH_FILEXFER_TYPE_UNKNOWN (5) - SSH_FILEXFER_TYPE_SOCKET (6) - SSH_FILEXFER_TYPE_CHAR_DEVICE (7) - SSH_FILEXFER_TYPE_BLOCK_DEVICE (8) - SSH_FILEXFER_TYPE_FIFO (9) *FileSize*: The file size, in bytes. *FileOwner*: The file owner. If the ProtocolVersion configuration option is "3" (default), this field should be a numeric Unix-like user identifier. V4, V5, and V6 of the secure file transfer protocol (SFTP) allow for an arbitrary string. *FileGroup*: The file owner group. If the ProtocolVersion configuration option is "3" (default), this field should be a numeric Unix-like group identifier. V4, V5, and V6 of the SFTP allow for an arbitrary string. *FilePermissions*: The POSIX-style file permissions. *FileATime*: The file last-access time, in milliseconds since January 1, 1970, in UTC. *FileCreateTime*: The file creation time, in milliseconds since January 1, 1970, in UTC. *FileMTime*: The file last-modified time, in milliseconds since January 1, 1970, in UTC. *FileAttrBits*: The file attributes, as a combination of the following values: - SSH_FILEXFER_ATTR_FLAGS_READONLY (0x00000001) - SSH_FILEXFER_ATTR_FLAGS_SYSTEM (0x00000002) - SSH_FILEXFER_ATTR_FLAGS_HIDDEN (0x00000004) - SSH_FILEXFER_ATTR_FLAGS_CASE_INSENSITIVE (0x00000008) - SSH_FILEXFER_ATTR_FLAGS_ARCHIVE (0x00000010) - SSH_FILEXFER_ATTR_FLAGS_ENCRYPTED (0x00000020) - SSH_FILEXFER_ATTR_FLAGS_COMPRESSED (0x00000040) - SSH_FILEXFER_ATTR_FLAGS_SPARSE (0x00000080) - SSH_FILEXFER_ATTR_FLAGS_APPEND_ONLY (0x00000100) - SSH_FILEXFER_ATTR_FLAGS_IMMUTABLE (0x00000200) - SSH_FILEXFER_ATTR_FLAGS_SYNC (0x00000400) - SSH_FILEXFER_ATTR_FLAGS_TRANSLATION_ERR (0x00000800) *FileAttrBitsValid*: A mask specifying which bits in *FileAttrBits* are supported by the server. *OtherAttributes*: A semicolon (;) delimited list of Name=Value pairs of other attributes supported by SFTP. These include the following: - MIMEType (String) - AllocationSize (64-bit int) - ATimeNS (int): ATime nanoseconds - CreateTimeNS (int): CreateTime nanoseconds - MTimeNS (int): MTime nanoseconds - TextHint (8-bit int) - LinkCount (int) - UntranslatedName (String) *FileMimeType*: The MIME type of the file. Valid status codes are as follows: - SSH_FX_OK 0 - SSH_FX_EOF 1 - SSH_FX_NO_SUCH_FILE 2 - SSH_FX_PERMISSION_DENIED 3 - SSH_FX_FAILURE 4 - SSH_FX_BAD_MESSAGE 5 - SSH_FX_NO_CONNECTION 6 - SSH_FX_CONNECTION_LOST 7 - SSH_FX_OP_UNSUPPORTED 8 - SSH_FX_INVALID_HANDLE 9 - SSH_FX_NO_SUCH_PATH 10 - SSH_FX_FILE_ALREADY_EXISTS 11 - SSH_FX_WRITE_PROTECT 12 - SSH_FX_NO_MEDIA 13 - SSH_FX_NO_SPACE_ON_FILESYSTEM 14 - SSH_FX_QUOTA_EXCEEDED 15 - SSH_FX_UNKNOWN_PRINCIPAL 16 - SSH_FX_LOCK_CONFLICT 17 - SSH_FX_DIR_NOT_EMPTY 18 - SSH_FX_NOT_A_DIRECTORY 19 - SSH_FX_INVALID_FILENAME 20 - SSH_FX_LINK_LOOP 21 - SSH_FX_CANNOT_DELETE 22 - SSH_FX_INVALID_PARAMETER 23 - SSH_FX_FILE_IS_A_DIRECTORY 24 - SSH_FX_BYTE_RANGE_LOCK_CONFLICT 25 - SSH_FX_BYTE_RANGE_LOCK_REFUSED 26 - SSH_FX_DELETE_PENDING 27 - SSH_FX_FILE_CORRUPT 28 - SSH_FX_OWNER_INVALID 29 - SSH_FX_GROUP_INVALID 30 - SSH_FX_NO_MATCHING_BYTE_RANGE_LOCK 31 # SSHStatus Event ([SFTPServer](#sftpserver-component) Component) Fired to track the progress of the secure connection. ## Syntax ```text public event OnSSHStatusHandler OnSSHStatus; public delegate void OnSSHStatusHandler(object sender, SFTPServerSSHStatusEventArgs e); public class SFTPServerSSHStatusEventArgs : EventArgs { public string ConnectionId { get; } public string Message { get; } } ``` ## Remarks This event is fired for informational and logging purposes only and is used to track the progress of the connection. # SSHUserAuthRequest Event ([SFTPServer](#sftpserver-component) Component) Fired when a client attempts to authenticate a connection. ## Syntax ```text public event OnSSHUserAuthRequestHandler OnSSHUserAuthRequest; public delegate void OnSSHUserAuthRequestHandler(object sender, SFTPServerSSHUserAuthRequestEventArgs e); public class SFTPServerSSHUserAuthRequestEventArgs : EventArgs { public string ConnectionId { get; } public string User { get; } public string Service { get; } public string AuthMethod { get; } public string AuthParam { get; } public bool Accept { get; set; } public bool PartialSuccess { get; set; } public string AvailableMethods { get; set; } public string HomeDir { get; set; } public string KeyAlgorithm { get; } } ``` ## Remarks The SSHUserAuthRequest event fires when a Secure Shell (SSH) client attempts to authenticate itself on a particular connection. *ConnectionId* will identify the connection being authenticated. *User* will be the name of the account requesting authentication, and *Service* will contain the name of the service the client is wishing to access. *AuthMethod* will denote which method the client is attempting to use to authenticate itself. *AuthParam* will contain the value of the authentication token used by the client. If the token is acceptable, you may set *Accept* to True to allow the SFTPServer to authenticate the client. If it is not, set *Accept* to False. Connecting clients will initially attempt authentication with an *AuthMethod* of "none". This is done with the expectation that the request will fail and the server will send a list of supported methods back to the client. In your implementation, check the *AuthMethod* parameter; if it is "none", you should set *AvailableMethods* and reject the request. The client will select one of the available methods and reauthenticate. You may set *AvailableMethods* to a comma-delimited string of authentication methods that are available for the user. This list will be sent back to the client so that it may perform further authentication attempts. The following is a list of methods implemented by the component: | | | | --- | --- | | none | This authentication method is used by most Secure Shell (SSH) clients to obtain the list of authentication methods available for the user's account. In most cases, you should not accept a request using this authentication method. | | password | AuthParam will contain the user-supplied password. If the password is correct, set Accept to True. | | publickey | AuthParam will contain an SSH2 public key blob. If the user's public key is acceptable, set Accept or PartialSuccess to true. The component will then handle verifying the digital signature and will respond to the client accordingly. | | keyboard-interactive | SSHUserAuthRequest will fire multiple times for keyboard-interactive authentication: It will fire once for each response sent by the client in the SSH_MSG_USERAUTH_INFO_RESPONSE packet (one time for each prompt specified by the daemon). The index of each response will be specified as a suffix in AuthMethod, with AuthParam containing the response to the corresponding prompt (e.g., keyboard-interactive-1, keyboard-interactive-2, and so on). Finally, SSHUserAuthRequest will fire one last time with AuthMethod set to "keyboard-interactive" and AuthParam set to an empty string. The daemon must set Accept to True every time to allow the authentication process to succeed. | If the user authentication succeeds, you may set *HomeDir* to the virtual path representing the initial directory for the user. If not set, the initial directory will be [RootDirectory](#rootdirectory-property-sftpserver-component). The *PartialSuccess* parameter is used only when multifactor authentication is needed. To implement multifactor authentication when this event fires, first verify the *AuthParam* for the given *AuthMethod*. If accepted, set *PartialSuccess* to True and *Accept* to False. The client should then send the authentication request for a different form of authentication specified in *AvailableMethods*. You may continue to set *PartialSuccess* to True until all authentication requirements are satisfied. Once all requirements are satisfied set *Accept* to True. *KeyAlgorithm* holds the signing algorithm used when the client attempts public key authentication. Possible values are as follows: - ssh-rsa - rsa-sha2-256 - rsa-sha2-512 - ssh-dss - ecdsa-sha2-nistp256 - ecdsa-sha2-nistp384 - ecdsa-sha2-nistp521 - x509v3-sign-rsa - x509v3-sign-dss NOTE: Processing long-running requests, including sending channel data, inside this event may cause the underlying transport to stop processing Secure Shell (SSH) data until the event returns. To prevent this from happening, all requests should be processed asynchronously in a separate thread outside of this event. # Certificate Type This is the digital certificate being used. ## Remarks This type describes the current digital certificate. The certificate may be a public or private key. The fields are used to identify or select certificates. The following fields are available: - [EffectiveDate](#Certificate_f_EffectiveDate) - [ExpirationDate](#Certificate_f_ExpirationDate) - [ExtendedKeyUsage](#Certificate_f_ExtendedKeyUsage) - [Fingerprint](#Certificate_f_Fingerprint) - [FingerprintSHA1](#Certificate_f_FingerprintSHA1) - [FingerprintSHA256](#Certificate_f_FingerprintSHA256) - [Issuer](#Certificate_f_Issuer) - [PrivateKey](#Certificate_f_PrivateKey) - [PrivateKeyAvailable](#Certificate_f_PrivateKeyAvailable) - [PrivateKeyContainer](#Certificate_f_PrivateKeyContainer) - [PublicKey](#Certificate_f_PublicKey) - [PublicKeyAlgorithm](#Certificate_f_PublicKeyAlgorithm) - [PublicKeyLength](#Certificate_f_PublicKeyLength) - [SerialNumber](#Certificate_f_SerialNumber) - [SignatureAlgorithm](#Certificate_f_SignatureAlgorithm) - [Store](#Certificate_f_Store) - [StorePassword](#Certificate_f_StorePassword) - [StoreType](#Certificate_f_StoreType) - [SubjectAltNames](#Certificate_f_SubjectAltNames) - [ThumbprintMD5](#Certificate_f_ThumbprintMD5) - [ThumbprintSHA1](#Certificate_f_ThumbprintSHA1) - [ThumbprintSHA256](#Certificate_f_ThumbprintSHA256) - [Usage](#Certificate_f_Usage) - [UsageFlags](#Certificate_f_UsageFlags) - [Version](#Certificate_f_Version) - [Subject](#Certificate_f_Subject) - [Encoded](#Certificate_f_Encoded) ## Fields **EffectiveDate** *string (read-only)* Default: "" The date on which this certificate becomes valid. Before this date, it is not valid. The date is localized to the system's time zone. The following example illustrates the format of an encoded date: 23-Jan-2000 15:00:00. **ExpirationDate** *string (read-only)* Default: "" The date on which the certificate expires. After this date, the certificate will no longer be valid. The date is localized to the system's time zone. The following example illustrates the format of an encoded date: 23-Jan-2001 15:00:00. **ExtendedKeyUsage** *string (read-only)* Default: "" A comma-delimited list of extended key usage identifiers. These are the same as ASN.1 object identifiers (OIDs). **Fingerprint** *string (read-only)* Default: "" The hex-encoded, 16-byte MD5 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys. The following example illustrates the format: *bc:2a:72:af:fe:58:17:43:7a:5f:ba:5a:7c:90:f7:02* **FingerprintSHA1** *string (read-only)* Default: "" The hex-encoded, 20-byte SHA-1 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys. The following example illustrates the format: *30:7b:fa:38:65:83:ff:da:b4:4e:07:3f:17:b8:a4:ed:80:be:ff:84* **FingerprintSHA256** *string (read-only)* Default: "" The hex-encoded, 32-byte SHA-256 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys. The following example illustrates the format: *6a:80:5c:33:a9:43:ea:b0:96:12:8a:64:96:30:ef:4a:8a:96:86:ce:f4:c7:be:10:24:8e:2b:60:9e:f3:59:53* **Issuer** *string (read-only)* Default: "" The issuer of the certificate. This field contains a string representation of the name of the issuing authority for the certificate. **PrivateKey** *string (read-only)* Default: "" The private key of the certificate (if available). The key is provided as PEM/Base64-encoded data. NOTE: The [PrivateKey](#Certificate_f_PrivateKey) may be available but not exportable. In this case, [PrivateKey](#Certificate_f_PrivateKey) returns an empty string. **PrivateKeyAvailable** *bool (read-only)* Default: False Whether a [PrivateKey](#Certificate_f_PrivateKey) is available for the selected certificate. If [PrivateKeyAvailable](#Certificate_f_PrivateKeyAvailable) is True, the certificate may be used for authentication purposes (e.g., server authentication). **PrivateKeyContainer** *string (read-only)* Default: "" The name of the [PrivateKey](#Certificate_f_PrivateKey) container for the certificate (if available). This functionality is available only on Windows platforms. **PublicKey** *string (read-only)* Default: "" The public key of the certificate. The key is provided as PEM/Base64-encoded data. **PublicKeyAlgorithm** *string (read-only)* Default: "" The textual description of the certificate's public key algorithm. The property contains either the name of the algorithm (e.g., "RSA" or "RSA_DH") or an object identifier (OID) string representing the algorithm. **PublicKeyLength** *int (read-only)* Default: 0 The length of the certificate's public key (in bits). Common values are 512, 1024, and 2048. **SerialNumber** *string (read-only)* Default: "" The serial number of the certificate encoded as a string. The number is encoded as a series of hexadecimal digits, with each pair representing a byte of the serial number. **SignatureAlgorithm** *string (read-only)* Default: "" The text description of the certificate's signature algorithm. The property contains either the name of the algorithm (e.g., "RSA" or "RSA_MD5RSA") or an object identifier (OID) string representing the algorithm. **Store** *string* Default: "MY" The name of the certificate store for the client certificate. The [StoreType](#Certificate_f_StoreType) field denotes the type of the certificate store specified by [Store](#Certificate_f_Store). If the store is password-protected, specify the password in [StorePassword](#Certificate_f_StorePassword). [Store](#Certificate_f_Store) is used in conjunction with the [Subject](#Certificate_f_Subject) field to specify client certificates. If [Store](#Certificate_f_Store) has a value, and [Subject](#Certificate_f_Subject) or [Encoded](#Certificate_f_Encoded) is set, a search for a certificate is initiated. Please see the [Subject](#Certificate_f_Subject) field for details. Designations of certificate stores are platform dependent. The following designations are the most common User and Machine certificate stores in Windows: | | | | --- | --- | | MY | A certificate store holding personal certificates with their associated private keys. | | CA | Certifying authority certificates. | | ROOT | Root certificates. | When the certificate store type is *cstPFXFile*, this property must be set to the name of the file. When the type is *cstPFXBlob*, the property must be set to the binary contents of a PFX file (i.e., PKCS#12 certificate store). **StoreB** *byte []* Default: "MY" The name of the certificate store for the client certificate. The [StoreType](#Certificate_f_StoreType) field denotes the type of the certificate store specified by [Store](#Certificate_f_Store). If the store is password-protected, specify the password in [StorePassword](#Certificate_f_StorePassword). [Store](#Certificate_f_Store) is used in conjunction with the [Subject](#Certificate_f_Subject) field to specify client certificates. If [Store](#Certificate_f_Store) has a value, and [Subject](#Certificate_f_Subject) or [Encoded](#Certificate_f_Encoded) is set, a search for a certificate is initiated. Please see the [Subject](#Certificate_f_Subject) field for details. Designations of certificate stores are platform dependent. The following designations are the most common User and Machine certificate stores in Windows: | | | | --- | --- | | MY | A certificate store holding personal certificates with their associated private keys. | | CA | Certifying authority certificates. | | ROOT | Root certificates. | When the certificate store type is *cstPFXFile*, this property must be set to the name of the file. When the type is *cstPFXBlob*, the property must be set to the binary contents of a PFX file (i.e., PKCS#12 certificate store). **StorePassword** *string* Default: "" If the type of certificate store requires a password, this field is used to specify the password needed to open the certificate store. **StoreType** *CertStoreTypes* Default: 0 The type of certificate store for this certificate. The component supports both public and private keys in a variety of formats. When the *cstAuto* value is used, the component will automatically determine the type. This field can take one of the following values: ```csharp sftp.SSHCert = new Certificate(CertStoreTypes.cstPKCS11, @"C:\Program Files\OpenSC Project\OpenSC\pkcs11\opensc-pkcs11.dll", "123456", // PIN "CN=cert_subject"); sftp.SSHUser = "test"; sftp.SSHLogon("myhost", 22); ``` ```csharp certmgr.CertStoreType = CertStoreTypes.cstPKCS11; certmgr.OnCertList += (s, e) => { secKeyBlob = e.CertEncoded; }; certmgr.CertStore = @"C:\Program Files\OpenSC Project\OpenSC\pkcs11\opensc-pkcs11.dll"; certmgr.CertStorePassword = "123456"; // PIN certmgr.ListStoreCertificates(); sftp.SSHCert = new Certificate(CertStoreTypes.cstPKCS11, secKeyBlob, "123456", "*"); sftp.SSHUser = "test"; sftp.SSHLogon("myhost", 22); ``` | | | | --- | --- | | 0 (cstUser - default) | For Windows, this specifies that the certificate store is a certificate store owned by the current user. NOTE: This store type is not available in Java. | | 1 (cstMachine) | For Windows, this specifies that the certificate store is a machine store. NOTE: This store type is not available in Java. | | 2 (cstPFXFile) | The certificate store is the name of a PFX (PKCS#12) file containing certificates. | | 3 (cstPFXBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in PFX (PKCS#12) format. | | 4 (cstJKSFile) | The certificate store is the name of a Java Key Store (JKS) file containing certificates. NOTE: This store type is only available in Java. | | 5 (cstJKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in Java Key Store (JKS) format. NOTE: This store type is only available in Java. | | 6 (cstPEMKeyFile) | The certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate. | | 7 (cstPEMKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a private key and an optional certificate. | | 8 (cstPublicKeyFile) | The certificate store is the name of a file that contains a PEM- or DER-encoded public key certificate. | | 9 (cstPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a PEM- or DER-encoded public key certificate. | | 10 (cstSSHPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains an SSH-style public key. | | 11 (cstP7BFile) | The certificate store is the name of a PKCS#7 file containing certificates. | | 12 (cstP7BBlob) | The certificate store is a string (binary) representing a certificate store in PKCS#7 format. | | 13 (cstSSHPublicKeyFile) | The certificate store is the name of a file that contains an SSH-style public key. | | 14 (cstPPKFile) | The certificate store is the name of a file that contains a PPK (PuTTY Private Key). | | 15 (cstPPKBlob) | The certificate store is a string (binary) that contains a PPK (PuTTY Private Key). | | 16 (cstXMLFile) | The certificate store is the name of a file that contains a certificate in XML format. | | 17 (cstXMLBlob) | The certificate store is a string that contains a certificate in XML format. | | 18 (cstJWKFile) | The certificate store is the name of a file that contains a JWK (JSON Web Key). | | 19 (cstJWKBlob) | The certificate store is a string that contains a JWK (JSON Web Key). | | 21 (cstBCFKSFile) | The certificate store is the name of a file that contains a BCFKS (Bouncy Castle FIPS Key Store). NOTE: This store type is only available in Java and .NET. | | 22 (cstBCFKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in BCFKS (Bouncy Castle FIPS Key Store) format. NOTE: This store type is only available in Java and .NET. | | 23 (cstPKCS11) | The certificate is present on a physical security key accessible via a PKCS#11 interface. To use a security key, create a new [Certificate](#certificate-type) object and pass cstPKCS11 as the [StoreType](#Certificate_f_StoreType), the full path of the PKCS#11 DLL as the [Store](#Certificate_f_Store), and the PIN as the [StorePassword](#Certificate_f_StorePassword). Code Example. SSH Authentication with Security Key (without CertMgr): Alternatively, collect the necessary data using the [CertMgr](CertMgr.md#CertMgr) component by calling the [ListStoreCertificates](CertMgr.md#CertMgr_m_ListStoreCertificates) method after setting the corresponding properties accordingly. The certificate information returned in the [CertList](CertMgr.md#CertMgr_e_CertList) event's CertEncoded parameter may be saved for later use. When using a certificate obtained with this approach, pass the previously saved security key information as the [Store](#Certificate_f_Store) and set [StorePassword](#Certificate_f_StorePassword) to the PIN. Code Example. SSH Authentication with Security Key (with CertMgr): | | 99 (cstAuto) | The store type is automatically detected from the input data. This setting may be used with both public and private keys and can detect any of the supported formats automatically. | **SubjectAltNames** *string (read-only)* Default: "" Comma-separated lists of alternative subject names for the certificate. **ThumbprintMD5** *string (read-only)* Default: "" The MD5 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed. **ThumbprintSHA1** *string (read-only)* Default: "" The SHA-1 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed. **ThumbprintSHA256** *string (read-only)* Default: "" The SHA-256 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed. **Usage** *string (read-only)* Default: "" The text description of [UsageFlags](#Certificate_f_UsageFlags). This value will be one or more of the following strings and will be separated by commas: - Digital Signature - Non-Repudiation - Key Encipherment - Data Encipherment - Key Agreement - Certificate Signing - CRL Signing - Encipher Only If the provider is OpenSSL, the value is a comma-separated list of X.509 certificate extension names. **UsageFlags** *int (read-only)* Default: 0 The flags that show intended use for the certificate. The value of [UsageFlags](#Certificate_f_UsageFlags) is a combination of the following flags: | | | | --- | --- | | 0x80 | Digital Signature | | 0x40 | Non-Repudiation | | 0x20 | Key Encipherment | | 0x10 | Data Encipherment | | 0x08 | Key Agreement | | 0x04 | Certificate Signing | | 0x02 | CRL Signing | | 0x01 | Encipher Only | Please see the [Usage](#Certificate_f_Usage) field for a text representation of [UsageFlags](#Certificate_f_UsageFlags). This functionality currently is not available when the provider is OpenSSL. **Version** *string (read-only)* Default: "" The certificate's version number. The possible values are the strings "V1", "V2", and "V3". **Subject** *string* Default: "" The subject of the certificate used for client authentication. This field will be populated with the full subject of the loaded certificate. When loading a certificate, the subject is used to locate the certificate in the store. If an exact match is not found, the store is searched for subjects containing the value of the property. If a match is still not found, the property is set to an empty string, and no certificate is selected. The special value "*" picks a random certificate in the certificate store. The certificate subject is a comma-separated list of distinguished name fields and values. For instance, "CN=www.server.com, OU=test, C=US, E=example@email.com". Common fields and their meanings are as follows: | Field | Meaning | | --- | --- | | CN | Common Name. This is commonly a hostname like www.server.com. | | O | Organization | | OU | Organizational Unit | | L | Locality | | S | State | | C | Country | | E | Email Address | If a field value contains a comma, it must be quoted. **Encoded** *string* Default: "" The certificate (PEM/Base64 encoded). This field is used to assign a specific certificate. The [Store](#Certificate_f_Store) and [Subject](#Certificate_f_Subject) fields also may be used to specify a certificate. When [Encoded](#Certificate_f_Encoded) is set, a search is initiated in the current [Store](#Certificate_f_Store) for the private key of the certificate. If the key is found, [Subject](#Certificate_f_Subject) is updated to reflect the full subject of the selected certificate; otherwise, [Subject](#Certificate_f_Subject) is set to an empty string. **EncodedB** *byte []* Default: "" The certificate (PEM/Base64 encoded). This field is used to assign a specific certificate. The [Store](#Certificate_f_Store) and [Subject](#Certificate_f_Subject) fields also may be used to specify a certificate. When [Encoded](#Certificate_f_Encoded) is set, a search is initiated in the current [Store](#Certificate_f_Store) for the private key of the certificate. If the key is found, [Subject](#Certificate_f_Subject) is updated to reflect the full subject of the selected certificate; otherwise, [Subject](#Certificate_f_Subject) is set to an empty string. ## Constructors ```text public Certificate(); ``` Creates a instance whose properties can be set. ```text public Certificate(string certificateFile); ``` Opens * CertificateFile * and reads out the contents as an X.509 public key. ```text public Certificate(byte[] encoded); ``` Parses * Encoded * as an X.509 public key. ```text public Certificate(CertStoreTypes storeType, string store, string storePassword, string subject); ``` * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a file containing the certificate store. * StorePassword * is the password used to protect the store. After the store has been successfully opened, the component will attempt to find the certificate identified by * Subject * . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN). The * Subject * parameter can also take an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load in a "Thumbprint=value" format. ```text public Certificate(CertStoreTypes storeType, string store, string storePassword, string subject, string configurationString); ``` * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a file containing the certificate store. * StorePassword * is the password used to protect the store. * ConfigurationString * is a newline-separated list of name-value pairs that may be used to modify the default behavior. Possible values include "PersistPFXKey", which shows whether or not the PFX key is persisted after performing operations with the private key. This correlates to the PKCS12_NO_PERSIST_KEY CryptoAPI option. The default value is True (the key is persisted). "Thumbprint" - an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load. When specified, this value is used to select the certificate in the store. This is applicable to the * cstUser * , * cstMachine * , * cstPublicKeyFile * , and * cstPFXFile * store types. "UseInternalSecurityAPI" shows whether the platform (default) or the internal security API is used when performing certificate-related operations. After the store has been successfully opened, the component will attempt to find the certificate identified by * Subject * . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN). The * Subject * parameter can also take an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load in a "Thumbprint=value" format. ```text public Certificate(CertStoreTypes storeType, string store, string storePassword, byte[] encoded); ``` * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a file containing the certificate store. * StorePassword * is the password used to protect the store. After the store has been successfully opened, the component will load * Encoded * as an X.509 certificate and search the opened store for a corresponding private key. ```text public Certificate(CertStoreTypes storeType, byte[] store, string storePassword, string subject); ``` * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a byte array containing the certificate data. * StorePassword * is the password used to protect the store. After the store has been successfully opened, the component will attempt to find the certificate identified by * Subject * . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN). The * Subject * parameter can also take an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load in a "Thumbprint=value" format. ```text public Certificate(CertStoreTypes storeType, byte[] store, string storePassword, string subject, string configurationString); ``` * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a byte array containing the certificate data. * StorePassword * is the password used to protect the store. After the store has been successfully opened, the component will attempt to find the certificate identified by * Subject * . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN). The * Subject * parameter can also take an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load in a "Thumbprint=value" format. ```text public Certificate(CertStoreTypes storeType, byte[] store, string storePassword, byte[] encoded); ``` * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a byte array containing the certificate data. * StorePassword * is the password used to protect the store. After the store has been successfully opened, the component will load * Encoded * as an X.509 certificate and search the opened store for a corresponding private key. # SFTPConnection Type A currently connected client. ## Remarks This type describes the connection of a client that currently is connected to the component. You may use the different fields of this type to manage the connection. The following fields are available: - [Connected](#SFTPConnection_f_Connected) - [ConnectionId](#SFTPConnection_f_ConnectionId) - [ErrorMessage](#SFTPConnection_f_ErrorMessage) - [FileData](#SFTPConnection_f_FileData) - [LocalAddress](#SFTPConnection_f_LocalAddress) - [ProtocolVersion](#SFTPConnection_f_ProtocolVersion) - [RemoteHost](#SFTPConnection_f_RemoteHost) - [RemotePort](#SFTPConnection_f_RemotePort) - [Timeout](#SFTPConnection_f_Timeout) ## Fields **Connected** *bool (read-only)* Default: False This field indicates the status of individual connections. When *true*, the connection is established. Use the Disconnect method to disconnect an existing connection. **ConnectionId** *string (read-only)* Default: "" This field contains an Id generated by the component to identify each connection. This Id is unique to this connection. **ErrorMessage** *string* Default: "" [ErrorMessage](#SFTPConnection_f_ErrorMessage) is used together with status codes returned from events to send informative errors back to the secure file transfer protocol (SFTP) client through the SSH_FXP_STATUS message. If left blank, the component will set a default message based on the returned status code. **FileData** *string* Default: "" The [FileData](#SFTPConnection_f_FileData) should be set or read when processing read/write file events. **FileDataB** *byte []* Default: "" The [FileData](#SFTPConnection_f_FileData) should be set or read when processing read/write file events. **LocalAddress** *string (read-only)* Default: "" This field shows the IP address of the interface through which the connection is passing. [LocalAddress](#SFTPConnection_f_LocalAddress) is important for multihomed hosts in cases in which it can be used to identify the particular network interface an individual connection is going through. **ProtocolVersion** *int (read-only)* Default: 3 The [ProtocolVersion](#SFTPConnection_f_ProtocolVersion) shows the secure file transfer protocol (SFTP) protocol version negotiated with the client when the SFTP connection was established. **RemoteHost** *string (read-only)* Default: "" The [RemoteHost](#SFTPConnection_f_RemoteHost) shows the IP address of the remote host through which the connection is coming. The connection must be valid or an error will be fired. If the component is configured to use a *SOCKS* firewall, the value assigned to this property may be preceded with an "*". If this is the case, the host name is passed to the firewall unresolved and the firewall performs the DNS resolution. **RemotePort** *int (read-only)* Default: 0 The [RemotePort](#SFTPConnection_f_RemotePort) shows the Transmission Control Protocol (TCP) port on the remote host through which the connection is coming. The connection must be valid or an error will be fired. **Timeout** *int* Default: 0 This field contains a timeout for the component. If the [Timeout](#SFTPConnection_f_Timeout) field is set to 0, all operations will run uninterrupted until successful completion or an error condition is encountered. If [Timeout](#SFTPConnection_f_Timeout) is set to a positive value, the component will wait for the operation to complete before returning control. The component will use DoEvents to enter an efficient wait loop during any potential waiting period, making sure that all system events are processed immediately as they arrive. This ensures that the host application does not freeze and remains responsive. If Timeout expires, and the operation is not yet complete, the component throws an exception. NOTE: By default, all timeouts are *inactivity timeouts*, that is, the timeout period is extended by Timeout seconds when any amount of data is successfully sent or received. The default value for [Timeout](#SFTPConnection_f_Timeout) is specified by the DefaultTimeout property. ## Constructors ```text public SFTPConnection(); ``` # SSHPrompt Type A prompt to provide to the client during keyboard-interactive authentication. ## Remarks This type describes a prompt the Secure Shell (SSH) daemon will send to the client when requesting keyboard-interactive authentication. The following fields are available: - [Echo](#SSHPrompt_f_Echo) - [Prompt](#SSHPrompt_f_Prompt) ## Fields **Echo** *bool* Default: False This field specifies whether or not the client should echo the value entered by the user. **Prompt** *string* Default: "" This field contains the prompt label or text the client should present to the user. ## Constructors ```text public SSHPrompt(); ``` ```text public SSHPrompt(string prompt, bool echo); ``` # Config Settings ([SFTPServer](#sftpserver-component) Component) The component accepts one or more of the following *configuration settings*. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these *internal properties* is provided through the [Config](#config-method-sftpserver-component) method. ### SFTPServer Config Settings **DirListBufferSize[ConnectionId]**: The number of entries to be returned in one response to a request for a directory listing.The default value for this configuration setting is 1, which means that the component will return one entry at a time in response to a request for a directory listing. Changing this value will allow the component to bundle multiple entries into a single response. **MaskSensitiveData**: Masks passwords in logs.The default value is True. When set to True, the component will mask passwords that otherwise would appear in its logs. **MaxStartupsConnections**: The number of unauthenticated connections that the server will accept. This configuration setting specifies the number of unauthenticated connections the server will accept before rejecting new connection attempts. The default value is 50. Additionally, unauthenticated connections may only request a buffer of 256 KB and will be disconnected if they are not authenticated within 120 seconds. **ProtocolVersion**: The highest allowable SFTP version to use.This configuration setting governs the highest allowable secure file transfer protocol (SFTP) version to use when negotiating the version with the client. The default value is 3 because this is the most common version. The component supports values from 3 to 6. **ResolveOwnerAndGroup[ConnectionId]**: Whether to automatically determine the FileOwner and FileGroup.When set to True (default), this configuration setting will allow the component to determine the user name from the Unix-like user identifier, and the group name from the Unix-like group identifier. When set to False, the component will return the Unix-like user and group identifiers instead. **RestrictUserToHomeDir[ConnectionId]**: Whether to restrict the user to their home directory.When True, this configuration setting will restrict the user to the path specified by the "HomeDir" parameter in the [SSHUserAuthRequest](#sshuserauthrequest-event-sftpserver-component) event. When False (default), the user will be able to navigate outside of the home directory. "ConnectionId" specifies the connection to which the restriction applies. ```text sftpserver.Config("RestrictUserToHomeDir[" + e.ConnectionId + "]=true"); ``` ## Example If the [RootDirectory](#rootdirectory-property-sftpserver-component) property of a certain SFTP server is set to */*, then the directory structure of the server might look like this: ```text Root Directory: / bin boot etc home user1 testfolder ``` When RestrictUserToHomeDir is set to True and the "HomeDir" parameter is set to */home/user1*, User 1 will land in the home directory and see the following file system when it connects: ```text Home Directory: /home/user1 /testfolder ``` The client will be able to perform operations only against */home/user1* and its children, but the client can see its working directory relative to the server root directory. **ServerEOL**: Specifies the line endings used in files on the server.This configuration setting is used to inform the connecting client what line endings are used in the files on the system. This is applicable only when [ProtocolVersion](#ProtocolVersion) is set to 4 or higher and a connecting client negotiates protocol version 4 or higher. When a client negotiates version 4 or higher, this value is reported using the "newline" protocol convention. The client may use that to transform line endings when downloading. The default value is CrLF. **SFTPErrorMessage[ConnectionId]**: Specifies the error message to be returned to the client.If an SFTP operation would return an error to the client (e.g., permission denied, file does not exist), then this configuration setting can be used to specify the error message to be returned to the client. This optional configuration setting is effective only when set within an event that uses the "StatusCode" field. **UnixStyleDateFormat**: Controls whether to use the Unix-style date format in directory listings.When set to True, the component will report entries in the Unix-style date format: if the modification time is within the previous 180 days, the date will be formatted as "Mmm dd hh:mm"; otherwise, it will be formatted as "Mmm dd yyyy". **UserRootDirectory[ConnectionId]**: The path of the server root directory for a particular user.When set to a subdirectory of the server root, this configuration setting will override the server [RootDirectory](#rootdirectory-property-sftpserver-component) for a particular user. The "HomeDir" parameter of the [SSHUserAuthRequest](#sshuserauthrequest-event-sftpserver-component) event will represent the initial path of the client relative to the UserRootDirectory. "ConnectionId" specifies the connection to which the restriction applies. ```text sftpserver.Config("UserRootDirectory[" + e.ConnectionId + "]=" + userRootDirectory ); ``` ## Example If the [RootDirectory](#rootdirectory-property-sftpserver-component) property of a certain SFTP server is set to */*, then the directory structure of the server might look like this: ```text Root Directory: / bin boot etc home user1 testfolder ``` When UserRootDirectory is set to */home/user1* and the HomeDir event parameter is set to */*, when User 1 connects they will land in the home directory and see the following file system: ```text Home Directory: / /testfolder ``` The client will be able to perform operations only against */* and its children, and the client cannot see its working directory relative to the server root directory. ### SSHServer Config Settings **AltSSHCertCount**: The number of records in the AltSSHCert configuration settings.This configuration setting controls the size of the following arrays: - [AltSSHCertStore](#AltSSHCertStore) - [AltSSHCertStorePassword](#AltSSHCertStorePassword) - [AltSSHCertStoreType](#AltSSHCertStoreType) - [AltSSHCertSubject](#AltSSHCertSubject) The array indices start at *0* and end at *AltSSHCertCount - 1*. The AltSSHCert configuration settings are used to specify alternative digital certificates to the one set using the [SSHCert](#sshcert-property-sftpserver-component). The server will determine the certificate to use during Secure Shell (SSH) negotiation based on the public key algorithm requested by the connecting client. A certificate with a private key is required for session authentication and encryption. The [AltSSHCertSubject](#AltSSHCertSubject) setting must be set last. When [AltSSHCertSubject](#AltSSHCertSubject) is set, a search is initiated in the [AltSSHCertStore](#AltSSHCertStore) and the certificate is loaded. The alternative server certificate specified by these settings must be configured before setting [Listening](#listening-property-sftpserver-component) to *true*. For example: ```csharp sftpserver.Config("AltSSHCertCount =1"); sftpserver.Config("AltSSHCertStoreType[0]=7"); //PEM Key Blob sftpserver.Config("AltSSHCertStore[0]=" + ed25519Key); //PEM formatted string sftpserver.Config("AltSSHCertSubject[0]=*"); //Load the first (and only) certificate ``` **AltSSHCertStore[i]**: The name of the certificate store.The name of the certificate store. This configuration setting is used when specifying an alternative [SSHCert](#sshcert-property-sftpserver-component). The [AltSSHCertStoreType](#AltSSHCertStoreType) specifies the type of the certificate store specified by [AltSSHCertStore](#AltSSHCertStore). If the store is password protected, specify the password in the [AltSSHCertStorePassword](#AltSSHCertStorePassword). [AltSSHCertStore](#AltSSHCertStore) is used in conjunction with the [AltSSHCertSubject](#AltSSHCertSubject) field to specify the certificate. Designations of certificate stores are platform dependent. The following designations are the most common User and Machine certificate stores in Windows: | | | | --- | --- | | MY | A certificate store holding personal certificates with their associated private keys. | | CA | Certifying authority certificates. | | ROOT | Root certificates. | When the certificate store type is *cstPFXFile*, this property must be set to the name of the file. When the type is *cstPFXBlob*, the property must be set to the binary contents of a PFX file (i.e., PKCS#12 certificate store). **AltSSHCertStorePassword[i]**: The password used to open the certificate store.If the certificate store requires a password, this configuration setting can be used to specify that password. This setting is used when specifying an alternative [SSHCert](#sshcert-property-sftpserver-component) **AltSSHCertStoreType[i]**: The type of certificate store.This configuration setting specifies the type of certificate store. This setting is used when specifying an alternate [SSHCert](#sshcert-property-sftpserver-component). Possible values are as follows: | | | | --- | --- | | 0 | User - This is the default for Windows. This specifies that the certificate store is a certificate store owned by the current user. NOTE: This store type is not available in Java. | | 1 | Machine - For Windows, this specifies that the certificate store is a machine store. NOTE: This store type is not available in Java. | | 2 | PFXFile - The certificate store is the name of a PFX (PKCS12) file containing certificates. | | 3 | PFXBlob - The certificate store is a string (binary or Base64-encoded) representing a certificate store in PFX (PKCS12) format. | | 4 | JKSFile - The certificate store is the name of a Java Key Store (JKS) file containing certificates. NOTE: This store type is available only in Java. | | 5 | JKSBlob - The certificate store is a string (binary or Base64-encoded) representing a certificate store in Java Key Store (JKS) format. NOTE: This store type is available only in Java. | | 6 | PEMKeyFile - The certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate. | | 7 | PEMKeyBlob - The certificate store is a string (binary or Base64-encoded) that contains a private key and an optional certificate. | | 14 | PPKFile - The certificate store is the name of a file that contains a PPK (PuTTY Private Key). | | 15 | PPKBlob - The certificate store is a string (binary) that contains a PPK (PuTTY Private Key). | | 16 | XMLFile - The certificate store is the name of a file that contains a certificate in XML format. | | 17 | XMLBlob - The certificate store is a string that contains a certificate in XML format. | **AltSSHCertSubject[i]**: The alternative certificate subject.The subject of the certificate. This configuration setting is used when specifying an alternative [SSHCert](#sshcert-property-sftpserver-component). The special value of *** may be used to select the first certificate in the store. **ClientSSHVersionString[ConnectionId]**: The client's version string.This configuration setting returns a connected client's SSH version string. It may be queried inside [SSHUserAuthRequest](#sshuserauthrequest-event-sftpserver-component). ```csharp sftpserver1.OnSSHUserAuthRequest += (obj, ev) => { Console.WriteLine(sftpserver1.Config("ClientSSHVersionString[" + ev.ConnectionId + "]")); }; ``` **FireAuthRequestAfterSig**: Whether to fire an informational event after the public key signature has been verified.When performing public key authentication, the connecting client will present both the public key as well as a signature to verify ownership of the corresponding private key. The component will automatically verify the signature and respond to the client to indicate whether the signature could be verified and the connection can continue. This configuration setting controls whether an additional informational event fires to report the result of the signature verification. If set to *true*, the [SSHUserAuthRequest](#sshuserauthrequest-event-sftpserver-component) event will fire twice per public key authentication attempt. The first time the event fires for public key authentication as usual. After verification of the signature has taken place, the [SSHUserAuthRequest](#sshuserauthrequest-event-sftpserver-component) will fire again, and the *AuthMethod* parameter will contain the string *sigstatus*. The *AuthParam* parameter will contain a value of *0* (invalid signature) or *1* (valid signature). If the signature is invalid, it will always result in a rejected authentication attempt. **KeyboardInteractivePrompts[ConnectionId]**: Specifies custom keyboard-interactive prompts for particular connections.By default, setting the [KeyboardInteractivePrompts](#keyboardinteractiveprompts-property-sftpserver-component) property will cause those prompts to be used for every user attempting to connect. This setting can be used to override the [KeyboardInteractivePrompts](#keyboardinteractiveprompts-property-sftpserver-component) property and provide unique prompts for certain connections. This configuration setting takes a list of prompts to display to the client, and each prompt includes an 'echo' parameter to specify whether or not to echo the client's response to the prompt. The prompt and the echo parameter should be separated by a comma (","), and each prompt should be separated by a semicolon (";"). For example: "KeyboardInteractivePrompts[connId]=First prompt,echo=false;Second prompt,echo=true" This configuration setting can be set anywhere in code, but it is necessary to know the ConnectionId for the specific connection beforehand; as such, it is generally recommended to set this configuration inside the [SSHUserAuthRequest](#sshuserauthrequest-event-sftpserver-component) event. Because connecting clients initially attempt to connect with and *AuthMethod* of 'none' (with the understanding that this attempt will fail, and the SSH server will advertise which authentication methods it supports), it is recommended to check the *AuthMethod*, *User*, and *ConnectionId* parameters of the [SSHUserAuthRequest](#sshuserauthrequest-event-sftpserver-component) event and set this configuration setting accordingly. When SSHServer displays keyboard-interactive prompts, it will first check to see if this configuration setting is populated for the current ConnectionId. If it is, the prompts set here will be used instead of those set in the [KeyboardInteractivePrompts](#keyboardinteractiveprompts-property-sftpserver-component) property. Otherwise, the [KeyboardInteractivePrompts](#keyboardinteractiveprompts-property-sftpserver-component) property will function as normal. **KeyRenegotiationThreshold**: Sets the threshold for the SSH Key Renegotiation.This property allows you to specify the threshold, in the number of bytes, for the Secure Shell (SSH) key renegotiation. The default value for this property is set to 1 GB. **Example. Setting the Threshold to 500 MB:** ```text SSHComponent.Config("KeyRenegotiationThreshold=524288000") ``` **LogLevel**: Specifies the level of detail that is logged.This configuration setting controls the level of detail that is logged through the [Log](#log-event-sftpserver-component) event. Possible values are as follows: | | | | --- | --- | | 0 (None) | No messages are logged. | | 1 (Info - Default) | Informational events such as Secure Shell (SSH) handshake messages are logged. | | 2 (Verbose) | Detailed data such as individual packet information are logged. | | 3 (Debug) | Debug data including all relevant sent and received bytes are logged. | **MaxAuthAttempts**: The maximum authentication attempts allowed before forcing a disconnect.This configuration setting specifies the maximum amount of authentication attempts that will be allowed before forcibly disconnecting the client. **NegotiatedStrictKex[ConnectionId]**: Returns whether strict key exchange was negotiated to be used.Returns whether strict key exchange (strict kex) was negotiated during the SSH handshake. This is a per-connection configuration setting accessed by passing the ConnectionId. If strict kex is being used, then this will return *"True"*. If strict kex is not being used, then this will return *"False"*. ```text component.Config("NegotiatedStrictKex[connId]") ``` **ServerSSHVersionString**: The SSH version string sent to connecting clients.This configuration setting specifies the version string value that is sent to all connecting clients. This may be set to specify server specific information. The default value is "SSH-2.0-IPWorks SSH Daemon 2024". When setting your own value, it must begin with "SSH-2.0-" because this is a standard format that specifies the supported SSH version. **SSHKeepAliveCountMax**: The maximum number of keep alive packets to send without a response.This configuration setting specifies the maximum number of keep-alive packets to send when no response is received. Normally a response to a keep-alive packet is received right away. If no response is received, the component will continue to send keep-alive packets until [SSHKeepAliveCountMax](#SSHKeepAliveCountMax) is reached. If this is reached, the component will assume the connection is broken and disconnect. The default value is 5. **SSHKeepAliveInterval**: The interval between keep alive packets.This configuration setting specifies the number of seconds between keep-alive packets. If set to a positive value, the component will send a SSH keep-alive packet after [KeepAliveInterval](#KeepAliveInterval) seconds of inactivity. This configuration setting takes effect only when there is no activity. If any data are sent or received over the connection, it will reset the timer. The default value is *0*, meaning no keep alives will be sent. NOTE: The SSHREVERSETUNNEL component uses a default value of 30. **SSHKeyExchangeAlgorithms**: Specifies the supported key exchange algorithms.This configuration setting may be used to specify the list of supported key exchange algorithms used during Secure Shell (SSH) negotiation. The value should contain a comma-separated list of algorithms. Supported algorithms are as follows: - curve25519-sha256 - curve25519-sha256@libssh.org - diffie-hellman-group1-sha1 - diffie-hellman-group14-sha1 - diffie-hellman-group14-sha256 - diffie-hellman-group16-sha512 - diffie-hellman-group18-sha512 - diffie-hellman-group-exchange-sha256 - diffie-hellman-group-exchange-sha1 - ecdh-sha2-nistp256 - ecdh-sha2-nistp384 - ecdh-sha2-nistp521 - gss-group14-sha256 - gss-group16-sha512 - gss-nistp256-sha256 - gss-curve25519-sha256 - gss-group14-sha1 - gss-gex-sha1 - mlkem768x25519-sha256 The default value is *curve25519-sha256,curve25519-sha256@libssh.org,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,mlkem768x25519-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1,gss-group14-sha256,gss-group16-sha512,gss-nistp256-sha256,gss-curve25519-sha256,gss-group14-sha1,gss-gex-sha1*. **SSHMacAlgorithms**: Specifies the supported Mac algorithms.This configuration setting may be used to specify an alternate list of supported Mac algorithms used during SSH negotiation. This also specifies the order in which the Mac algorithms are preferred. The value should contain a comma-separated list of algorithms. Supported algorithms are as follows: - hmac-sha1 - hmac-md5 - hmac-sha1-96 - hmac-md5-96 - hmac-sha2-256 - hmac-sha2-256-96 - hmac-sha2-512 - hmac-sha2-512-96 - hmac-ripemd160 - hmac-ripemd160-96 - hmac-sha2-256-etm@openssh.com - hmac-sha2-512-etm@openssh.com - hmac-sha2-256-96-etm@openssh.com - hmac-sha2-512-96-etm@openssh.com - umac-64@openssh.com - umac-64-etm@openssh.com - umac-128@openssh.com - umac-128-etm@openssh.com The default value is *hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5,hmac-ripemd160,hmac-sha1-96,hmac-md5-96,hmac-sha2-256-96,hmac-sha2-512-96,hmac-ripemd160-96,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,umac-64@openssh.com,umac-64-etm@openssh.com,umac-128@openssh.com,umac-128-etm@openssh.com*. **SSHPubKeyAuthSigAlgorithms**: Specifies the allowed signature algorithms used by a client performing public key authentication.This configuration setting specifies a list of signature algorithms that a client is allowed to use when authenticating to the server using public key authentication. This applies only when public key authentication is performed by the client. The configuration setting should be a comma-separated list of algorithms. When a client connects, the server will verify that the client performing the public key authentication has used one of the specified signature algorithms. If the client uses a signature algorithm that is not in the list, the connection will be rejected. Possible values areas follows: - ssh-rsa - rsa-sha2-256 - rsa-sha2-512 - ssh-dss - ecdsa-sha2-nistp256 - ecdsa-sha2-nistp384 - ecdsa-sha2-nistp521 - ssh-ed25519 - x509v3-sign-rsa - x509v3-sign-dss The default value in Windows is *ssh-rsa,rsa-sha2-256,rsa-sha2-512,x509v3-sign-rsa,ssh-dss,x509v3-sign-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519*. **SSHPublicKeyAlgorithms**: Specifies the supported public key algorithms for the server's public key. This configuration setting specifies the allowed public key algorithms for the server's public key. This list controls only the public key algorithm used when authenticating the server's public key. This list has no bearing on the public key algorithms that can be used by the client when performing public key authentication to the server. The default value is *ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-256,rsa-sha2-512,ssh-rsa,ssh-dss,x509v3-sign-rsa,x509v3-sign-dss*. **SSHVersionPattern**: The pattern used to match the remote host's version string.This configuration setting specifies the pattern used to accept or deny the remote host's SSH version string. It takes a comma-delimited list of patterns to match. The default value is "*SSH-1.99-*,*SSH-2.0-*" and will accept connections from SSH 1.99 and 2.0 hosts. As an example, the following value would accept connections for SSH 1.99, 2.0, and 2.99 hosts: ```text *SSH-1.99-*,*SSH-2.0-*,*SSH-2.99-* ``` **UserAuthBanner[ConnectionId]**: A custom user authentication banner.This configuration setting specifies a custom user authentication banner, which may be sent to give the client more information regarding an authentication attempt. "ConnectionId" specifies the particular connection to send the message to. This configuration option is effective only when set within the [SSHUserAuthRequest](#sshuserauthrequest-event-sftpserver-component) event. **UseStrictKeyExchange**: Specifies how strict key exchange is supported.This configuration setting controls whether strict key exchange (strict kex) is enabled to mitigate the Terrapin attack. When enabled, the component will indicate support for strict key exchange by automatically including the pseudo-algorithm *kex-strict-c-v00@openssh.com* for client components and *kex-strict-s-v00@openssh.com* for server components in the list of supported key exchange algorithms. Because both client and server must implement strict key exchange to effectively mitigate the Terrapin attack, the component provides options to further control the behavior in different scenarios. Possible values for this setting are as follows: | | | | --- | --- | | 0 | Disabled. Strict key exchange is not supported in the component. | | 1 (default) | Enabled, but not enforced. This setting enables strict key exchange, but if the remote host does not support strict key exchange the connection is still allowed to continue. | | 2 | Enabled, but will reject affected algorithms if the remote host does not support strict key exchange. If the remote host supports strict key exchange, all algorithms may be used. If the remote host does not support strict key exchange, the connection will continue only if the selected encryption and message authentication code (MAC) algorithms are not affected by the Terrapin attack. | | 3 | Required. If the remote host does not support strict key exchange, the connection will fail. | ### TCPServer Config Settings **AllowedClients**: A comma-separated list of host names or IP addresses that can access the component.This configuration setting defines a comma-separated list of host names or IPv4 addresses that may access the component. The wildcard character "*" is supported. The default value is "*" and all connections are accepted. When a client connects, the client's address is checked against the list defined here. If there is no match, the [ConnectionRequest](#connectionrequest-event-sftpserver-component) event fires with an *Accept* value set to *false*. If no action is taken within the [ConnectionRequest](#connectionrequest-event-sftpserver-component) event, the client will be disconnected. **BindExclusively**: Whether or not the component considers a local port reserved for exclusive use.If this is *true* (default), the component will bind to the local port with the ExclusiveAddressUse option set, meaning that nothing else can bind to the same port. Also the component will not be able to bind to local ports that are already in use by some other instance, and attempts to do so will result in failure. **BlockedClients**: A comma-separated list of host names or IP addresses that cannot access the component.This configuration setting defines a comma-separated list of host names or IPv4 addresses that cannot access the component.The default value is "" and all connections are accepted. When a client connects, the client's address is checked against the list defined here. If there is a match, the [ConnectionRequest](#connectionrequest-event-sftpserver-component) event fires with an *Accept* value set to *false*. If no action is taken within the [ConnectionRequest](#connectionrequest-event-sftpserver-component) event, the client will not be connected. **CloseStreamAfterTransfer**: If true, the component will close the upload or download stream after the transfer.This configuration setting determines whether the input or output stream is closed after the transfer completes. When set to True (default), all streams will be closed after a transfer is completed. To keep streams open after the transfer of data, set this to False. The default value is True. **DefaultConnectionTimeout**: The inactivity timeout applied to the SSL handshake.This configuration setting specifies the inactivity (in seconds) to apply to incoming Secure Sockets Layer (SSL) connections. When set to a positive value, if the other end is unresponsive for the specified number of seconds, the connection will timeout. This is not applicable to the entire handshake. It is applicable only to the inactivity of the connecting client during the handshake if a response is expected and none is received within the timeout window. The default value is 0, and no connection-specific timeout is applied. NOTE: This is applicable only to incoming SSL connections. This should be set only if there is a specific reason to do so. **InBufferSize**: The size in bytes of the incoming queue of the socket. This is the size of an internal queue in the Transmission Control Protocol (TCP)/IP stack. You can increase or decrease its size depending on the amount of data that you will be receiving. Increasing the value of the [InBufferSize](#InBufferSize) setting can provide significant improvements in performance in some cases. Some TCP/IP implementations do not support variable buffer sizes. If that is the case, when the component is activated, the [InBufferSize](#InBufferSize) reverts to its defined size. The same thing will happen if you attempt to make it too large or too small. [InBufferSize](#InBufferSize) is shared among incoming connections. When the setting is set, the corresponding value is set for incoming connections as they are accepted. Existing connections are not modified. **KeepAliveInterval**: The retry interval, in milliseconds, to be used when a TCP keep-alive packet is sent and no response is received.A TCP keep-alive packet will be sent after a period of inactivity, as defined by [KeepAliveTime](#KeepAliveTime). If no acknowledgment is received from the remote host, the keep-alive packet will be sent again. This setting specifies the interval at which the successive keep-alive packets are sent in milliseconds. If this value is not specified here, the system default is 1 second. This setting is applicable to all connections. NOTE: This value is not applicable in macOS. **KeepAliveTime**: The inactivity time in milliseconds before a TCP keep-alive packet is sent.By default, the operating system will determine the time a connection is idle before a TCP keep-alive packet is sent. If this value is not specified here, the system default is 2 hours. In many cases, a shorter interval is more useful. Set this value to the desired interval in milliseconds. This setting is applicable to all connections. **MaxConnections**: The maximum number of connections available. This is the maximum number of connections available. This setting must be set before [Listening](#listening-property-sftpserver-component) is set to *true*, and once set, it can no longer be changed for the current instance of the component. The maximum value for this setting is 100,000 connections. Use this setting with caution. Extremely large values may affect performance. **OutBufferSize**: The size in bytes of the outgoing queue of the socket.This is the size of an internal queue in the TCP/IP stack. You can increase or decrease its size depending on the amount of data that you will be sending. Increasing the value of the [OutBufferSize](#OutBufferSize) setting can provide significant improvements in performance in some cases. Some TCP/IP implementations do not support variable buffer sizes. If that is the case, when the component is activated the [OutBufferSize](#OutBufferSize) reverts to its defined size. The same thing will happen if you attempt to make it too large or too small. [OutBufferSize](#OutBufferSize) is shared among incoming connections. When the setting is set, the corresponding value is set for incoming connections as they are accepted. Existing connections are not modified. **PreferredDHGroupBits**: Size of the Diffie-Hellman group, in bits.This configuration setting specifies the key length used by the Diffie-Hellman key algorithm. The default value is *2048* (bits). **TcpNoDelay**: Whether or not to delay when sending packets. When set to True, the socket will send all data that are ready to send at once. When set to False, the socket will send smaller buffered packets of data at small intervals. This is known as the Nagle algorithm. By default, this configuration setting is set to False. **UseBackgroundThread**: Whether threads created by the component are background threads.If set to *true*, when the component creates a thread, the thread's IsBackground property will be explicitly set to *true*. By default, this setting is *false*. **UseIPv6**: Whether to use IPv6.When set to 0 (default), the component will use IPv4 exclusively. When set to 1, the component will use IPv6 exclusively. When set to 2, the component will listen for both IPv4 and IPv6 connections. If IPv6 is not available on the system, only IPv4 will be used. The default value is 0. Possible values are as follows: | | | | --- | --- | | 0 | IPv4 Only | | 1 | IPv6 Only | | 2 | IPv6 and IPv4 | ### Base Config Settings **BuildInfo**: Information about the product's build.When queried, this setting will return a string containing information about the product's build. **GUIAvailable**: Whether or not a message loop is available for processing events.In a GUI-based application, long-running blocking operations may cause the application to stop responding to input until the operation returns. The component will attempt to discover whether or not the application has a message loop and, if one is discovered, it will process events in that message loop during any such blocking operation. In some non-GUI applications, an invalid message loop may be discovered that will result in errant behavior. In these cases, setting [GUIAvailable](#GUIAvailable) to *false* will ensure that the component does not attempt to process external events. **LicenseInfo**: Information about the current license.When queried, this setting will return a string containing information about the license this instance of a component is using. It will return the following information: - Product: The product the license is for. - Product Key: The key the license was generated from. - License Source: Where the license was found (e.g., RuntimeLicense, License File). - License Type: The type of license installed (e.g., Royalty Free, Single Server). - Last Valid Build: The last valid build number for which the license will work. **MaskSensitiveData**: Whether sensitive data is masked in log messages.In certain circumstances it may be beneficial to mask sensitive data, like passwords, in log messages. Set this to *true* to mask sensitive data. The default is *true*. **UseFIPSCompliantAPI**: Tells the component whether or not to use FIPS certified APIs.When set to *true*, the component will utilize the underlying operating system's certified APIs. Java editions, regardless of OS, utilize Bouncy Castle Federal Information Processing Standards (FIPS), while all other Windows editions make use of Microsoft security libraries. FIPS mode can be enabled by setting the *UseFIPSCompliantAPI* configuration setting to *true*. This is a static setting that applies to all instances of all components of the toolkit within the process. It is recommended to enable or disable this setting once before the component has been used to establish a connection. Enabling FIPS while an instance of the component is active and connected may result in unexpected behavior. For more details, please see the [FIPS 140-2 Compliance](https://www.nsoftware.com/kb/articles/fips.rst) article. NOTE: This setting is applicable only on Windows. NOTE: Enabling FIPS compliance requires a special license; please contact [sales@nsoftware.com](mailto:sales@nsoftware.com) for details. **UseInternalSecurityAPI**: Whether or not to use the system security libraries or an internal implementation. When set to *false*, the component will use the system security libraries by default to perform cryptographic functions where applicable. In this case, calls to unmanaged code will be made. In certain environments, this is not desirable. To use a completely managed security implementation, set this setting to *true*. Setting this configuration setting to *true* tells the component to use the internal implementation instead of using the system security libraries. On Windows, this setting is set to *false* by default. On Linux/macOS, this setting is set to *true* by default. NOTE: This setting is static. The value set is applicable to all components used in the application. When this value is set, the product's system dynamic link library (DLL) is no longer required as a reference, as all unmanaged code is stored in that file. # Trappable Errors ([SFTPServer](#sftpserver-component) Component) ### SFTPServer Errors | | | | --- | --- | | 118 | Firewall error. Error description contains detailed information. | | 2001 | The specified path is invalid. | | 2002 | An I/O error occurred. | | 2003 | The file attributes could not be set. | The component may also return one of the following error codes, which are inherited from other components. ### SSHServer Errors | | | | --- | --- | | 1201 | Could not forward connection. A detailed message follows. | | 1202 | Could not forward connection/channel data. A detailed message follows. | | 1300 | Could not authenticate client. | | 1301 | No server certificate was specified or no private key found. | ### TCPServer Errors | | | | --- | --- | | 100 | You cannot change the RemotePort at this time. A connection is in progress. | | 101 | You cannot change the RemoteHost at this time. A connection is in progress. | | 102 | The RemoteHost address is invalid (0.0.0.0). | | 104 | TCPServer is already listening. | | 106 | Cannot change [LocalPort](#localport-property-sftpserver-component) when TCPServer is listening. | | 107 | Cannot change [LocalHost](#localhost-property-sftpserver-component) when TCPServer is listening. | | 108 | Cannot change [MaxConnections](#MaxConnections) when TCPServer is listening. | | 112 | You cannot change [MaxLineLength](#MaxLineLength) at this time. A connection is in progress. | | 116 | RemotePort cannot be zero. Please specify a valid service port number. | | 126 | Invalid ConnectionId. | | 135 | Operation would block. | ### TCP/IP Errors | | | | --- | --- | | 10004 | [10004] Interrupted system call. | | 10009 | [10009] Bad file number. | | 10013 | [10013] Access denied. | | 10014 | [10014] Bad address. | | 10022 | [10022] Invalid argument. | | 10024 | [10024] Too many open files. | | 10035 | [10035] Operation would block. | | 10036 | [10036] Operation now in progress. | | 10037 | [10037] Operation already in progress. | | 10038 | [10038] Socket operation on nonsocket. | | 10039 | [10039] Destination address required. | | 10040 | [10040] Message is too long. | | 10041 | [10041] Protocol wrong type for socket. | | 10042 | [10042] Bad protocol option. | | 10043 | [10043] Protocol is not supported. | | 10044 | [10044] Socket type is not supported. | | 10045 | [10045] Operation is not supported on socket. | | 10046 | [10046] Protocol family is not supported. | | 10047 | [10047] Address family is not supported by protocol family. | | 10048 | [10048] Address already in use. | | 10049 | [10049] Cannot assign requested address. | | 10050 | [10050] Network is down. | | 10051 | [10051] Network is unreachable. | | 10052 | [10052] Net dropped connection or reset. | | 10053 | [10053] Software caused connection abort. | | 10054 | [10054] Connection reset by peer. | | 10055 | [10055] No buffer space available. | | 10056 | [10056] Socket is already connected. | | 10057 | [10057] Socket is not connected. | | 10058 | [10058] Cannot send after socket shutdown. | | 10059 | [10059] Too many references, cannot splice. | | 10060 | [10060] Connection timed out. | | 10061 | [10061] Connection refused. | | 10062 | [10062] Too many levels of symbolic links. | | 10063 | [10063] File name is too long. | | 10064 | [10064] Host is down. | | 10065 | [10065] No route to host. | | 10066 | [10066] Directory is not empty | | 10067 | [10067] Too many processes. | | 10068 | [10068] Too many users. | | 10069 | [10069] Disc Quota Exceeded. | | 10070 | [10070] Stale NFS file handle. | | 10071 | [10071] Too many levels of remote in path. | | 10091 | [10091] Network subsystem is unavailable. | | 10092 | [10092] WINSOCK DLL Version out of range. | | 10093 | [10093] Winsock is not loaded yet. | | 11001 | [11001] Host not found. | | 11002 | [11002] Nonauthoritative 'Host not found' (try again or check DNS setup). | | 11003 | [11003] Nonrecoverable errors: FORMERR, REFUSED, NOTIMP. | | 11004 | [11004] Valid name, no data record (check DNS setup). |