Differences
This shows you the differences between the selected revisions of the page.
| 2008-07-16 | 2008-11-13 | ||
| remove invalid anchor #server_hostkey_fingerprint (martin) | no summary (90.19.141.67) (hidden) | ||
| Line 38: | Line 38: | ||
| [[administration|System administrator can restrict]] connection to server without having their host keys accepted in advance. | [[administration|System administrator can restrict]] connection to server without having their host keys accepted in advance. | ||
| - | ===== Encryption in SSH ===== | + | == |
| - | SSH clients and servers can use a number of encryption methods. In the older SSH-1 protocol, 3DES and DES are typically used. | + | in |
| - | SSH-2 adds support for additional encryption methods including AES and | + | |
| - | Blowfish. By default, AES is used if supported by the server. While AES is | + | |
| - | considered to be highly secure, AES encryption requires substantial processor overhead. Blowfish is also considered | + | |
| - | secure, but with less computational overhead, it's also theoretically | + | |
| - | easier to perform a brute-force attack. Depending on your security and | + | |
| - | performance requirements, you may wish to configure WinSCP to prefer | + | |
| - | the Blowfish algorithm. 3DES and DES are used with SSH-1 servers. DES | + | |
| - | is widely regarded as insecure, as the resources to perform an | + | |
| - | exhaustive brute-force attack have been well within the realm of | + | |
| - | commercial feasibility for some time. | + | |
| ===== SSH Protocols ===== | ===== SSH Protocols ===== | ||