rtcvb32: ROT13 - Technically character substitution but with a simple rule. Add 13 to whatever your character is and it's encoded. encode it again and you get the original value.
OneFiercePuppy: I. Caesar what you did there
There's also ROT26 or 2ROT13, which is equivalent to not encrypting the data at all; I could call the "don't encrypt" algorithm NOP encryption (NOP is short for no-op).
I believe it is possible to get ssh to not encrypt, but you have to go out of your way to do so (so it doesn't happen by accident), and situations where you would need to do so are rare.
rtcvb32: Public key Encryption (
based on RSA) takes two primes, multiplies them together to get a shared number which is distributed, then two values are created using the primes and shared number to get your public and private numbers. To get the private number you have to break the shared number back into the two primes. Each prime is likely hundreds of digits long...
One thing to note: It is possible (though extremely unlikely) for the routine that checks to see if a number is prime to let a composite number pass.through. If this happens, the encryption will, I believe, be easily breakable (either that or the encryption will become lossy making decryption not work).