Encrypting in Networking: Implications of Unencrypted Data

[chroot]

I wasn't speaking of port blocking, but when requiring a set of passwords of which are encrypted so that they can be planely seen, except by the other communicating machine.

You didn't realize you were talking about port blocking, but you were. There are no port-level cryptographic authorization schemes. You can deny connections by IP, but that's about it. Anyone can connect to an open port on another machine. Authorization using cryptography is done by a server servicing that port at the application level -- much, much higher than the port itself.

This is not entirely so, when using a file sharing program, most often the program will merely know your IP, so that someone wanting access to the information being sent could merely "spoof" there IP and pretend they were one of the machines(personaly i would say that the user receiving the file would be the one to spoof, as to promote less work by the middleman in not having to get into the other persons system prior, but to instead just walk into the connect) then simultaniously send it out to the real user spoofing the senders' IP.

And where would the real packets go? Would you just use your super-laser-ray and obliterate them off the ethernet wires?

I was not claiming your ignorance, I'm merely presenting another side to an arguement, and if you wish to degrade to using pety comments such as this to proove your point, then I no longer have any position in this debate anymore. It was nice, and a great debate while it was being upheld properly. I hope you, Reshma, got the answers you were seeking.

We're not conducting a debate. You're saying things that are wrong. I, and others, are correcting you. Whether or not it's worth doing, only you can say.

- Warren