For this stuff to work, you need the alternative firmware WDLXTV for your WD TV Live Box. You can get that from the WDLXV site.

Simply get the file and copy it to /conf/ directory on your WD TV Live wdlxtv pimp'ed box:

 scp dailypodcasts.xml root@ip_of_your_wdtv:/conf/ 

(if you have trouble downloading the file, e.g. get displayed XML code, use "Save As..." function of your browser)

Some simple shell scripts for synchronize your data using rsync.

You only have to adapt the variables at the beginning of the scripts according your needs.

rsync_home.sh

This one can be used if you have your remote system mounted onto the local file system, e.g. using NFS or SAMBA

Variables:

MOUNTPOINT: Path on local system where you have mounted the exported path of remote system
LOCALDIR: Path on local system from where you want to synchronize (by default your home directory)
EXCLUDEFILE: File where you can enter all path's (one on a line) that shouldn't be transferred
LOGFILE: File to log output of rsync into

rsync_home_ssh.sh

This one is an example if you want to access the remote system over SSH.

Variables:

REMOTEHOST: Full qualified host name of remote system
LOCALDIR: Path on local system from where you want to synchronize (by default your home directory)
REMOTEDIR: directory on remote host after the colon (":") (by default your home directory)
EXCLUDEFILE: File where you can enter all path's (one on a line) that shouldn't be transferred
LOGFILE: File to log output of rsync into

Remote Host can be either preset or passed as a command line parameter.

For not have to type your passphrase for your ssh key every time, you can store it within your SSH agent.

Sometimes, you need some SSL certificates for providing SSL encrypted pages.

You can obtain a server certificate from Verisign or Entrust but they're quite expensive.

Or you can make them yourself. Here are some tools to get there. I won't provide information about cryptology at all, neither you will find a professional PKI solution here.

Creating your "own CA" makes only sense for sites where encryption should be in place, without providing official trusted credentials. Every user connecting to your secured site get a warning message every time he connects to your site, until he manually accept your CA Certificate.

First you need OpenSSL, the code which deals with digital certificates.
For information on the command options of the OpenSSL tools look at the OpenSSL Documentation (from openssl.org)
Then get the SSL CA-Tools 0.2 (SSL CA-Tools 0.2). This is a version slightly modified so you can also renew certificates easily.
If you do prefer to use the original version, you can find it here: SSL CA-Tools)

The SSL CA-Tools are easy to use scripts which query the necessary information in a dialog and execute the appropriate openssl commands. Untar it somewhere, e.g. under your openssl directory, look at the README, and create a self-signed CA certificate, user- and server certificates and finally sign them with your CA key.