Jan - 2014-02-02

Some modifications to this requirement: Another option would be to offer the personalized files for (automatic) download. The base URL would then have to be known.
The stream owner home page server would then need to store some kind of "client identifier" to encrypt the data with, to be able to offer auth files that only the relevant client can read. On installation, the software would have to create a random cliend ID; an option needs to be given to change it to another random ID later (for copied installations that need their own ID).
Actually the externally visible client ID would be a public key to encrypt the file with; only the client has the corresponding private key at hand.