How important is it to you?

When you use the Flock Blog feature, it connects to your server using those XML requests. If there is a protocol analyzer on your network, the captured packets have your user name and password for that blog, in plain text. I'm sure many of you already know of this though, and its very understandable. It's not like the browser is going to go out and use 3DES/DES or even plain IPSec for a little feature, it would slow it down to much, especially for a feature that not many people use. I'm creating my own blog based on my framework for my site, and I'm just trying to think of ways instead of entering a user name and password for credentials (My site will also have public blogs for the technical users). Any of you familiar with Linux, SSH in particular, then you might have some experience using Diffy Helman asymmetric keys for encrypting data. I'm thinking about creating keys for every IP the user wishes to use on their account, along with a pass code/pass phrase, which would create a private and public key. You would then be able to enter your User name, or another credential, not decided on yet, and your public key, which would authorize against the private key in the database. Now, this would run parallel to the users' account, and they would still have the generic username and password for site functions, but more secure forms for the XMLRPC communications.

Feedback?