Back to product page
- Introduction
- License agreement
- Classes
- Enumerations
- Exceptions
- WeOnlyDo.Client.SSH
- Methods
- Properties
- AllocatePty
- Authentication
- Blocking
- Columns
- Command
- Compression
- DataOut
- DataReady
- Encryption
- EncryptionList
- ExitSignal
- ExitStatus
- FingerPrintType
- FIPS
- ForwardHost
- ForwardPort
- HMacList
- Hostname
- KeepAlives
- KeyExchangeList
- KeyFowarding
- Login
- Password
- Port
- PrivateKey
- Prompt
- Protocol
- ProxyHostname
- ProxyLogin
- ProxyPassword
- ProxyPort
- ProxyType
- RemoteIdentification
- Rows
- ShowStdErrorMessages
- State
- StripANSI
- Subsystem
- TerminalType
- Timeout
- Version
- Events
- How to get support?
Protocol property
SSH protocol version used.
Type
SupportedProtocols enumeration value.Syntax
- C#
- VB.NET
SupportedProtocols Protocol {get; set; };
Property Protocol As SupportedProtocols
Remarks
Protocol property determines which protocol version will be used when communicating with the server. Possible values are Raw, Telnet, SSH1, SSH2, SSHAuto and Rlogin.If set to Raw or Telnet, then wodSSH.NET will not use internal encryption at all - since these protocols don't support it. If you want to use encryption, you should probably set Protocol to SSHAuto - which will force wodSSH.NET to automatically negotiate SSH (encrypted!) protocol that will be used with the connection. Some servers support both SSH1 and SSH2, in which cases SSH2 will be selected. However, if server is SSH1, wodSSH.NET will automatically fallback to SSH1 and use it.
SSH1 protocol is 'old-style' SSH protocol, which is most popular among UNIX servers today. Almost all servers that support Telnet, support also SSH1 protocol. It's fully encrypted, and it's known to be secure - if DES algorithm is not used for encryption.
SSH2 protocol is somehow newer than SSH1 and uses more sophisticated protocol description. It supports far more encryption algorithms, and most of them are used with larger key values than in SSH1. Although name is similar, protocols are quite different and are not backward compatible.
You can test Protocol property later during connection to obtain protocol type value. Although you may have set it to SSHAuto (for example), wodSSH.NET may change this value internally to SSH1 or SSH2 depending which SSH version it negotiated with remote server.
Please keep in mind that before new connection is established (with some other server) you should set this property back to SSHAuto.