On Mon, 2006-05-22 at 05:37 -0500, chrisisbd@leary.csoft.net wrote:
User server side encrypt/decrypt and an https: server. This requires more effort to set up apache to do https: but I suspect is rather easier to do the actual encrypting and decrypting.
It's not as much effort to set up as it seems, there are about a million guides on the interweb on how to do it. In fact certificate generation aside it's pretty much automatic on most modern distros. Depending on how sensitive the data is you can probably use self signed certs.
This has the benefit that you can then format the data in anyway that works as a web page...just bolt a bit of authentication on the front and you are done.
In fact, given that the 'source' code lives on a fairly secure machine at home how vulnerable would the data be if it was just in a password protected Wiki? (i.e. the data itself isn't encrypted)
But the server would have to pass the data in plain text to your browser so that it can be rendered. So anyone sniffing the network would be able to see your data as you viewed the page. Unless you mean that you want to make the data available as downloadable files that are encrypted by another means themselves...but that would be very cumbersome.