[email protected] (Mark Post) writes: > SSH depends on SSL to do its encryption.
SSH & SSL both do public key operations SSL(/TLS) has bunch of stuff in the protocol with (public key) digital certificates. SSH protocol doesn't require digital certificates for its public key operations. some "open" ssh references: http://www.openssh.com/ http://en.wikipedia.org/wiki/OpenSSH "features" http://www.openssh.com/features.html the above describes that OpenSSH supports the following symmetric cryptography (after exchanging symmetric cryptography key using public key operation): 3DES, Blowfish, AES, Arcfour. It does mention that some code for licensed or patented components may be from external libraries (like OpenSSL) ... although not 3DES, Blowfish, AES, or Arcfour. I guess that wouldn't preclude a totally different SSH implementation from borrowing something like AES (or Blowfish) encryption implementation from a SSL library (and depending how packaged ... possibly dependent on SSL package to work ... as opposed to including the code in SSH package). reference to OpenSSH Public Key Authentication http://sial.org/howto/openssh/publickey-auth/ some "open" SSL references: http://www.openssl.org/ http://en.wikipedia.org/wiki/OpenSSL the above mentions that OpenSSL supports the following symmetric cryptography (after exchanging symmetric cryptography key using public key operation): Blowfish, Camellia, DES, RC2, RC4, RC5, IDEA, AES. also (symmetric cryptography) DES wiki page http://en.wikipedia.org/wiki/Data_Encryption_Standard AES wiki page http://en.wikipedia.org/wiki/Advanced_Encryption_Standard Blowfish wiki page http://en.wikipedia.org/wiki/Blowfish_%28cipher%29 -- 40+yrs virtualization experience (since Jan68), online at home since Mar1970 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
