This property is applicable only when the Protocol property
is set to SSH1, SSH2 or SSHAuto, otherwise it is
ignored.
When set to anything other than encAny, during negotiation of a secure connection
between wodSSH and the remote server, wodSSH will allow only
the specified encryption algorithm to be used for encrypted
data transmission. If this property is set to encAny (as it is by default), any encryption known to both
wodSSH and the remote server will be used.
wodSSH implementation forces selection of encryption
algorithms (when encAny is specified) in
this order:
1. For an SSH1 connection it will try to negotiate the
TripleDES algorithm first. If it fails,
it will try Blowfish. If it is not
available (on the remote server), it will fallback to
DES. Please note that the DES algorithm is declared as
'insecure', so you should avoid using it if at all
possible.
2. For an SSH2 connection it will try to negotiate an AES
algorithm first (any type). If it fails,
TripleDES will be attempted. If this is not
available, Blowfish is selected. If
this fails, the connection will be dropped.
DES will not be negotiated at all
because most (new) servers don't support it due to it's poor security.
For a list of all supported encryption methods, look
here.
Additional encryption methods can be added to wodSSH on
your request. If you have a requirement, feel free to send feedback
go general@weonlydo.com
.