> Something like distributing files with encrypted data in most columns
> can be done, with the encryption key being a combination
> of some hardware-related stuff such as MAC address that the user will
> provide to you, and the key you generate and provide to the user.
> Of course it creates a problem when the target computer crashes.
> Everything else is probably either hackable or would be based
> on the assumption that you'll be in the business forever
> but anyway there must be specialists out there in some security related
> groups that know how to make it hard to hack.
> On the surface of it if you provide this sort of protection you'll be
> able to distribute
> it as open source since you are protecting data and not the code but
> I'm sure bigger lycensing minds will easily prove me wrong and explain
> that there is such a thing as a GPL for data and copyrighting data is bad,
> which would mean that copyrighting anything is bad, or that copyrighting
> data is OK but the essence of your application is data so if you charge
> for it you can't distribute mysql with it under GPL etc.
> Actually it would be interesting to hear the opinion of mysql legal
> department on this.
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1
> Check Out the new free AIM(R) Mail -- 2 GB of storage and
> industry-leading spam and email virus protection.
You will not be able to search on encrypted fields.
Gerald L. Clark
Supplier Systems Corporation