Ken Elliott wrote:
> Pete>>I am working on such an application for Traditional Chinese Medicine.
> Pete>>I guess I will have to make it lock down by default so they *have* to
> use secure passwords,
> Pete>> change the passwords every so often and so on.
>
> Since you are writing the app, you could encrypt the data BEFORE you store
> it in a database. That would render it useless to anything other then your
> application. Each patient would need a client copy of an app that would
> (using normal security measures) read the database, and decode it using a
> patient-specific key. Your app would have to use a different key for each
> patient, and you'd have to provide a way to change the data should a key be
> made public. That way, you could only lose on patient's data at a time,
> rather than risk the whole DB.
Hi Ken!
Food for thought, thanks. Academic right now since I am still trying to
copy a file to a floppy - in Linux, that is. I can do it in Windows but
the non-profit can't afford Windows . . .
Regards,
Pete
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 16:47:54 EDT