Re: Hello Nethelpers [SSH / PUTTY]Strange behaviour with telnetd
On Saturday, July 01, 2006 6:57 AM GMT,
jbmorla <jbmorla@gmail.com> wrote:
< which is decoded
automatically by the SSH daemon on the Debian side. >
How could sshd automatically decode data sent by the PuTTY session
If it does not have the key to do it ?
I have one ssh manual, 2 ssh howto, the complete sshd man pages,
The complete 7000 lines of PuTTY printed documentation,
If you want to understand how SSH, all of what you mentioned above will not
be of any good. You need to understand the SSH protocol to know how it
works. You can read about it here:
http://www.ietf.org/html.charters/secsh-charter.html
But I can't find where they deal with having duplicate of the same
encrypted key
On both client and server.
If at any moment the encrypted key travels across the network through
the router/bridge,
Which has a private ip on the internet,
Then a cracker might sniff it.
So?
The main idea behind the invention of public key cryptography is to get rid
of all the problems associated with key distribution when using
symmetric/private key cyphers.
Generally speaking, in private key ciphers, you use the same key to encrypt
and decrypt messages. All you do is reverse the steps of the encryption
process itself, while using the same key, and you will get the original
message. In public key ciphers, yoh have only one function, which is used to
both encrypt and decrypt messages. However, you have two keys, each is the
mathematical inverse of the other. Each will decrypt messages encrypted with
the other key. You (usually the application) chooses one of those keys as
the private key, and the other as the public key which is distributed to
everyone.
In an SSH session, each of the SSH server and client exchange their public
keys with the other party. Then each party uses the public key of the other
to encrypt messages and send them over the unsecure connection. So, in your
case, if Putty is sending a message encrypted with the public key of the SSH
server, only the SSH server on the box you are connected to can decrypt that
message because its the only one who has/knows the private key.
PS: while you are at it, consider switching to firefox and ditching IE.
Please be patient, I'm pretty dumb for starters
Later it gets worse ;-)
Regards,
Regards,
IraqiGeek
www.iraqigeek.com
Don't stop at one bug.
Reply to: