Anyone else bothered by the fact that ddclient.conf contains an unecrypted username and password? Chmoding to 600 only makes me a little less nervous.

Of course if someone gets permission to read ddclient.conf (root permission), then I guess being able to change my zone files would only be a small concern, but what about the http requests when ddclient updates my zone file? Does anyone know if it's a security issue, and if so, how can it be encrypted?

Thanks!

P.S. I'm run Debian Sarge on an old laptop (Compaq Armada 7800) as a home server experiment, with a dynamic IP address. And it's working beautifully, almost for free! Why pay?!

According to http://www.dyndns.com/support/kb/arc..._services.html, ddclient used http up until version 3.7.0. From version 3.7.0 you can add ssl=yes to your conf file and use https.

Thanks gilead, I hadn't come across that. I'm looking into that.

I installed it a few days ago to try it on a box here. The SSL setting works fine, packet sniffing with ethereal just captured gibberish.